On Tue, Mar 28, 2017 at 05:35:52PM -0700, Steve Longerbeam wrote: > > > On 03/28/2017 05:21 PM, Rob Herring wrote: > > On Mon, Mar 27, 2017 at 7:40 PM, Steve Longerbeam <slongerbeam@xxxxxxxxx> wrote: > > > Add bindings documentation for the i.MX media driver. > > > > > > <snip> > > > + > > > +mipi_csi2 node > > > +-------------- > > > + > > > +This is the device node for the MIPI CSI-2 Receiver, required for MIPI > > > +CSI-2 sensors. > > > + > > > +Required properties: > > > +- compatible : "fsl,imx6-mipi-csi2", "snps,dw-mipi-csi2"; > > > > As I mentioned in v5, there's a DW CSI2 binding in progress. This > > needs to be based on that. > > Hi Rob, I'm not sure what you are asking me to do. > > I assume if there's another binding doc in progress, it means > someone is working on another Synopsys DW CSI-2 subdevice driver. Yes. see http://patchwork.ozlabs.org/patch/736177/ > Unfortunately I don't have the time to contribute and switch to > this other subdevice, and do test/debug. >From a DT perspective, I'm not asking that you share the subdevice driver, only the binding. Simply put, there's 1 h/w block here, so there should only be 1 binding. The binding is an ABI, so you can't just merge it and change it later. The driver side is a decision for the V4L2 maintainers. > For now I would prefer if this patchset is merged as is, and > then contribute/switch to another CSI-2 subdev later. It is > also getting very difficult managing all these patches (39 as > of this version), and I'd prefer not to spam the lists with > such large patchsets for too much longer. Then maybe you should figure out how to split up the series. I've not looked at it to provide suggestions. Rob _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
