All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	linux-clk <linux-clk@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] clk: renesas: rz: Select EXTAL vs USB clock
Date: Mon, 29 Aug 2016 14:53:34 +0000	[thread overview]
Message-ID: <SG2PR06MB1165182DE474D907F38694E98AE10@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdWiPfZq=VgWhFRaQBoazLGSDo3+AB_cUG5hMhPxzypLAA@mail.gmail.com>

Hi Geert,

On Aug 29, 2016, Geert Uytterhoeven wrote:
>> Instead of hard coding EXTAL only, check if EXTAL was specified. If 
>> not, then assume the USB clock is used as the main system clock.
>>
>> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
>
> What's the rationale behind this change?


I'm thinking about beyond Renesas boards. People are making RZ/A1 boards with just the USB clock to save on BOM costs since 384MHz vs 400MHz is not enough of a drop to care about.
And of course, having someone make this kind of selection in the DT is better than forcing them to hack the clock file.



Chris

WARNING: multiple messages have this Message-ID (diff)
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	linux-clk <linux-clk@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] clk: renesas: rz: Select EXTAL vs USB clock
Date: Mon, 29 Aug 2016 14:53:34 +0000	[thread overview]
Message-ID: <SG2PR06MB1165182DE474D907F38694E98AE10@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdWiPfZq=VgWhFRaQBoazLGSDo3+AB_cUG5hMhPxzypLAA@mail.gmail.com>

SGkgR2VlcnQsDQoNCk9uIEF1ZyAyOSwgMjAxNiwgR2VlcnQgVXl0dGVyaG9ldmVuIHdyb3RlOg0K
Pj4gSW5zdGVhZCBvZiBoYXJkIGNvZGluZyBFWFRBTCBvbmx5LCBjaGVjayBpZiBFWFRBTCB3YXMg
c3BlY2lmaWVkLiBJZiANCj4+IG5vdCwgdGhlbiBhc3N1bWUgdGhlIFVTQiBjbG9jayBpcyB1c2Vk
IGFzIHRoZSBtYWluIHN5c3RlbSBjbG9jay4NCj4+DQo+PiBTaWduZWQtb2ZmLWJ5OiBDaHJpcyBC
cmFuZHQgPGNocmlzLmJyYW5kdEByZW5lc2FzLmNvbT4NCj4NCj4gV2hhdCdzIHRoZSByYXRpb25h
bGUgYmVoaW5kIHRoaXMgY2hhbmdlPw0KDQoNCkknbSB0aGlua2luZyBhYm91dCBiZXlvbmQgUmVu
ZXNhcyBib2FyZHMuIFBlb3BsZSBhcmUgbWFraW5nIFJaL0ExIGJvYXJkcyB3aXRoIGp1c3QgdGhl
IFVTQiBjbG9jayB0byBzYXZlIG9uIEJPTSBjb3N0cyBzaW5jZSAzODRNSHogdnMgNDAwTUh6IGlz
IG5vdCBlbm91Z2ggb2YgYSBkcm9wIHRvIGNhcmUgYWJvdXQuDQpBbmQgb2YgY291cnNlLCBoYXZp
bmcgc29tZW9uZSBtYWtlIHRoaXMga2luZCBvZiBzZWxlY3Rpb24gaW4gdGhlIERUIGlzIGJldHRl
ciB0aGFuIGZvcmNpbmcgdGhlbSB0byBoYWNrIHRoZSBjbG9jayBmaWxlLg0KDQoNCg0KQ2hyaXMN
Cg==

  reply	other threads:[~2016-08-29 14:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 19:05 [PATCH] clk: renesas: rz: Select EXTAL vs USB clock Chris Brandt
2016-08-29 13:18 ` Geert Uytterhoeven
2016-08-29 14:53   ` Chris Brandt [this message]
2016-08-29 14:53     ` Chris Brandt
2016-08-29 15:13     ` Geert Uytterhoeven
2016-08-29 15:32       ` Chris Brandt
2016-08-29 15:32         ` Chris Brandt
2016-08-29 15:41         ` Geert Uytterhoeven
2016-08-29 16:04           ` Chris Brandt
2016-08-29 16:04             ` Chris Brandt
2016-08-29 18:39 ` Sergei Shtylyov
2016-08-29 18:41   ` Geert Uytterhoeven
2016-08-30  3:13 ` [PATCH v2] " Chris Brandt
2016-08-30  7:04   ` Simon Horman
2016-08-30  7:06     ` Simon Horman
2016-08-30  7:23   ` Geert Uytterhoeven
2016-08-30 13:31     ` Chris Brandt
2016-08-30 13:31       ` Chris Brandt
2016-09-01 13:10   ` [PATCH v3] " Chris Brandt
2016-09-01 19:21     ` Geert Uytterhoeven
2016-09-01 19:41       ` Chris Brandt
2016-09-01 19:41         ` Chris Brandt
2016-09-02  2:32     ` [PATCH v4] " Chris Brandt
2016-09-02  8:19       ` Geert Uytterhoeven

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=SG2PR06MB1165182DE474D907F38694E98AE10@SG2PR06MB1165.apcprd06.prod.outlook.com \
    --to=chris.brandt@renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.