linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC/PATCH 2/6] serial: sh-sci: Drop the interface clock
Date: Mon, 12 May 2014 20:23:31 +0000	[thread overview]
Message-ID: <2562271.Lvip36Cm4X@avalon> (raw)
In-Reply-To: <1398817906-6023-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Simon,

On Wednesday 30 April 2014 15:43:04 Simon Horman wrote:
> On Wed, Apr 30, 2014 at 02:31:42AM +0200, Laurent Pinchart wrote:
> > As no platform defines an interface clock the SCI driver always fall
> > back to a clock named "peripheral_clk". On SH platform that clock is the
> > base clock for the SCI functional clock and has the same frequency. On
> > ARM platforms that clock doesn't exist, and clk_get() will return the
> > default clock for the device. We can thus make the functional clock
> > mandatory and drop the interface clock.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  .../bindings/serial/renesas,sci-serial.txt         |  4 +-
> >  drivers/tty/serial/sh-sci.c                        | 52 +++++++++--------
> >  2 files changed, 31 insertions(+), 25 deletions(-)
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt
> > b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt index
> > 53e6c17..efc9eda 100644
> > --- a/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt
> > +++ b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt
> > 
> > @@ -26,7 +26,7 @@ Required properties:
> >    - clocks: Must contain a phandle and clock-specifier pair for each
> >      entry in clock-names.
> > -  - clock-names: Must contain "sci_ick" for the SCIx UART interface
> > clock.
> > +  - clock-names: Must contain "fck" for the SCIx UART functional clock.
> 
> I have tested that this patch works on the Koelsch and Lager boards with the
> remainder of the series applied and a fixup for the Lager patch, as noted in
> a response to that patch.
> 
> I have also tested that this patch works on the Marzen board with a modified
> version of my series to enable SCI via DT on that board.
> 
> 
> It was my understanding that this patch would not break existing bindings.
> However, if my reading and testing of this patch correct this patch modifies
> an existing binding, included in v3.14, in an incompatible way. Requiring
> all users of "sci_ick" to be updated to "fck".

You're right. Lack of testing mixed with coding during a 12h flight makes it 
easy to overlook basic issues :-)

> This includes the DT nodes provided for the r8a7790 and r8a7791 which are
> present in v3.15-rc1 and will also be included in v3.15 unless this patch,
> its dependencies and the patches in this series that update the dtsi for
> those SoCs are submitted as fixes for v3.15. (I am aware the nodes in
> question are "disabled" :)
> 
> I would prefer if this change it was done in a way that maintains
> compatibility with the published binding.

I have mixed feelings here. On one hand you're right from a theoretical point 
of view. On the other hand, the bindings are so recent, and the DT nodes are 
marked as "disabled", so I'm pretty sure nobody uses them. It would be a shame 
to have to keep compatibility code around forever in the sh-sci driver, even 
if the code itself wouldn't be too complex. How much do you insist on this ? 
:-)

> Apart from addressing my concern above such an approach would also allow
> patches that enable SCI via DT (using "sci_ick") to be merged independently
> of this driver change. Although I am happy to wait on those if you have a
> strong preference for them to use the updated binding.

I don't have a strong preference here, except that I'd like to drop support 
for the sci_ick clock name completely, which wouldn't play very well with 
adding new users right now :-)

> >  Note: Each enabled SCIx UART should have an alias correctly numbered in
> >  the "aliases" node.
> > 
> > @@ -42,5 +42,5 @@ Example:
> >  		interrupt-parent = <&gic>;
> >  		interrupts = <0 144 IRQ_TYPE_LEVEL_HIGH>;
> >  		clocks = <&mstp2_clks R8A7790_CLK_SCIFA0>;
> > -		clock-names = "sci_ick";
> > +		clock-names = "fck";
> >  	};

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-05-12 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  0:31 [RFC/PATCH 2/6] serial: sh-sci: Drop the interface clock Laurent Pinchart
2014-04-30  6:43 ` Simon Horman
2014-05-12 20:23 ` Laurent Pinchart [this message]
2014-05-13  1:06 ` Simon Horman
2014-05-13  4:06 ` Simon Horman
2014-05-13 11:44 ` 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=2562271.Lvip36Cm4X@avalon \
    --to=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).