On Fri, Mar 02, 2018 at 01:58:53PM +0100, Hans de Goede wrote: > On 02-03-18 13:18, Mark Brown wrote: > > What makes you claim that? Any board with jack detection wired up will > > call that function. Not all boards have that configured of course but > > there's absolutely nothing Intel specific about that interface. > Right I'm not claiming the interface is Intel specific, what I'm trying > to say is that the need for some code outside of the codec driver > to create the jack means that adding jack-support to DT platforms > cannot be done through just adding DT properties (once this patch > is merged), it will still require platform code changes. On DT the situation with generic drivers is much better than it is on ACPI so we're actually able to create jacks purely from DT with both the simple and graph cards. This was what drove the creation of the generic jack operation rather than device specific function calls, Bard realized that the device specific calls were all very similar and adding the call allowed the generic cards to work with jacks. > > No, that's really not a good idea. Any jacks in the system are part of > > the system specific wiring, they're not something that's intrinsic to > > the CODEC. Even with fairly basic setups you've got options like having > > a headset jack or separate microphone and headphone jacks. > OK, so if doing the jack creation in the machine-driver / platform > code is by design and you want to keep things that way, then I > assume that what needs changing for v3 of this patch is: > 1) Split the patch in separate codec + machine-drv patches > 2) Add comments to make the ordering requirements clear to > both the codec- and machine-driver. > Correct? Yes, I think so.
Attachment:
signature.asc
Description: PGP signature
