From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: r8a7791: add ADSP clocks
Date: Mon, 29 Dec 2014 22:13:17 +0000 [thread overview]
Message-ID: <54A1D1FD.7010006@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdWwx3So77Zuz7JrpJbBZe2oKN3YnkZL3m0gUCHZGu6SEg@mail.gmail.com>
On 12/30/2014 12:23 AM, 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.
Oh, OK...
> 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,
Yes, exactly. The driver will cuss loudly but will continue to work.
> or does the whole CPG driver fail?
No.
> I wanted to check that after seeing the RCAN CPG patch, but haven't gotten to it
> yet due to Xmas and NY holidays.
No holidays yet here. There will be long holidays starting from January 1st...
> Gr{oetje,eeting}s,
> Geert
WBR, Sergei
prev parent reply other threads:[~2014-12-29 22:13 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
2014-12-29 22:13 ` Sergei Shtylyov [this message]
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=54A1D1FD.7010006@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).