| 1 |
The Atmel ISC driver is not compliant with media controller specification. |
| 2 |
In order to evolve this driver, it has to move to media controller, to |
| 3 |
support enhanced features and future products which embed it. |
| 4 |
The move to media controller involves several changes which are |
| 5 |
not backwards compatible with the current usability of the driver. |
| 6 |
|
| 7 |
The best example is the way the format is propagated from the top video |
| 8 |
driver /dev/videoX down to the sensor. |
| 9 |
|
| 10 |
In a simple configuration sensor ==> isc , the isc just calls subdev s_fmt |
| 11 |
and controls the sensor directly. This is achieved by having a lot of code |
| 12 |
inside the driver that will query the subdev at probe time and make a list |
| 13 |
of formats which are usable. |
| 14 |
Basically the user has nothing to configure, as the isc will handle |
| 15 |
everything at the top level. This is an easy way to capture, but also comes |
| 16 |
with the drawback of lack of flexibility. |
| 17 |
In a more complicated pipeline |
| 18 |
sensor ==> controller 1 ==> controller 2 ==> isc |
| 19 |
this will not be achievable, as controller 1 and controller 2 might be |
| 20 |
media-controller configurable, and will not propagate the formats down to |
| 21 |
the sensor. |
| 22 |
|
| 23 |
After discussions with the media maintainers, the decision is to move |
| 24 |
Atmel ISC to staging as-is, to keep the Kconfig symbols and the users |
| 25 |
to the driver in staging. Thus, all the existing users of the non |
| 26 |
media-controller paradigm will continue to be happy and use the old config |
| 27 |
way. |
| 28 |
|
| 29 |
The new driver was added in the media subsystem with a different |
| 30 |
symbol, with the conversion to media controller done, and new users |
| 31 |
of the driver will be able to use all the new features. |
| 32 |
|
| 33 |
The replacement driver is named VIDEO_MICROCHIP_ISC or |
| 34 |
VIDEO_MICROCHIP_XISC depending on the product flavor. |