From: Neil Armstrong <narmstrong@baylibre.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL FOR v5.6] R-Car DU & LVDS decoder
Date: Wed, 18 Dec 2019 12:55:24 +0100 [thread overview]
Message-ID: <51adf016-a591-be25-e2bb-27266b79423d@baylibre.com> (raw)
In-Reply-To: <43211e43-2849-6ef2-d475-9813c0d56c34@baylibre.com>
On 18/12/2019 12:22, Neil Armstrong wrote:
> Hi,
>
> On 18/12/2019 01:44, Laurent Pinchart wrote:
>> Hi Neil,
>>
>> On Tue, Dec 17, 2019 at 02:23:57PM +0100, Neil Armstrong wrote:
>>> On 17/12/2019 13:43, Daniel Vetter wrote:
>>>> On Thu, Nov 28, 2019 at 04:45:24AM +0200, Laurent Pinchart wrote:
>>>>> Hi Dave,
>>>>>
>>>>> The following changes since commit acc61b8929365e63a3e8c8c8913177795aa45594:
>>>>>
>>>>> Merge tag 'drm-next-5.5-2019-11-22' of git://people.freedesktop.org/~agd5f/linux into drm-next (2019-11-26 08:40:23 +1000)
>>>>>
>>>>> are available in the Git repository at:
>>>>>
>>>>> git://linuxtv.org/pinchartl/media.git tags/du-next-20191128
>>>>>
>>>>> for you to fetch changes up to c43bcd64c7c703ff7196f74cb6bfc67e35b562d9:
>>>>>
>>>>> dt-bindings: display: bridge: lvds-codec: Document ti,ds90cf384a (2019-11-28 03:55:56 +0200)
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> - R-Car DU Color Management Module support
>>>>> - LVDS decoder support
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> Fabrizio Castro (9):
>>>>> dt-bindings: display: bridge: Convert lvds-transmitter binding to json-schema
>>>>> dt-bindings: display: bridge: lvds-transmitter: Document powerdown-gpios
>>>>> dt-bindings: display: bridge: lvds-transmitter: Absorb ti,ds90c185.txt
>>>>> dt-bindings: display: bridge: lvds-transmitter: Document "ti,sn75lvds83"
>>>>> drm/bridge: Repurpose lvds-encoder.c
>>>>> drm/bridge: lvds-codec: Add "lvds-decoder" support
>>>>> drm/bridge: lvds-codec: Simplify panel DT node localisation
>>>>> dt-bindings: display: bridge: Repurpose lvds-encoder
>>>>> dt-bindings: display: bridge: lvds-codec: Document ti,ds90cf384a
>>>>
>>>> Why bridge stuff not in drm-misc?
>>>>
>>>> Also, and the reason I've not pulled this:
>>>>
>>>> dim: c43bcd64c7c7 ("dt-bindings: display: bridge: lvds-codec: Document ti,ds90cf384a"): committer Signed-off-by missing.
>>>> dim: bb29b64ac196 ("dt-bindings: display: bridge: Repurpose lvds-encoder"): committer Signed-off-by missing.
>>>> dim: 5db8ae664da4 ("drm/bridge: lvds-codec: Simplify panel DT node localisation"): committer Signed-off-by missing.
>>>> dim: e94bb2bf88e2 ("drm/bridge: lvds-codec: Add "lvds-decoder" support"): committer Signed-off-by missing.
>>>> dim: b6fafff0c335 ("drm/bridge: Repurpose lvds-encoder.c"): committer Signed-off-by missing.
>>>> dim: 1c060450177f ("dt-bindings: display: bridge: lvds-transmitter: Document "ti,sn75lvds83""): committer Signed-off-by missing.
>>>> dim: d2f2a148ba7c ("dt-bindings: display: bridge: lvds-transmitter: Absorb ti,ds90c185.txt"): committer Signed-off-by missing.
>>>> dim: 07e5c8731999 ("dt-bindings: display: bridge: lvds-transmitter: Document powerdown-gpios"): committer Signed-off-by missing.
>>>> dim: 0fa9d2323ed3 ("dt-bindings: display: bridge: Convert lvds-transmitter binding to json-schema"): committer Signed-off-by missing.
>>>> dim: ERROR: issues in commits detected, aborting
>>>
>>> Laurent, I can push them into drm-misc if needed, so it will unlock boris.
>>
>> Thanks for the offer. I've gathered all the bridge patches that are not
>> specific to Renesas in
>>
>> The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:
>>
>> Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)
>>
>> are available in the Git repository at:
>>
>> git://linuxtv.org/pinchartl/media.git drm/bridge/next
>>
>> for you to fetch changes up to efe52545bccf56d62c1fd1704937a971fa2d24f8:
>>
>> dt-bindings: display: bridge: lvds-codec: Absorb thine,thc63lvdm83d.txt (2019-12-18 02:37:47 +0200)
>>
>> ----------------------------------------------------------------
>> Fabrizio Castro (10):
>> dt-bindings: display: bridge: Convert lvds-transmitter binding to json-schema
>> dt-bindings: display: bridge: lvds-transmitter: Document powerdown-gpios
>> dt-bindings: display: bridge: lvds-transmitter: Absorb ti,ds90c185.txt
>> dt-bindings: display: bridge: lvds-transmitter: Document "ti,sn75lvds83"
>> drm/bridge: Repurpose lvds-encoder.c
>> drm/bridge: lvds-codec: Add "lvds-decoder" support
>> drm/bridge: lvds-codec: Simplify panel DT node localisation
>> dt-bindings: display: bridge: Repurpose lvds-encoder
>> dt-bindings: display: bridge: lvds-codec: Document ti,ds90cf384a
>> dt-bindings: display: bridge: lvds-codec: Absorb thine,thc63lvdm83d.txt
>>
>> .../bindings/display/bridge/lvds-codec.yaml | 131 +++++++++++++++++
>> .../bindings/display/bridge/lvds-transmitter.txt | 66 ---------
>> .../bindings/display/bridge/thine,thc63lvdm83d.txt | 50 -------
>> .../bindings/display/bridge/ti,ds90c185.txt | 55 --------
>> drivers/gpu/drm/bridge/Kconfig | 8 +-
>> drivers/gpu/drm/bridge/Makefile | 2 +-
>> drivers/gpu/drm/bridge/lvds-codec.c | 151 ++++++++++++++++++++
>> drivers/gpu/drm/bridge/lvds-encoder.c | 155 ---------------------
>> 8 files changed, 287 insertions(+), 331 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml
>> delete mode 100644 Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt
>> delete mode 100644 Documentation/devicetree/bindings/display/bridge/thine,thc63lvdm83d.txt
>> delete mode 100644 Documentation/devicetree/bindings/display/bridge/ti,ds90c185.txt
>> create mode 100644 drivers/gpu/drm/bridge/lvds-codec.c
>> delete mode 100644 drivers/gpu/drm/bridge/lvds-encoder.c
>>
>> (with proper SoB tags this time).
>>
>> Merging them through drm-misc makes sense, if you want to push them that
>> would be appreciated (although I suppose that would require applying
>> them from patchwork with dim ?).
>>
>> Otherwise I can include them in my next pull request for Renesas, which
>> I plan to submit tomorrow.
>
> Indeed I would need to find out the correct message ID in patchwork to get
> them with dim.
>
> I can have a try, if I fail you can take them in your renesas PR.
Ok, all applied to drm-misc-next.
Neil
>
> Neil
>
>>
>>>> *insert small sermon about if you do your own maintainer, pls do it right ...
>>>>
>>>> Cheers, Daniel
>>>>
>>>>>
>>>>> Geert Uytterhoeven (2):
>>>>> dt-bindings: display: renesas: du: Add vendor prefix to vsps property
>>>>> drm: rcar-du: Recognize "renesas,vsps" in addition to "vsps"
>>>>>
>>>>> Jacopo Mondi (6):
>>>>> dt-bindings: display: renesas,cmm: Add R-Car CMM documentation
>>>>> dt-bindings: display: renesas,du: Document cmms property
>>>>> drm: rcar-du: Add support for CMM
>>>>> drm: rcar-du: kms: Initialize CMM instances
>>>>> drm: rcar-du: crtc: Control CMM operations
>>>>> drm: rcar-du: crtc: Register GAMMA_LUT properties
>>>>>
>>>>> .../bindings/display/bridge/lvds-codec.yaml | 132 +++++++++++++
>>>>> .../bindings/display/bridge/lvds-transmitter.txt | 66 -------
>>>>> .../bindings/display/bridge/ti,ds90c185.txt | 55 ------
>>>>> .../devicetree/bindings/display/renesas,cmm.yaml | 67 +++++++
>>>>> .../devicetree/bindings/display/renesas,du.txt | 15 +-
>>>>> drivers/gpu/drm/bridge/Kconfig | 8 +-
>>>>> drivers/gpu/drm/bridge/Makefile | 2 +-
>>>>> drivers/gpu/drm/bridge/lvds-codec.c | 151 ++++++++++++++
>>>>> drivers/gpu/drm/bridge/lvds-encoder.c | 155 ---------------
>>>>> drivers/gpu/drm/rcar-du/Kconfig | 8 +
>>>>> drivers/gpu/drm/rcar-du/Makefile | 1 +
>>>>> drivers/gpu/drm/rcar-du/rcar_cmm.c | 217 +++++++++++++++++++++
>>>>> drivers/gpu/drm/rcar-du/rcar_cmm.h | 58 ++++++
>>>>> drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 71 +++++++
>>>>> drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 +
>>>>> drivers/gpu/drm/rcar-du/rcar_du_drv.h | 2 +
>>>>> drivers/gpu/drm/rcar-du/rcar_du_group.c | 10 +
>>>>> drivers/gpu/drm/rcar-du/rcar_du_group.h | 2 +
>>>>> drivers/gpu/drm/rcar-du/rcar_du_kms.c | 93 ++++++++-
>>>>> drivers/gpu/drm/rcar-du/rcar_du_regs.h | 5 +
>>>>> 20 files changed, 829 insertions(+), 291 deletions(-)
>>>>> create mode 100644 Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml
>>>>> delete mode 100644 Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt
>>>>> delete mode 100644 Documentation/devicetree/bindings/display/bridge/ti,ds90c185.txt
>>>>> create mode 100644 Documentation/devicetree/bindings/display/renesas,cmm.yaml
>>>>> create mode 100644 drivers/gpu/drm/bridge/lvds-codec.c
>>>>> delete mode 100644 drivers/gpu/drm/bridge/lvds-encoder.c
>>>>> create mode 100644 drivers/gpu/drm/rcar-du/rcar_cmm.c
>>>>> create mode 100644 drivers/gpu/drm/rcar-du/rcar_cmm.h
>>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-18 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 2:45 [GIT PULL FOR v5.6] R-Car DU & LVDS decoder Laurent Pinchart
2019-12-17 12:43 ` Daniel Vetter
2019-12-17 13:23 ` Neil Armstrong
2019-12-18 0:44 ` Laurent Pinchart
2019-12-18 11:22 ` Neil Armstrong
2019-12-18 11:55 ` Neil Armstrong [this message]
2019-12-18 12:59 ` Laurent Pinchart
2019-12-17 21:08 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51adf016-a591-be25-e2bb-27266b79423d@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).