From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: mach-shmobile: r8a7779: add SATA support
Date: Tue, 19 Feb 2013 18:26:01 +0400 [thread overview]
Message-ID: <51238B79.2080807@cogentembedded.com> (raw)
In-Reply-To: <87ehgdf85y.wl%kuninori.morimoto.gx@renesas.com>
Hello.
On 19-02-2013 4:40, Kuninori Morimoto wrote:
>>>>> static const struct of_dev_auxdata r8a7779_auxdata_lookup[] __initconst
>>>>> = {
>>>>> + OF_DEV_AUXDATA("renesas,rcar-sata", 0xfc600000, "sata_rcar",
>>>>> NULL),
>>>> ??
>>>> Is this settings really required for DT ??
>>> Yes, TTBOMK, it's the last resort measure used in exctly this case.
>> Well, I have to agree with Morimoto-san here. Other vendors may chose
>> to use AUXDATA to map clocks, and I believe it makes sense in the case
>> of adding platform data as a workaround during transition to full DT
>> support. But for simply mapping clocks please follow the same style as
>> we have done so far, which is what Morimoto-san pointed out:
>> CLKDEV_DEV_ID("fc600000.sata_rcar", &mstp_clks[MSTP115]),
>> Also, I don't think SATA is needed as an early device so it should be
>> enough to register it late as a regular platform device. =)
> BTW, Sergei, which branch are you using for R-Car H1 DT booting ?
> I'm not sure detail, but, I guess R-Car H1 DT detection needs
> simon's latest branch.
I noted in the cover letter that the patches are against the 'next' branch.
> If you are using old branch, DT detection will be failed ?
Those old/new branches sound too vague for me.
WBR, Sergei
next prev parent reply other threads:[~2013-02-19 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 22:43 [PATCH 2/4] ARM: mach-shmobile: r8a7779: add SATA support Sergei Shtylyov
2013-02-18 1:23 ` Kuninori Morimoto
2013-02-18 14:07 ` Sergei Shtylyov
2013-02-18 14:21 ` Magnus Damm
2013-02-19 0:40 ` Kuninori Morimoto
2013-02-19 1:26 ` Simon Horman
2013-02-19 14:26 ` Sergei Shtylyov [this message]
2013-02-19 1:25 ` Simon Horman
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=51238B79.2080807@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).