All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm: rcar-du: V3U support
Date: Wed, 23 Jun 2021 09:28:34 +0100	[thread overview]
Message-ID: <dba479d7-eab8-dbc0-ec70-0c898c5783df@ideasonboard.com> (raw)
In-Reply-To: <YNKX8qN4YtjFlW6T@pendragon.ideasonboard.com>

Hi Laurent,

On 23/06/2021 03:09, Laurent Pinchart wrote:
> Hi Kieran,
> 
> It seems that the cover letter didn't include the mailing lists on CC,
> fixing this.

Argh, I should have remembered this. I used --cc-cmd
./scripts/get_maintainer... but it doesn't match anything for the cover
letters, when really the cover letter should cc all recipients of all
patches.

Anyone got a workaround for that, so that the cover-letter actually
makes it to the right places as well?


> On Wed, Jun 23, 2021 at 12:20:21AM +0100, Kieran Bingham wrote:
>> Extend support for the V3U Display Unit, making use of the {recently,
>> soon to be} posted DSI encoder from Laurent.
>>
>> Patch 1 just cleans up in preparation for patch 3, and patch 2 is
>> required for operation on the V3U, however it is functional and should
>> be correct for the D3 and E3 as well, as they also lack external sync.
>>
>> Patch 3 enables the V3U and connects it to the MIPI DSI encoder, of
>> which I'm in a race between me and laurent for posting these patches ;-)
> 
> You won the race :-)

Ah well, as long as the dependency is clear ;D

--
Kieran


> 
>> Tests have been run and produce images - but there are artifacts visible
>> and some modes are unavailable, which will need further investigations,
>> but can be done on top of this integration.
>>
>> Kieran Bingham (3):
>>   drm: rcar-du: Sort the DU outputs
>>   drm: rcar-du: Only initialise TVM_TVSYNC mode when supported
>>   drm: rcar-du: Add r8a779a0 device support
>>
>>  drivers/gpu/drm/rcar-du/rcar_du_crtc.c    | 25 ++++++++++++++++++++++-
>>  drivers/gpu/drm/rcar-du/rcar_du_crtc.h    |  6 ++++--
>>  drivers/gpu/drm/rcar-du/rcar_du_drv.c     | 21 +++++++++++++++++++
>>  drivers/gpu/drm/rcar-du/rcar_du_drv.h     |  6 ++++++
>>  drivers/gpu/drm/rcar-du/rcar_du_encoder.c |  4 ++++
>>  drivers/gpu/drm/rcar-du/rcar_du_group.c   |  2 ++
>>  6 files changed, 61 insertions(+), 3 deletions(-)
>>
> 

WARNING: multiple messages have this Message-ID (diff)
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm: rcar-du: V3U support
Date: Wed, 23 Jun 2021 09:28:34 +0100	[thread overview]
Message-ID: <dba479d7-eab8-dbc0-ec70-0c898c5783df@ideasonboard.com> (raw)
In-Reply-To: <YNKX8qN4YtjFlW6T@pendragon.ideasonboard.com>

Hi Laurent,

On 23/06/2021 03:09, Laurent Pinchart wrote:
> Hi Kieran,
> 
> It seems that the cover letter didn't include the mailing lists on CC,
> fixing this.

Argh, I should have remembered this. I used --cc-cmd
./scripts/get_maintainer... but it doesn't match anything for the cover
letters, when really the cover letter should cc all recipients of all
patches.

Anyone got a workaround for that, so that the cover-letter actually
makes it to the right places as well?


> On Wed, Jun 23, 2021 at 12:20:21AM +0100, Kieran Bingham wrote:
>> Extend support for the V3U Display Unit, making use of the {recently,
>> soon to be} posted DSI encoder from Laurent.
>>
>> Patch 1 just cleans up in preparation for patch 3, and patch 2 is
>> required for operation on the V3U, however it is functional and should
>> be correct for the D3 and E3 as well, as they also lack external sync.
>>
>> Patch 3 enables the V3U and connects it to the MIPI DSI encoder, of
>> which I'm in a race between me and laurent for posting these patches ;-)
> 
> You won the race :-)

Ah well, as long as the dependency is clear ;D

--
Kieran


> 
>> Tests have been run and produce images - but there are artifacts visible
>> and some modes are unavailable, which will need further investigations,
>> but can be done on top of this integration.
>>
>> Kieran Bingham (3):
>>   drm: rcar-du: Sort the DU outputs
>>   drm: rcar-du: Only initialise TVM_TVSYNC mode when supported
>>   drm: rcar-du: Add r8a779a0 device support
>>
>>  drivers/gpu/drm/rcar-du/rcar_du_crtc.c    | 25 ++++++++++++++++++++++-
>>  drivers/gpu/drm/rcar-du/rcar_du_crtc.h    |  6 ++++--
>>  drivers/gpu/drm/rcar-du/rcar_du_drv.c     | 21 +++++++++++++++++++
>>  drivers/gpu/drm/rcar-du/rcar_du_drv.h     |  6 ++++++
>>  drivers/gpu/drm/rcar-du/rcar_du_encoder.c |  4 ++++
>>  drivers/gpu/drm/rcar-du/rcar_du_group.c   |  2 ++
>>  6 files changed, 61 insertions(+), 3 deletions(-)
>>
> 

  reply	other threads:[~2021-06-23  8:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210622232024.3215248-1-kieran.bingham@ideasonboard.com>
2021-06-22 23:20 ` [PATCH 1/3] drm: rcar-du: Sort the DU outputs Kieran Bingham
2021-06-22 23:20   ` Kieran Bingham
2021-06-23  2:13   ` Laurent Pinchart
2021-06-23  2:13     ` Laurent Pinchart
2021-06-22 23:20 ` [PATCH 2/3] drm: rcar-du: Only initialise TVM_TVSYNC mode when supported Kieran Bingham
2021-06-22 23:20   ` Kieran Bingham
2021-06-23  2:16   ` Laurent Pinchart
2021-06-23  2:16     ` Laurent Pinchart
2021-06-22 23:20 ` [PATCH 3/3] drm: rcar-du: Add r8a779a0 device support Kieran Bingham
2021-06-22 23:20   ` Kieran Bingham
2021-06-23  2:27   ` Laurent Pinchart
2021-06-23  2:27     ` Laurent Pinchart
2021-06-23 10:50     ` Kieran Bingham
2021-06-23 10:50       ` Kieran Bingham
2021-06-23  5:51   ` kernel test robot
2021-06-23  8:59   ` kernel test robot
2021-06-23  2:09 ` [PATCH 0/3] drm: rcar-du: V3U support Laurent Pinchart
2021-06-23  2:09   ` Laurent Pinchart
2021-06-23  8:28   ` Kieran Bingham [this message]
2021-06-23  8:28     ` Kieran Bingham

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=dba479d7-eab8-dbc0-ec70-0c898c5783df@ideasonboard.com \
    --to=kieran.bingham@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.