All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-renesas-soc@vger.kernel.org,
	Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH v2] arm64: dts: r8a7795: salvator-x: Add DU0 and DU3 external dot clocks
Date: Thu, 12 Jan 2017 10:41:32 +0100	[thread overview]
Message-ID: <20170112094131.GA7184@verge.net.au> (raw)
In-Reply-To: <67469901.ez4UZFCvZ8@avalon>

On Thu, Jan 12, 2017 at 11:23:57AM +0200, Laurent Pinchart wrote:
> Hi Simon,
> 
> On Thursday 12 Jan 2017 10:04:34 Simon Horman wrote:
> > On Thu, Jan 12, 2017 at 03:51:21AM +0200, Laurent Pinchart wrote:
> > > The clocks are generated by an I2C-controlled programmable clock
> > > generator.
> > > 
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> > > ---
> > > 
> > >  arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 26 +++++++++++++++--
> > >  1 file changed, 24 insertions(+), 2 deletions(-)
> > > 
> > > This patch depends on the clk-versaclock5 driver posted by Marek.
> > 
> > Can the patch be safely applied without the above driver present?
> 
> It will result in DU probing being deferred forever, so I'd say no :-)

Agreed.

> > FWIW, this patch does not seem to apply cleanly on
> > renesas-next-20170110-v4.10-rc2.
> 
> I'll fix the conflicts and resubmit when the driver lands.

Thanks.

      reply	other threads:[~2017-01-12  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  1:51 [PATCH v2] arm64: dts: r8a7795: salvator-x: Add DU0 and DU3 external dot clocks Laurent Pinchart
2017-01-12  1:56 ` Marek Vasut
2017-01-12  8:36 ` Geert Uytterhoeven
2017-01-12  9:04 ` Simon Horman
2017-01-12  9:23   ` Laurent Pinchart
2017-01-12  9:41     ` Simon Horman [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=20170112094131.GA7184@verge.net.au \
    --to=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut@gmail.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 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.