devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC] serial: sh-sci: Add device tree support for r8a7779
Date: Tue, 29 Apr 2014 15:44:46 +0200	[thread overview]
Message-ID: <1986104.5bpNkKVN8D@avalon> (raw)
In-Reply-To: <20140428070748.GA24537@verge.net.au>

Hi Simon,

On Monday 28 April 2014 16:07:49 Simon Horman wrote:
> On Mon, Apr 28, 2014 at 10:13:55AM +0900, Simon Horman wrote:
> > On Mon, Apr 28, 2014 at 02:08:16AM +0200, Laurent Pinchart wrote:
> > > On Monday 28 April 2014 09:03:14 Simon Horman wrote:
> > > > On Fri, Apr 25, 2014 at 09:11:06AM +0200, Geert Uytterhoeven wrote:
> > > > > On Fri, Apr 25, 2014 at 9:05 AM, Laurent Pinchart wrote:
> > > > > >> +     scif0: serial@ffe40000 {
> > > > > >> +             compatible = "renesas,scif",
> > > > > >> "renesas,scif-r8a7779";
> > > > > >> +             reg = <0xffe40000 265>;
> > > > > >> +             interrupt-parent = <&gic>;
> > > > > >> +             interrupts = <0 88 IRQ_TYPE_LEVEL_HIGH>;
> > > > > >> +             clocks = <&cpg_clocks R8A7779_CLK_P>;
> > > > > >> +             clock-names = "sci_ick";
> > > > > > 
> > > > > > Clock handling in the sh-sci driver should probably be improved.
> > > > > > The driver currently requires an "sci_ick" interface clock and
> > > > > > supports an optional "sci_fck" functional clock. In practice, as
> > > > > > far as I can see, platforms that provide both sci_ick and sci_fck
> > > > > > set the two clocks to the same source.
> > > > > 
> > > > > That's right. As a consequence, the clock's enable count is
> > > > > incremented
> > > > > 
> > > > > 3 times:
> > > > >   - once for fck,
> > > > >   - once for ick,
> > > > >   - once for generic Runtime PM using the "NULL" clock.
> > > > 
> > > > This approach is fine by me.
> > > > But I think you need to maintain compatibility with the old
> > > > binding ("sci_ick" required, "sci_fsk") as it seems that
> > > > was included in v3.14.
> > > 
> > > sci_fck isn't part of the DT bindings, so we can at least drop that one.
> > 
> > So long as its not used anywhere in-tree, which I believe is the case,
> > then that is fine by me.
> 
> BTW, are you planning to make the above mentioned driver update
> before or after re-posting enablement patches for Koelsch and/or Lager?
> I ask because I would like to make such patches the basis for
> a patch for Marzen.

I'll try to do so today, after my talk at the ELC :-)

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-04-29 13:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  6:54 [PATCH/RFC] serial: sh-sci: Add device tree support for r8a7779 Simon Horman
2014-04-24 23:33 ` Laurent Pinchart
2014-04-25  0:26   ` Simon Horman
2014-04-25  7:05     ` Laurent Pinchart
2014-04-25  7:11       ` Geert Uytterhoeven
2014-04-28  0:03         ` Simon Horman
2014-04-28  0:08           ` Laurent Pinchart
2014-04-28  1:13             ` Simon Horman
2014-04-28  7:07               ` Simon Horman
2014-04-29 13:44                 ` Laurent Pinchart [this message]
2014-04-29 21:48                   ` Simon Horman
2014-04-30  0:59                     ` Laurent Pinchart
2014-04-30  1:45                       ` Simon Horman

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=1986104.5bpNkKVN8D@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@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 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).