From: jonathanh@nvidia.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/6] clk: tegra: add TEGRA30_CLK_NOR to init table
Date: Thu, 3 Nov 2016 13:45:55 +0000 [thread overview]
Message-ID: <cf378096-26ca-33d2-2b51-a388aa080b3b@nvidia.com> (raw)
In-Reply-To: <1477576872-2665-3-git-send-email-mirza.krak@gmail.com>
On 27/10/16 15:01, Mirza Krak wrote:
> From: Mirza Krak <mirza.krak@gmail.com>
>
> Add TEGRA30_CLK_NOR to init table and set default rate to 127 MHz which
> is max rate.
>
> The maximum rate value of 127 MHz is pulled from the downstream L4T
> kernel.
>
> Signed-off-by: Mirza Krak <mirza.krak@gmail.com>
> Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> Tested-on: Colibri T20/T30 on EvalBoard V3.x and GMI-Memory Board
Acked-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-11-03 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 14:01 [PATCH V3 0/6] Add support for Tegra GMI bus controller Mirza Krak
2016-10-27 14:01 ` [PATCH V3 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table Mirza Krak
2016-11-03 10:06 ` Jon Hunter
2016-11-03 12:26 ` Mirza Krak
2016-11-03 12:30 ` Mirza Krak
2016-11-03 13:45 ` Jon Hunter
2016-11-03 13:45 ` Jon Hunter
2016-10-27 14:01 ` [PATCH V3 2/6] clk: tegra: add TEGRA30_CLK_NOR " Mirza Krak
2016-11-03 13:45 ` Jon Hunter [this message]
2016-10-27 14:01 ` [PATCH V3 3/6] dt/bindings: Add bindings for Tegra GMI controller Mirza Krak
2016-10-31 5:29 ` Rob Herring
2016-10-27 14:01 ` [PATCH V3 4/6] ARM: tegra: Add Tegra30 GMI support Mirza Krak
2016-11-03 10:15 ` Jon Hunter
2016-10-27 14:01 ` [PATCH V3 5/6] ARM: tegra: Add Tegra20 " Mirza Krak
2016-10-27 17:09 ` kbuild test robot
2016-10-27 18:55 ` Mirza Krak
2016-11-03 10:29 ` Jon Hunter
2016-10-27 14:01 ` [PATCH V3 6/6] bus: Add support for Tegra Generic Memory Interface Mirza Krak
2016-11-03 10:51 ` Jon Hunter
2016-11-03 13:08 ` Mirza Krak
2016-11-03 13:50 ` Jon Hunter
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=cf378096-26ca-33d2-2b51-a388aa080b3b@nvidia.com \
--to=jonathanh@nvidia.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).