linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Zhang Rui <rui.zhang@intel.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v2] thermal: rcar: Add binding docs for new R-Car Gen2 SoCs
Date: Mon, 08 Sep 2014 10:48:37 +0000	[thread overview]
Message-ID: <20140908104835.GB3573@developer> (raw)
In-Reply-To: <CAMuHMdW_BYT8ughx=-j3Y+5Bd1Jkb3An8D=uTNcXa6rU3nfNQg@mail.gmail.com>

Hi Geert,

On Sat, Sep 06, 2014 at 08:10:13PM +0200, Geert Uytterhoeven wrote:
> Hi Eduardo,
> 
> On Sat, Sep 6, 2014 at 6:13 PM, Eduardo Valentin <edubezval@gmail.com> wrote:
> > On Thu, Aug 28, 2014 at 10:12:32AM +0200, Geert Uytterhoeven wrote:
> >>   - r8a7792 (R-Car V2H)
> >>   - r8a7793 (R-Car M2-N)
> >>   - r8a7794 (R-Car E2)
> >>
> >> r8a7791 is now called "R-Car M2-W".
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > I don't have any concerns on this patch and will be adding to my next
> > branch. But before that, I have one simple question. Although the
> 
> Thanks!
> 
> > binding description mention about soc types, the rcar thermal driver do
> > not differentiate soc types, only supports the "renesas,rcar-thermal"
> > compatible.
> >
> > Do you care explaining why we need the soc specific compatibles?
> 
> The reason we also have the SoC-specific values is that we are not
> 100% sure the thermal IP cores in the Renesas R-Car Gen1 and R-Car Gen2
> series are really identical.
> 
> Currently the driver treats all of them the same, but if we ever discover
> a difference, and the driver needs to start distinguishing among different
> versions, we will need to have the SoC-specific values in the DTSes to
> do so.

In this case, wouldn't make sense to find out first the differences
before changing DT documentation?

Otherwise, you may also figure out that there is no difference and
then send a patch to remove the changes you are sending now
(or even removing the -<soc specific> parts).


> 
> I hope this explains our rationale.
> 
> 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

  reply	other threads:[~2014-09-08 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  8:12 [PATCH v2] thermal: rcar: Add binding docs for new R-Car Gen2 SoCs Geert Uytterhoeven
2014-09-06 16:13 ` Eduardo Valentin
2014-09-06 18:10   ` Geert Uytterhoeven
2014-09-08 10:48     ` Eduardo Valentin [this message]
2014-09-08 11:02       ` Geert Uytterhoeven
2014-09-09 14:51 ` Eduardo Valentin

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=20140908104835.GB3573@developer \
    --to=edubezval@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rui.zhang@intel.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).