Re: [PATCH v6 0/5] davinci: VPIF: add DT support
On 27/01/17 18:22, Kevin Hilman wrote: On Fri, Dec 16, 2016 at 4:49 PM, Kevin Hilmanwrote: Hans Verkuil writes: On 07/12/16 19:30, Kevin Hilman wrote: Prepare the groundwork for adding DT support for davinci VPIF drivers. This series does some fixups/cleanups and then adds the DT binding and DT compatible string matching for DT probing. The controversial part from previous versions around async subdev parsing, and specifically hard-coding the input/output routing of subdevs, has been left out of this series. That part can be done as a follow-on step after agreement has been reached on the path forward. With this version, platforms can still use the VPIF capture/display drivers, but must provide platform_data for the subdevs and subdev routing. Tested video capture to memory on da850-lcdk board using composite input. Other than the comment for the first patch this series looks good. So once that's addressed I'll queue it up for 4.11. I've fixed that issue, and sent an update for just that patch in reply to the original. Thanks for the review, Gentle ping on this series. I'm still not seeing this series yet in linux-next, so am worried it might not make it for v4.11. Kevin Mauro was on vacation, so pull requests were delayed. I understood from him that he's going to process pending pull requests this week, which should include your series. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
On Fri, Dec 16, 2016 at 4:49 PM, Kevin Hilmanwrote: > Hans Verkuil writes: > >> On 07/12/16 19:30, Kevin Hilman wrote: >>> Prepare the groundwork for adding DT support for davinci VPIF drivers. >>> This series does some fixups/cleanups and then adds the DT binding and >>> DT compatible string matching for DT probing. >>> >>> The controversial part from previous versions around async subdev >>> parsing, and specifically hard-coding the input/output routing of >>> subdevs, has been left out of this series. That part can be done as a >>> follow-on step after agreement has been reached on the path forward. >>> With this version, platforms can still use the VPIF capture/display >>> drivers, but must provide platform_data for the subdevs and subdev >>> routing. >>> >>> Tested video capture to memory on da850-lcdk board using composite >>> input. >> >> Other than the comment for the first patch this series looks good. >> >> So once that's addressed I'll queue it up for 4.11. > > I've fixed that issue, and sent an update for just that patch in reply > to the original. > > Thanks for the review, Gentle ping on this series. I'm still not seeing this series yet in linux-next, so am worried it might not make it for v4.11. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
+ Mauro On Tuesday 03 January 2017 02:42 PM, Laurent Pinchart wrote: > Hi Sekhar, > > On Tuesday 03 Jan 2017 14:33:00 Sekhar Nori wrote: >> On Friday 16 December 2016 03:17 PM, Hans Verkuil wrote: >>> On 07/12/16 19:30, Kevin Hilman wrote: Prepare the groundwork for adding DT support for davinci VPIF drivers. This series does some fixups/cleanups and then adds the DT binding and DT compatible string matching for DT probing. The controversial part from previous versions around async subdev parsing, and specifically hard-coding the input/output routing of subdevs, has been left out of this series. That part can be done as a follow-on step after agreement has been reached on the path forward. With this version, platforms can still use the VPIF capture/display drivers, but must provide platform_data for the subdevs and subdev routing. Tested video capture to memory on da850-lcdk board using composite input. >>> >>> Other than the comment for the first patch this series looks good. >>> >>> So once that's addressed I'll queue it up for 4.11. >> >> Can you provide an immutable commit (as it will reach v4.11) with with >> this series applied? I have some platform changes to queue for v4.11 >> that depend on the driver updates. > > I don't think that's possible, given that Mauro rewrites all patches when > handling pull requests to prepend [media] to the subject line and to add his > SoB. Only Mauro can thus provide a stable branch, Hans can't. Hi Mauro, once Hans sends you these patches, can you host these patches on a stable branch, which I can merge into my pull request to ARM-SoC. I have some platform updates that depend on these driver changes. Ideally the branch has only these patches over an early v4.10-rc so I include as little of media stuff as possible in my pull request. Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
Hi Sekhar, On Tuesday 03 Jan 2017 14:33:00 Sekhar Nori wrote: > On Friday 16 December 2016 03:17 PM, Hans Verkuil wrote: > > On 07/12/16 19:30, Kevin Hilman wrote: > >> Prepare the groundwork for adding DT support for davinci VPIF drivers. > >> This series does some fixups/cleanups and then adds the DT binding and > >> DT compatible string matching for DT probing. > >> > >> The controversial part from previous versions around async subdev > >> parsing, and specifically hard-coding the input/output routing of > >> subdevs, has been left out of this series. That part can be done as a > >> follow-on step after agreement has been reached on the path forward. > >> With this version, platforms can still use the VPIF capture/display > >> drivers, but must provide platform_data for the subdevs and subdev > >> routing. > >> > >> Tested video capture to memory on da850-lcdk board using composite > >> input. > > > > Other than the comment for the first patch this series looks good. > > > > So once that's addressed I'll queue it up for 4.11. > > Can you provide an immutable commit (as it will reach v4.11) with with > this series applied? I have some platform changes to queue for v4.11 > that depend on the driver updates. I don't think that's possible, given that Mauro rewrites all patches when handling pull requests to prepend [media] to the subject line and to add his SoB. Only Mauro can thus provide a stable branch, Hans can't. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
Hi Hans, On Friday 16 December 2016 03:17 PM, Hans Verkuil wrote: > On 07/12/16 19:30, Kevin Hilman wrote: >> Prepare the groundwork for adding DT support for davinci VPIF drivers. >> This series does some fixups/cleanups and then adds the DT binding and >> DT compatible string matching for DT probing. >> >> The controversial part from previous versions around async subdev >> parsing, and specifically hard-coding the input/output routing of >> subdevs, has been left out of this series. That part can be done as a >> follow-on step after agreement has been reached on the path forward. >> With this version, platforms can still use the VPIF capture/display >> drivers, but must provide platform_data for the subdevs and subdev >> routing. >> >> Tested video capture to memory on da850-lcdk board using composite >> input. > > Other than the comment for the first patch this series looks good. > > So once that's addressed I'll queue it up for 4.11. Can you provide an immutable commit (as it will reach v4.11) with with this series applied? I have some platform changes to queue for v4.11 that depend on the driver updates. Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
Hans Verkuilwrites: > On 07/12/16 19:30, Kevin Hilman wrote: >> Prepare the groundwork for adding DT support for davinci VPIF drivers. >> This series does some fixups/cleanups and then adds the DT binding and >> DT compatible string matching for DT probing. >> >> The controversial part from previous versions around async subdev >> parsing, and specifically hard-coding the input/output routing of >> subdevs, has been left out of this series. That part can be done as a >> follow-on step after agreement has been reached on the path forward. >> With this version, platforms can still use the VPIF capture/display >> drivers, but must provide platform_data for the subdevs and subdev >> routing. >> >> Tested video capture to memory on da850-lcdk board using composite >> input. > > Other than the comment for the first patch this series looks good. > > So once that's addressed I'll queue it up for 4.11. I've fixed that issue, and sent an update for just that patch in reply to the original. Thanks for the review, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
On 07/12/16 19:30, Kevin Hilman wrote: Prepare the groundwork for adding DT support for davinci VPIF drivers. This series does some fixups/cleanups and then adds the DT binding and DT compatible string matching for DT probing. The controversial part from previous versions around async subdev parsing, and specifically hard-coding the input/output routing of subdevs, has been left out of this series. That part can be done as a follow-on step after agreement has been reached on the path forward. With this version, platforms can still use the VPIF capture/display drivers, but must provide platform_data for the subdevs and subdev routing. Tested video capture to memory on da850-lcdk board using composite input. Other than the comment for the first patch this series looks good. So once that's addressed I'll queue it up for 4.11. Regards, Hans Changes since v5: - locking fix: updated comment around lock variable - binding doc: added example for - added reviewed-by tags from Laurent (thanks!) Changes since v4: - dropped controversial async subdev parsing support. That can be done as a follow-up step after the discussions have finalized on the right approach. - DT binding Acked by DT maintainer (Rob H.) - reworked locking fix (suggested by Laurent) Changes since v3: - move to a single VPIF node, DT binding updated accordingly - misc fixes/updates based on reviews from Sakari Changes since v2: - DT binding doc: fix example to use correct compatible Changes since v1: - more specific compatible strings, based on SoC: ti,da850-vpif* - fix locking bug when unlocking over subdev s_stream Kevin Hilman (5): [media] davinci: VPIF: fix module loading, init errors [media] davinci: vpif_capture: remove hard-coded I2C adapter id [media] davinci: vpif_capture: fix start/stop streaming locking [media] dt-bindings: add TI VPIF documentation [media] davinci: VPIF: add basic support for DT init .../devicetree/bindings/media/ti,da850-vpif.txt| 83 ++ drivers/media/platform/davinci/vpif.c | 14 +++- drivers/media/platform/davinci/vpif_capture.c | 26 +-- drivers/media/platform/davinci/vpif_capture.h | 2 +- drivers/media/platform/davinci/vpif_display.c | 6 ++ include/media/davinci/vpif_types.h | 1 + 6 files changed, 125 insertions(+), 7 deletions(-) create mode 100644 Documentation/devicetree/bindings/media/ti,da850-vpif.txt -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
Hi Javier, Javier Martinez Canillaswrites: > On Wed, Dec 7, 2016 at 3:30 PM, Kevin Hilman wrote: >> Prepare the groundwork for adding DT support for davinci VPIF drivers. >> This series does some fixups/cleanups and then adds the DT binding and >> DT compatible string matching for DT probing. >> >> The controversial part from previous versions around async subdev >> parsing, and specifically hard-coding the input/output routing of >> subdevs, has been left out of this series. That part can be done as a >> follow-on step after agreement has been reached on the path forward. > > I had a similar need for another board (OMAP3 IGEPv2), that has a > TVP5151 video decoder (that also supports 2 composite or 1 s-video > signal) attached to the OMAP3 ISP. > > I posted some RFC patches [0] to define the input signals in the DT, > and AFAICT Laurent and Hans were not against the approach but just had > some comments on the DT binding. > > Basically they wanted the ports to be directly in the tvp5150 node > instead of under a connectors sub-node [1] and to just be called just > a (input / output) port instead of a connector [2]. > > Unfortunately I was busy with other tasks so I couldn't res-pin the > patches, but I think you could have something similar in the DT > binding for your case and it shouldn't be hard to parse the ports / > endpoints in the driver to get that information from DT and setup the > input and output pins. Thanks for pointing that out. I did see this in Hans' reply to one of my earlier versions. Indeed I think this could be useful in solving my problem. >> With is version, platforms can still use the VPIF capture/display >> drivers, but must provide platform_data for the subdevs and subdev >> routing. >> > > I guess DT backward compatibility isn't a big issue on this platform, > since support for the platform is quite recently and after all someone > who wants to use the vpif with current DT will need platform data and > pdata-quirks anyways. That's correct. > So I agree with you that the input / output signals lookup from DT > could be done as a follow-up. Thanks. I'll happily add the input/output signals once they're agreed upon. In the mean time, at least we can have a usable video capture on this platform, and it's at least a step in the right direction for DT support. Thanks for the review, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 0/5] davinci: VPIF: add DT support
Hello Kevin, On Wed, Dec 7, 2016 at 3:30 PM, Kevin Hilmanwrote: > Prepare the groundwork for adding DT support for davinci VPIF drivers. > This series does some fixups/cleanups and then adds the DT binding and > DT compatible string matching for DT probing. > > The controversial part from previous versions around async subdev > parsing, and specifically hard-coding the input/output routing of > subdevs, has been left out of this series. That part can be done as a > follow-on step after agreement has been reached on the path forward. I had a similar need for another board (OMAP3 IGEPv2), that has a TVP5151 video decoder (that also supports 2 composite or 1 s-video signal) attached to the OMAP3 ISP. I posted some RFC patches [0] to define the input signals in the DT, and AFAICT Laurent and Hans were not against the approach but just had some comments on the DT binding. Basically they wanted the ports to be directly in the tvp5150 node instead of under a connectors sub-node [1] and to just be called just a (input / output) port instead of a connector [2]. Unfortunately I was busy with other tasks so I couldn't res-pin the patches, but I think you could have something similar in the DT binding for your case and it shouldn't be hard to parse the ports / endpoints in the driver to get that information from DT and setup the input and output pins. > With this version, platforms can still use the VPIF capture/display > drivers, but must provide platform_data for the subdevs and subdev > routing. > I guess DT backward compatibility isn't a big issue on this platform, since support for the platform is quite recently and after all someone who wants to use the vpif with current DT will need platform data and pdata-quirks anyways. So I agree with you that the input / output signals lookup from DT could be done as a follow-up. [0]: https://lkml.org/lkml/2016/4/12/983 [1]: https://lkml.org/lkml/2016/4/27/678 [2]: https://lkml.org/lkml/2016/11/11/346 Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v6 0/5] davinci: VPIF: add DT support
Prepare the groundwork for adding DT support for davinci VPIF drivers. This series does some fixups/cleanups and then adds the DT binding and DT compatible string matching for DT probing. The controversial part from previous versions around async subdev parsing, and specifically hard-coding the input/output routing of subdevs, has been left out of this series. That part can be done as a follow-on step after agreement has been reached on the path forward. With this version, platforms can still use the VPIF capture/display drivers, but must provide platform_data for the subdevs and subdev routing. Tested video capture to memory on da850-lcdk board using composite input. Changes since v5: - locking fix: updated comment around lock variable - binding doc: added example for - added reviewed-by tags from Laurent (thanks!) Changes since v4: - dropped controversial async subdev parsing support. That can be done as a follow-up step after the discussions have finalized on the right approach. - DT binding Acked by DT maintainer (Rob H.) - reworked locking fix (suggested by Laurent) Changes since v3: - move to a single VPIF node, DT binding updated accordingly - misc fixes/updates based on reviews from Sakari Changes since v2: - DT binding doc: fix example to use correct compatible Changes since v1: - more specific compatible strings, based on SoC: ti,da850-vpif* - fix locking bug when unlocking over subdev s_stream Kevin Hilman (5): [media] davinci: VPIF: fix module loading, init errors [media] davinci: vpif_capture: remove hard-coded I2C adapter id [media] davinci: vpif_capture: fix start/stop streaming locking [media] dt-bindings: add TI VPIF documentation [media] davinci: VPIF: add basic support for DT init .../devicetree/bindings/media/ti,da850-vpif.txt| 83 ++ drivers/media/platform/davinci/vpif.c | 14 +++- drivers/media/platform/davinci/vpif_capture.c | 26 +-- drivers/media/platform/davinci/vpif_capture.h | 2 +- drivers/media/platform/davinci/vpif_display.c | 6 ++ include/media/davinci/vpif_types.h | 1 + 6 files changed, 125 insertions(+), 7 deletions(-) create mode 100644 Documentation/devicetree/bindings/media/ti,da850-vpif.txt -- 2.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html