From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Hiroshi Doyu <hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [v3 1/6] ARM: tegra20: create a DT header defining CLK IDs
Date: Tue, 28 May 2013 16:09:38 -0600 [thread overview]
Message-ID: <51A52B22.6080402@wwwdotorg.org> (raw)
In-Reply-To: <519D35A7.5090102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 05/22/2013 03:16 PM, Stephen Warren wrote:
> On 05/22/2013 10:45 AM, Hiroshi Doyu wrote:
>> Create a header file to define the clock IDs used by the Tegra20 clock
>> binding. Remove the list of definitions from the binding documentation,
>> and refer the reader to the header file.
>>
>> This will allow the same header to be used by both device tree files,
>> and drivers implementing this binding, which guarantees that the two
>> stay in sync. This also makes device trees more readable by using names
>> instead of magic numbers.
>
> I have applied patches 1, 3, 5 to Tegra's for-3.11/deps-for-clk branch,
> merged that into Tegra's for-3.11/dt branch, and then applied patches 2,
> 4, 6 to Tegra's for-3.11/dt branch.
Oops. I actually forgot to apply patches 2, 4, 6 before. I just applied
them. I noticed one issue: The new headers were added to
<dt-bindings/clk/>. However, some other similar files have since shown
up in <dt-bindings/clock/>. Since the latter location better matches the
path-names of the DT bindings themselves, I moved the header files while
applying the patches, and fixed up the usage.
> Once you send the drivers/clk changes that build on top of this, I'll
> create a tag and send a pull request to Mike to pick up the headers so
> he can apply the clk changes.
next prev parent reply other threads:[~2013-05-28 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 16:45 [v3 1/6] ARM: tegra20: create a DT header defining CLK IDs Hiroshi Doyu
[not found] ` <1369241136-21903-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-22 16:45 ` [v3 2/6] ARM: tegra20: convert device tree files to use CLK defines Hiroshi Doyu
2013-05-22 16:45 ` [v3 3/6] ARM: tegra30: create a DT header defining CLK IDs Hiroshi Doyu
2013-05-22 16:45 ` [v3 4/6] ARM: tegra30: convert device tree files to use CLK defines Hiroshi Doyu
2013-05-22 16:45 ` [v3 5/6] ARM: tegra114: create a DT header defining CLK IDs Hiroshi Doyu
2013-05-22 16:45 ` [v3 6/6] ARM: tegra114: convert device tree files to use CLK defines Hiroshi Doyu
2013-05-22 21:16 ` [v3 1/6] ARM: tegra20: create a DT header defining CLK IDs Stephen Warren
[not found] ` <519D35A7.5090102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-28 22:09 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-15 8:43 [v3 0/6] ARM: tegra: convert device tree files to use CLK defines Hiroshi Doyu
2013-02-15 8:43 ` [v3 1/6] ARM: tegra20: create a DT header defining CLK IDs Hiroshi Doyu
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=51A52B22.6080402@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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