| Message ID | 20240509-dt-bindings-dsi-panel-reg-v1-0-8b2443705be0@linaro.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | dt-bindings: display: panel: constrain 'reg' | expand |
On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: > Hi, > > Cleanups for display panel bindings. > > Rob, maybe you could take entire set if it applies? I based it on > linux-next, so letl me know if I need to rebase on your for-next. Applied. These 2 don't exist in my tree: Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml Documentation/devicetree/bindings/display/panel/raydium,rm69380.yaml Rob
On Mon, 13 May 2024 at 16:17, Rob Herring <robh@kernel.org> wrote: > > On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > Cleanups for display panel bindings. > > > > Rob, maybe you could take entire set if it applies? I based it on > > linux-next, so letl me know if I need to rebase on your for-next. > > Applied. These 2 don't exist in my tree: It's most likely fine, but was there an ack from drm-misc maintainers? > Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml > Documentation/devicetree/bindings/display/panel/raydium,rm69380.yaml Because those were added to drm-misc during the last cycle. So ideally the patch should have gone through drm-misc.
On 13/05/2024 18:41, Dmitry Baryshkov wrote: > On Mon, 13 May 2024 at 16:17, Rob Herring <robh@kernel.org> wrote: >> >> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: >>> Hi, >>> >>> Cleanups for display panel bindings. >>> >>> Rob, maybe you could take entire set if it applies? I based it on >>> linux-next, so letl me know if I need to rebase on your for-next. >> >> Applied. These 2 don't exist in my tree: > > It's most likely fine, but was there an ack from drm-misc maintainers? > >> Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml >> Documentation/devicetree/bindings/display/panel/raydium,rm69380.yaml > > Because those were added to drm-misc during the last cycle. So ideally > the patch should have gone through drm-misc. > Exact there's a conflict on today's next, Rob can you drop them so I can apply them via drm-misc ? Thanks, Neil
On 14/05/2024 10:44, Neil Armstrong wrote: > On 13/05/2024 18:41, Dmitry Baryshkov wrote: >> On Mon, 13 May 2024 at 16:17, Rob Herring <robh@kernel.org> wrote: >>> >>> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: >>>> Hi, >>>> >>>> Cleanups for display panel bindings. >>>> >>>> Rob, maybe you could take entire set if it applies? I based it on >>>> linux-next, so letl me know if I need to rebase on your for-next. >>> >>> Applied. These 2 don't exist in my tree: >> >> It's most likely fine, but was there an ack from drm-misc maintainers? >> >>> Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml >>> Documentation/devicetree/bindings/display/panel/raydium,rm69380.yaml >> >> Because those were added to drm-misc during the last cycle. So ideally >> the patch should have gone through drm-misc. >> > > Exact there's a conflict on today's next, Rob can you drop them so I can apply them via drm-misc ? It's almost the first time I see bindings picked up via drm-misc. Is this an exception or rather new trend (which would be awesome as this is what we prefer usually)? Best regards, Krzysztof
On 14/05/2024 11:07, Krzysztof Kozlowski wrote: > On 14/05/2024 10:44, Neil Armstrong wrote: >> On 13/05/2024 18:41, Dmitry Baryshkov wrote: >>> On Mon, 13 May 2024 at 16:17, Rob Herring <robh@kernel.org> wrote: >>>> >>>> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: >>>>> Hi, >>>>> >>>>> Cleanups for display panel bindings. >>>>> >>>>> Rob, maybe you could take entire set if it applies? I based it on >>>>> linux-next, so letl me know if I need to rebase on your for-next. >>>> >>>> Applied. These 2 don't exist in my tree: >>> >>> It's most likely fine, but was there an ack from drm-misc maintainers? >>> >>>> Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml >>>> Documentation/devicetree/bindings/display/panel/raydium,rm69380.yaml >>> >>> Because those were added to drm-misc during the last cycle. So ideally >>> the patch should have gone through drm-misc. >>> >> >> Exact there's a conflict on today's next, Rob can you drop them so I can apply them via drm-misc ? > > It's almost the first time I see bindings picked up via drm-misc. Is > this an exception or rather new trend (which would be awesome as this is > what we prefer usually)? I usually pick up bindings along drivers like other subsystems, and when reviewed I take independent bindings fixes aswell when rob doesn't pick them before. Neil > > Best regards, > Krzysztof >
Hi, Cleanups for display panel bindings. Rob, maybe you could take entire set if it applies? I based it on linux-next, so letl me know if I need to rebase on your for-next. I actually do not know if devices affected here take more than one chip select or DSI virtual channel number. I assume DTS and examples are correct here. Worst case this can be fixed later - maxItems:2. Best regards, Krzysztof --- Krzysztof Kozlowski (3): dt-bindings: display: samsung,ams495qa01: add missing SPI properties ref dt-bindings: display: panel: constrain 'reg' in SPI panels dt-bindings: display: panel: constrain 'reg' in DSI panels Documentation/devicetree/bindings/display/panel/abt,y030xx067a.yaml | 4 +++- .../devicetree/bindings/display/panel/asus,z00t-tm5p5-nt35596.yaml | 5 ++++- .../devicetree/bindings/display/panel/boe,bf060y8m-aj0.yaml | 4 +++- Documentation/devicetree/bindings/display/panel/boe,himax8279d.yaml | 4 +++- .../devicetree/bindings/display/panel/boe,th101mb31ig002-28a.yaml | 4 +++- .../devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml | 2 +- Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml | 5 ++++- .../devicetree/bindings/display/panel/fascontek,fs035vg158.yaml | 3 +++ .../devicetree/bindings/display/panel/feixin,k101-im2ba02.yaml | 5 ++++- Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml | 4 +++- Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml | 3 ++- Documentation/devicetree/bindings/display/panel/ilitek,ili9163.yaml | 4 +++- Documentation/devicetree/bindings/display/panel/ilitek,ili9322.yaml | 3 +++ Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml | 3 ++- Documentation/devicetree/bindings/display/panel/ilitek,ili9805.yaml | 4 +++- .../devicetree/bindings/display/panel/ilitek,ili9881c.yaml | 4 +++- .../devicetree/bindings/display/panel/innolux,ej030na.yaml | 4 +++- .../devicetree/bindings/display/panel/innolux,p097pfg.yaml | 4 +++- .../devicetree/bindings/display/panel/jadard,jd9365da-h3.yaml | 3 ++- .../devicetree/bindings/display/panel/jdi,lpm102a188a.yaml | 4 +++- .../devicetree/bindings/display/panel/jdi,lt070me05000.yaml | 4 +++- .../devicetree/bindings/display/panel/kingdisplay,kd035g6-54nt.yaml | 4 +++- .../devicetree/bindings/display/panel/leadtek,ltk035c5444t.yaml | 3 +++ .../devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml | 5 ++++- .../devicetree/bindings/display/panel/leadtek,ltk500hd1829.yaml | 5 ++++- Documentation/devicetree/bindings/display/panel/lg,lg4573.yaml | 3 ++- Documentation/devicetree/bindings/display/panel/lg,sw43408.yaml | 4 +++- .../devicetree/bindings/display/panel/lgphilips,lb035q02.yaml | 3 +++ Documentation/devicetree/bindings/display/panel/nec,nl8048hl11.yaml | 4 +++- .../devicetree/bindings/display/panel/newvision,nv3051d.yaml | 4 +++- .../devicetree/bindings/display/panel/novatek,nt35510.yaml | 5 ++++- .../devicetree/bindings/display/panel/novatek,nt35950.yaml | 4 +++- .../devicetree/bindings/display/panel/novatek,nt36523.yaml | 4 +++- .../devicetree/bindings/display/panel/novatek,nt36672a.yaml | 4 +++- .../devicetree/bindings/display/panel/olimex,lcd-olinuxino.yaml | 4 +++- .../devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml | 3 +++ .../devicetree/bindings/display/panel/raydium,rm67191.yaml | 4 +++- .../devicetree/bindings/display/panel/raydium,rm692e5.yaml | 4 +++- .../devicetree/bindings/display/panel/raydium,rm69380.yaml | 5 +++-- Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml | 2 +- .../devicetree/bindings/display/panel/samsung,amoled-mipi-dsi.yaml | 4 +++- .../devicetree/bindings/display/panel/samsung,ams495qa01.yaml | 5 ++++- Documentation/devicetree/bindings/display/panel/samsung,ld9040.yaml | 4 +++- .../devicetree/bindings/display/panel/samsung,lms380kf01.yaml | 3 ++- .../devicetree/bindings/display/panel/samsung,lms397kf04.yaml | 3 ++- .../devicetree/bindings/display/panel/samsung,s6d16d0.yaml | 4 +++- .../devicetree/bindings/display/panel/samsung,s6d27a1.yaml | 3 ++- .../devicetree/bindings/display/panel/samsung,s6d7aa0.yaml | 3 ++- .../devicetree/bindings/display/panel/samsung,s6e63m0.yaml | 4 +++- .../bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml | 5 ++++- .../devicetree/bindings/display/panel/samsung,s6e8aa0.yaml | 4 +++- .../devicetree/bindings/display/panel/sharp,lq101r1sx01.yaml | 4 +++- .../devicetree/bindings/display/panel/sharp,ls043t1le01.yaml | 4 +++- .../devicetree/bindings/display/panel/sharp,ls060t1sx01.yaml | 4 +++- .../devicetree/bindings/display/panel/sitronix,st7789v.yaml | 4 +++- Documentation/devicetree/bindings/display/panel/sony,acx424akp.yaml | 5 ++++- Documentation/devicetree/bindings/display/panel/sony,acx565akm.yaml | 3 +++ .../devicetree/bindings/display/panel/sony,td4353-jdi.yaml | 3 ++- .../devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml | 3 ++- .../devicetree/bindings/display/panel/synaptics,r63353.yaml | 6 ++++-- Documentation/devicetree/bindings/display/panel/tpo,td.yaml | 4 +++- Documentation/devicetree/bindings/display/panel/tpo,tpg110.yaml | 3 ++- .../devicetree/bindings/display/panel/visionox,rm69299.yaml | 3 ++- .../devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml | 5 ++++- 64 files changed, 187 insertions(+), 60 deletions(-) --- base-commit: b010817abf0197596fbfddf1957bac968facb991 change-id: 20240509-dt-bindings-dsi-panel-reg-a6e7d930b46f Best regards,