devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Simon Horman <horms@verge.net.au>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Russell King <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: shmobile: r8a7791: add ADSP clocks
Date: Mon, 29 Dec 2014 22:23:44 +0100	[thread overview]
Message-ID: <CAMuHMdWwx3So77Zuz7JrpJbBZe2oKN3YnkZL3m0gUCHZGu6SEg@mail.gmail.com> (raw)
In-Reply-To: <54A1BABF.5070208@cogentembedded.com>

Hi Sergei,

On Mon, Dec 29, 2014 at 9:34 PM, Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> On 12/29/2014 11:24 PM, Geert Uytterhoeven wrote:
>
>>> --- renesas.orig/include/dt-bindings/clock/r8a7791-clock.h
>>> +++ renesas/include/dt-bindings/clock/r8a7791-clock.h
>
>
>>> -#define R8A7791_CLK_RCAN               9
>>> +#define R8A7791_CLK_ADSP               9
>>> +#define R8A7791_CLK_RCAN               10
>
>> R8A7791_CLK_RCAN is changed?
>
>    Yes. It shouldn't be?

All definitions in include/dt-bindings/ are part of the DT ABI, and cannot be
changed without breaking the DT binding.

Hence when adding new entries, they must be added at the end of the list,
using a new available value.

Apart from that, what happens if you boot a new DTS on a kernel with an old
clk-rcar-gen2 driver that doesn't know about the new CPG clock?
Does it just fail to initialize and find that single clock, or does
the whole CPG
driver fail?
I wanted to check that after seeing the RCAN CPG patch, but haven't gotten to it
yet due to Xmas and NY holidays.

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-12-29 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 20:19 [PATCH] ARM: shmobile: r8a7791: add ADSP clocks Sergei Shtylyov
2014-12-29 20:24 ` Geert Uytterhoeven
2014-12-29 20:34   ` Sergei Shtylyov
2014-12-29 21:23     ` Geert Uytterhoeven [this message]
2014-12-29 22:13       ` Sergei Shtylyov

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=CAMuHMdWwx3So77Zuz7JrpJbBZe2oKN3YnkZL3m0gUCHZGu6SEg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=horms@verge.net.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).