public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] clk: shmobile: Add R8A7740-specific clock support
Date: Thu, 22 May 2014 12:22:09 +0200	[thread overview]
Message-ID: <2463693.SJ3Ug7SyHp@avalon> (raw)
In-Reply-To: <CANqRtoQtPnUcGCg4X9UuNoA6pg6Vd7HWfo30LqD1LOUi+5VC-A@mail.gmail.com>

Hi Magnus,

On Thursday 22 May 2014 09:37:40 Magnus Damm wrote:
> On Thu, May 22, 2014 at 12:41 AM, Laurent Pinchart wrote:
> > On Wednesday 21 May 2014 16:21:26 Ulrich Hecht wrote:
> >> Driver for the R8A7740's clocks that are too specific to be supported by
> >> a generic driver.
> >> 
> >> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > 
> > The implementation looks globally sane to me. There's still quite a few
> > missing clocks, but there's no hurry in adding support for them at the
> > moment. I'd like to get the bindings reviewed by someone outside of our
> > team, but that would require making the CPG documentation (or at least
> > the block diagram) available. Magnus, is there a chance for that to
> > happen ?
> 
> Regarding documentation, as much as I'd like to see this, in practice it
> feels highly unlikely since I'm not in control of the actual data sheet
> distribution policy. I believe Emma Mobile series data sheet are available
> for public download, but the rest of the SoCs are not unfortunately.
> 
> This issue with closed documentation is not specific to r8a7740 though, so
> earlier developed CCF implementations included in upstream like r8a7790,
> r8a7791, r7s72100 and r8a7779 are in the same state as r8a7740.

Yes they are, although the hardware is simpler in those cases, so there's less 
potential issues. I don't have a specific concern here, just a feeling of 
uneasiness coming from publishing DT bindings that can't be properly reviewed 
by someone out of our team. We're too familiar with the hardware to take a 
step back and see the bindings from an external point of view, which is why 
I'd like an external review before committing to any DT binding stability.

There's of course no reason to delay this patch (well, except for all the 
other small comments I've made :-)), but if it were me I would mark the 
corresponding bindings with a big "EXPERIMENTAL" warning.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2014-05-22 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 14:21 [PATCH v3] clk: shmobile: Add R8A7740-specific clock support Ulrich Hecht
2014-05-21 14:31 ` Geert Uytterhoeven
2014-05-21 15:41 ` Laurent Pinchart
2014-05-21 15:50   ` Geert Uytterhoeven
2014-05-22 22:42     ` Laurent Pinchart
2014-05-23  6:47       ` Geert Uytterhoeven
2014-05-22  0:37   ` Magnus Damm
2014-05-22 10:22     ` Laurent Pinchart [this message]
2014-05-22 11:16       ` Magnus Damm
2014-05-22 23:18         ` Laurent Pinchart
2014-05-26  4:30           ` Magnus Damm

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=2463693.SJ3Ug7SyHp@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox