lkml.org 
[lkml]   [2017]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v6 17/39] platform: add video-multiplexer subdevice driver
From
Date
Hi Pavel,

On Fri, 2017-04-14 at 22:32 +0200, Pavel Machek wrote:
> Hi!
>
> > > The MUX framework is already in linux-next. Could you use that instead of
> > > adding new driver + bindings that are not compliant with the MUX framework?
> > > I don't think it'd be much of a change in terms of code, using the MUX
> > > framework appears quite simple.
> >
> > It is not quite clear to me how to design the DT bindings for this. Just
> > splitting the video-multiplexer driver from the mux-mmio / mux-gpio
> > would make it necessary to keep the video-multiplexer node to describe
> > the of-graph bindings. But then we have two different nodes in the DT
> > that describe the same hardware:
> >
> > mux: mux {
> > compatible = "mux-gpio";
> > mux-gpios = <&gpio 0>, <&gpio 1>;
> > #mux-control-cells = <0>;
> > }
> >
> > video-multiplexer {
> > compatible = "video-multiplexer"
> > mux-controls = <&mux>;
> >
> > ports {
> > /* ... */
> > }
> > }
> >
> > It would feel more natural to have the ports in the mux node, but then
> > how would the video-multiplexer driver be instanciated, and how would it
> > get to the of-graph nodes?
>
> Device tree representation and code used to implement the muxing
> driver should be pretty independend, no? Yes, one piece of hardware
> should have one entry in the device tree,

I agree.

> so it should be something like:
>
> video-multiplexer {
> compatible = "video-multiplexer-gpio"
> mux-gpios = <&gpio 0>, <&gpio 1>;
> #mux-control-cells = <0>;
>
> mux-controls = <&mux>;
>
> ports {
> /* ... */
> }
> }

That self-referencing mux-controls property looks a bit superfluous:

mux: video-multiplexer {
mux-controls = <&mux>;
};

Other than that, I'm completely fine with splitting the compatible into
something like video-mux-gpio and video-mux-mmio and reusing the
mux-gpios property for video-mux-gpio.

> You should be able to use code in drivers/mux as a library...

This is a good idea in principle, but this requires some rework of the
mux subsystem, and that subsystem hasn't even landed yet. For now I'd
like to focus on getting the DT bindings right.

I'd honestly prefer to not add this rework as a requirement for the i.MX
media drivers to get into staging.

regards
Philipp

\
 
 \ /
  Last update: 2017-04-18 10:13    [W:0.111 / U:2.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site