From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC] serial: sh-sci: Add device tree support for r8a7779
Date: Mon, 28 Apr 2014 00:03:14 +0000 [thread overview]
Message-ID: <20140428000314.GK32087@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWB4ZnwyNFXMK_rdCKAMOXt+HRMZKG+j4O-tdfiP_-PLg@mail.gmail.com>
On Fri, Apr 25, 2014 at 09:11:06AM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 25, 2014 at 9:05 AM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> 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.
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
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: Mon, 28 Apr 2014 09:03:14 +0900 [thread overview]
Message-ID: <20140428000314.GK32087@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWB4ZnwyNFXMK_rdCKAMOXt+HRMZKG+j4O-tdfiP_-PLg@mail.gmail.com>
On Fri, Apr 25, 2014 at 09:11:06AM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 25, 2014 at 9:05 AM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> 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.
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC] serial: sh-sci: Add device tree support for r8a7779
Date: Mon, 28 Apr 2014 09:03:14 +0900 [thread overview]
Message-ID: <20140428000314.GK32087@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWB4ZnwyNFXMK_rdCKAMOXt+HRMZKG+j4O-tdfiP_-PLg@mail.gmail.com>
On Fri, Apr 25, 2014 at 09:11:06AM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 25, 2014 at 9:05 AM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
> >> + scif0: serial at 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.
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2014-04-28 0:03 UTC|newest]
Thread overview: 45+ 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 6:54 ` Simon Horman
2014-04-24 6:54 ` Simon Horman
2014-04-24 23:33 ` Laurent Pinchart
2014-04-24 23:33 ` Laurent Pinchart
2014-04-24 23:33 ` Laurent Pinchart
2014-04-25 0:26 ` Simon Horman
2014-04-25 0:26 ` Simon Horman
2014-04-25 0:26 ` Simon Horman
2014-04-25 7:05 ` Laurent Pinchart
2014-04-25 7:05 ` Laurent Pinchart
2014-04-25 7:05 ` Laurent Pinchart
2014-04-25 7:11 ` Geert Uytterhoeven
2014-04-25 7:11 ` Geert Uytterhoeven
2014-04-25 7:11 ` Geert Uytterhoeven
2014-04-28 0:03 ` Simon Horman [this message]
2014-04-28 0:03 ` Simon Horman
2014-04-28 0:03 ` Simon Horman
2014-04-28 0:08 ` Laurent Pinchart
2014-04-28 0:08 ` Laurent Pinchart
2014-04-28 0:08 ` Laurent Pinchart
2014-04-28 1:13 ` Simon Horman
2014-04-28 1:13 ` Simon Horman
2014-04-28 1:13 ` Simon Horman
2014-04-28 7:07 ` Simon Horman
2014-04-28 7:07 ` Simon Horman
2014-04-28 7:07 ` Simon Horman
2014-04-29 13:44 ` Laurent Pinchart
2014-04-29 13:44 ` Laurent Pinchart
2014-04-29 13:44 ` Laurent Pinchart
2014-04-29 21:48 ` Simon Horman
2014-04-29 21:48 ` Simon Horman
2014-04-29 21:48 ` Simon Horman
2014-04-30 0:59 ` Laurent Pinchart
2014-04-30 0:59 ` Laurent Pinchart
2014-04-30 0:59 ` Laurent Pinchart
2014-04-30 1:45 ` Simon Horman
2014-04-30 1:45 ` Simon Horman
2014-04-30 1:45 ` Simon Horman
2014-07-02 4:19 ` [PATCH/RFC] serial: sh-sci: Add device tree support for r8a7778 Simon Horman
2014-07-02 4:19 ` Simon Horman
2014-07-02 4:19 ` Simon Horman
2014-07-02 8:01 ` Laurent Pinchart
2014-07-02 8:01 ` Laurent Pinchart
2014-07-02 8:01 ` 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=20140428000314.GK32087@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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.