From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "mirza.krak@gmail.com" <mirza.krak@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"pgaikwad@nvidia.com" <pgaikwad@nvidia.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"mchourasia@nvidia.com" <mchourasia@nvidia.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"pdeschrijver@nvidia.com" <pdeschrijver@nvidia.com>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table]
Date: Wed, 31 Aug 2016 11:28:36 +0000 [thread overview]
Message-ID: <1472642915.31008.32.camel@toradex.com> (raw)
In-Reply-To: <CALw8SCUHjFAr7RT3UCOkZ9W4Uf=nLHr2F3A_DqKiw1q_LOXDrg@mail.gmail.com>
T24gV2VkLCAyMDE2LTA4LTMxIGF0IDExOjQ3ICswMjAwLCBNaXJ6YSBLcmFrIHdyb3RlOg0KPiBJ
J20ganVzdCBjdXJpb3VzIHdoZXJlIHRoYXQgOTIgTUh6IGNhbWUgZnJvbS4gQWNjb3JkaW5nIHRv
IHRoZQ0KPiA+IFRlZ3JhIDINCj4gPiBJbnRlcmZhY2UgRGVzaWduIEd1aWRlIHVwIHRvIDEzMyBN
SHogc2hvdWxkIGFjdHVhbGx5IGJlIHBvc3NpYmxlLg0KPiBUaGUgbWF4aW11bSByYXRlcyBmb3Ig
Ym90aCBUMjAgYW5kIFQzMCBhcmUgdmFsdWVzIHRoYXQgYXJlIHNldCBhcw0KPiBtYXhpbXVtIGlu
IHRoZSBkb3duc3RyZWFtIEw0VCBrZXJuZWwuDQo+IA0KPiBJbiB0ZWdyYTJfY2xvY2tzLmM6DQo+
IFBFUklQSF9DTEsoIm5vciIsICJ0ZWdyYS1ub3IiLCBOVUxMLCA0MiwgMHgxZDAsIDB4MzFFLCA5
MjAwMDAwMCwNCj4gbXV4X3BsbHBfcGxsY19wbGxtX2Nsa20sIE1VWCB8IERJVl9VNzEpLCAvKiBy
ZXF1aXJlcyBtaW4gdm9sdGFnZSAqLw0KPiANCj4gQW5kIGluIHRlZ3JhM19jbG9ja3MuYw0KPiBQ
RVJJUEhfQ0xLKCJub3IiLCAidGVncmEtbm9yIiwgTlVMTCwgNDIsIDB4MWQwLCAxMjcwMDAwMDAs
DQo+IG11eF9wbGxwX3BsbGNfcGxsbV9jbGttLCBNVVggfCBESVZfVTcxKSwgLyogcmVxdWlyZXMg
bWluIHZvbHRhZ2UgKi8NCj4gDQo+IEkgbG9va2VkIHVwIHRoZSBjb21taXQgaW4gdGhlIGRvd25z
dHJlYW0ga2VybmVsIHRoYXQgYWRkZWQgdGhlICJub3IiDQo+IGNsb2NrLCBpdCBkb2VzIG5vdCBt
ZW50aW9uIHJlYXNvbiBiZWhpbmQgdGhlIG1heGltYWwgcmF0ZXMuIEF1dGhvcg0KPiB3YXMNCj4g
TWFub2ogQ2hvdXJhc2lhLCBhZGRlZCBoaW0gdG8gQ0MuDQoNCkxldCdzIHNlZSB3aGV0aGVyIHdl
IGRvIGdldCBhbnkgZmVlZGJhY2sgZnJvbSBoaW0uDQoNCk5vbmV0aGVsZXNzIGl0IG1heSBiZSBn
b29kIHRvIGFkZCB0aGlzIGluZm9ybWF0aW9uIHRvIHRoZSBjb21taXQNCm1lc3NhZ2Ugc28gc2hv
dWxkIHNvbWVib2R5IGV2ZXIgZmVlbCB0aGUgc2FtZSBjdXJpb3NpdHkgbGlrZSBJIGRpZCBoZQ0K
d291bGQgYXQgbGVhc3Qga25vdyB3aGVyZSBpdCBpbml0aWFsbHkgY2FtZSBmcm9tLg0KDQo+IEkg
YWN0dWFsbHkgZG8gbm90IGhhdmUgdGhlIFRlZ3JhMiBJbnRlcmZhY2UgRGVzaWduIEd1aWRlLCBk
byBub3Qga25vdw0KPiBpZiBJIGNhbiBnZXQgYWNjZXNzIHRvIGl0Lg0KDQpJIGd1ZXNzIHRoYXQg
b25lIGlzIG9ubHkgYWNjZXNzaWJsZSB1bmRlciBOREEuIFdlIGNvdWxkIG9mIGNvdXJzZSB0cnkN
CnRvIGdldCBvbmUgaW4gcGxhY2UgZm9yIHlvdSBidXQgSSBjYW4ndCBwcm9taXNlIHlvdSBhbnl0
aGluZy4NCg0KPiBCZXN0IFJlZ2FyZHMNCj4gTWlyemENCg0KVGhhbmtzLCBNaXJ6YQ==
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "mirza.krak@gmail.com" <mirza.krak@gmail.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"pgaikwad@nvidia.com" <pgaikwad@nvidia.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"mchourasia@nvidia.com" <mchourasia@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"pdeschrijver@nvidia.com" <pdeschrijver@nvidia.com>,
"linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.i>
Subject: Re: [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table]
Date: Wed, 31 Aug 2016 11:28:36 +0000 [thread overview]
Message-ID: <1472642915.31008.32.camel@toradex.com> (raw)
In-Reply-To: <CALw8SCUHjFAr7RT3UCOkZ9W4Uf=nLHr2F3A_DqKiw1q_LOXDrg@mail.gmail.com>
On Wed, 2016-08-31 at 11:47 +0200, Mirza Krak wrote:
> I'm just curious where that 92 MHz came from. According to the
> > Tegra 2
> > Interface Design Guide up to 133 MHz should actually be possible.
> The maximum rates for both T20 and T30 are values that are set as
> maximum in the downstream L4T kernel.
>
> In tegra2_clocks.c:
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 0x31E, 92000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> And in tegra3_clocks.c
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 127000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> I looked up the commit in the downstream kernel that added the "nor"
> clock, it does not mention reason behind the maximal rates. Author
> was
> Manoj Chourasia, added him to CC.
Let's see whether we do get any feedback from him.
Nonetheless it may be good to add this information to the commit
message so should somebody ever feel the same curiosity like I did he
would at least know where it initially came from.
> I actually do not have the Tegra2 Interface Design Guide, do not know
> if I can get access to it.
I guess that one is only accessible under NDA. We could of course try
to get one in place for you but I can't promise you anything.
> Best Regards
> Mirza
Thanks, Mirza
WARNING: multiple messages have this Message-ID (diff)
From: marcel.ziswiler@toradex.com (Marcel Ziswiler)
To: linux-arm-kernel@lists.infradead.org
Subject: [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table]
Date: Wed, 31 Aug 2016 11:28:36 +0000 [thread overview]
Message-ID: <1472642915.31008.32.camel@toradex.com> (raw)
In-Reply-To: <CALw8SCUHjFAr7RT3UCOkZ9W4Uf=nLHr2F3A_DqKiw1q_LOXDrg@mail.gmail.com>
On Wed, 2016-08-31 at 11:47 +0200, Mirza Krak wrote:
> I'm just curious where that 92 MHz came from. According to the
> > Tegra 2
> > Interface Design Guide up to 133 MHz should actually be possible.
> The maximum rates for both T20 and T30 are values that are set as
> maximum in the downstream L4T kernel.
>
> In tegra2_clocks.c:
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 0x31E, 92000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> And in tegra3_clocks.c
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 127000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> I looked up the commit in the downstream kernel that added the "nor"
> clock, it does not mention reason behind the maximal rates. Author
> was
> Manoj Chourasia, added him to CC.
Let's see whether we do get any feedback from him.
Nonetheless it may be good to add this information to the commit
message so should somebody ever feel the same curiosity like I did he
would at least know where it initially came from.
> I actually do not have the Tegra2 Interface Design Guide, do not know
> if I can get access to it.
I guess that one is only accessible under NDA. We could of course try
to get one in place for you but I can't promise you anything.
> Best Regards
> Mirza
Thanks, Mirza
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "mirza.krak@gmail.com" <mirza.krak@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"pgaikwad@nvidia.com" <pgaikwad@nvidia.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"mchourasia@nvidia.com" <mchourasia@nvidia.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"pdeschrijver@nvidia.com" <pdeschrijver@nvidia.com>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table]
Date: Wed, 31 Aug 2016 11:28:36 +0000 [thread overview]
Message-ID: <1472642915.31008.32.camel@toradex.com> (raw)
In-Reply-To: <CALw8SCUHjFAr7RT3UCOkZ9W4Uf=nLHr2F3A_DqKiw1q_LOXDrg@mail.gmail.com>
On Wed, 2016-08-31 at 11:47 +0200, Mirza Krak wrote:
> I'm just curious where that 92 MHz came from. According to the
> > Tegra 2
> > Interface Design Guide up to 133 MHz should actually be possible.
> The maximum rates for both T20 and T30 are values that are set as
> maximum in the downstream L4T kernel.
>
> In tegra2_clocks.c:
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 0x31E, 92000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> And in tegra3_clocks.c
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 127000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
>
> I looked up the commit in the downstream kernel that added the "nor"
> clock, it does not mention reason behind the maximal rates. Author
> was
> Manoj Chourasia, added him to CC.
Let's see whether we do get any feedback from him.
Nonetheless it may be good to add this information to the commit
message so should somebody ever feel the same curiosity like I did he
would at least know where it initially came from.
> I actually do not have the Tegra2 Interface Design Guide, do not know
> if I can get access to it.
I guess that one is only accessible under NDA. We could of course try
to get one in place for you but I can't promise you anything.
> Best Regards
> Mirza
Thanks, Mirza
next prev parent reply other threads:[~2016-08-31 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472569308.5703.22.camel@toradex.com>
2016-08-31 7:15 ` [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table] Marcel Ziswiler
2016-08-31 7:15 ` Marcel Ziswiler
2016-08-31 7:15 ` Marcel Ziswiler
2016-08-31 7:15 ` Marcel Ziswiler
2016-08-31 9:47 ` Mirza Krak
2016-08-31 9:47 ` Mirza Krak
2016-08-31 9:47 ` Mirza Krak
2016-08-31 11:28 ` Marcel Ziswiler [this message]
2016-08-31 11:28 ` Marcel Ziswiler
2016-08-31 11:28 ` Marcel Ziswiler
2016-08-31 11:28 ` Marcel Ziswiler
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=1472642915.31008.32.camel@toradex.com \
--to=marcel.ziswiler@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mchourasia@nvidia.com \
--cc=mirza.krak@gmail.com \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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 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.