dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	SH-Linux <linux-sh@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] R-Car DU: Add support for R8A7793 and R8A7794
Date: Fri, 17 Jul 2015 18:10:04 +0900	[thread overview]
Message-ID: <CANqRtoSeaBExag+z7_yeJKYg1R+HpvJR_+FMpV2wZqQ85H=YrQ@mail.gmail.com> (raw)
In-Reply-To: <2044648.OO6sEKHBOn@avalon>

Hi Laurent,

On Fri, Jul 17, 2015 at 6:06 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> Hi Morimoto-san,
>
> Thank you for your quick reply.
>
> On Friday 17 July 2015 09:03:32 Kuninori Morimoto wrote:
>> Hi Laurent, again
>>
>> >> This patch series adds support for the DU found in the R8A7793 and
>> >> R8A7794 SoCs. It mostly consists of DT bindings updates (1/5 and 2/5)
>> >> with a small driver change in 2/5 to support fixed RGB output routing.
>> >> Patches 4/5 and 5/5 then add DU nodes to the r8a7793.dtsi and
>> >> r8a7794.dtsi, with patch 3/5 adding support for the DU0 clock to
>> >> r8a7794.dtsi.
>> >>
>> >> I will enable DU support for the Gose and Alt board in a later step when
>> >> I'll have access to the schematics. I won't be able to test that due to
>> >> lack of hardware though.
>> >>
>> >> The R8A7794 datasheet documents as single DU clock named DU0, while the
>> >> DU section documents DU0 and DU1 channels. I don't know at this point
>> >> whether this is a datasheet mistake or if the DU0 clock drives both
>> >> channels. I've opted for the latter, but I'd appreciate a confirmation.
>> >
>> > I will check it. please wait
>>
>> According to HW team, MSTP page of datasheet seems wrong
>> Maybe you have already tried, but,
>> can you access to MSTPSR1 :: 27bit (for DU1)
>
> I would try if I had access to an Alt board :-)
>
> Magnus, do you have an Alt board I could access remotely ?

Not sure if it is hooked up right now, but I will make sure you can
get access sometime soon.

Cheers,

/ magnus

      reply	other threads:[~2015-07-17  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  8:26 [PATCH 0/5] R-Car DU: Add support for R8A7793 and R8A7794 Laurent Pinchart
2015-07-17  8:26 ` [PATCH 1/5] drm: rcar-du: Add support for the R8A7793 DU Laurent Pinchart
2015-07-17  8:26 ` [PATCH 2/5] drm: rcar-du: Add support for the R8A7794 DU Laurent Pinchart
2015-07-17  8:26 ` [PATCH 3/5] ARM: shmobile: r8a7794: Add DU0 clock Laurent Pinchart
2015-08-03  7:37   ` Geert Uytterhoeven
2015-07-17  8:26 ` [PATCH 4/5] ARM: shmobile: r8a7793: Add DU node to device tree Laurent Pinchart
2015-07-17  8:26 ` [PATCH 5/5] ARM: shmobile: r8a7794: " Laurent Pinchart
2015-07-17  8:35 ` [PATCH 0/5] R-Car DU: Add support for R8A7793 and R8A7794 Kuninori Morimoto
2015-07-17  9:03   ` Kuninori Morimoto
2015-07-17  9:06     ` Laurent Pinchart
2015-07-17  9:10       ` Magnus Damm [this message]

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='CANqRtoSeaBExag+z7_yeJKYg1R+HpvJR_+FMpV2wZqQ85H=YrQ@mail.gmail.com' \
    --to=magnus.damm@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@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 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).