From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
<linux-kernel@vger.kernel.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: [PATCH v2 2/3] ARM: at91/dt: add basic dtsi for sama5d2 SoC
Date: Thu, 30 Jul 2015 12:22:33 +0200 [thread overview]
Message-ID: <55B9FAE9.3030906@atmel.com> (raw)
In-Reply-To: <20150729150218.GA6073@piout.net>
Le 29/07/2015 17:02, Alexandre Belloni a écrit :
> Hi,
>
> On 28/07/2015 at 12:25:50 +0200, Nicolas Ferre wrote :
>> +
>> + sdmmc0: sdio-host@a0000000 {
>> + compatible = "atmel,sama5d2-sdhci";
>> + reg = <0xa0000000 0x300>;
>> + interrupts = <31 IRQ_TYPE_LEVEL_HIGH 0>;
>> + clocks = <&sdmmc0_hclk>, <&sdmmc0_gclk>, <&main>;
>> + clock-names = "hclock", "multclk", "baseclk";
>
> Those bindings have not been taken yet. Are you confident enough this
> will go in as-is?
You're right: I'll remove these nodes as well as the ones about the
classD and generated clocks. That way we avoid anticipating on drivers
that are not-so-quite-merged-yet-but-probably-will ;-)
Bye,
>> + status = "disabled";
>> + };
>> +
>
--
Nicolas Ferre
next prev parent reply other threads:[~2015-07-30 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 10:25 [PATCH v2 0/3] ARM: at91: introducing Atmel sama5d2 SoC Nicolas Ferre
2015-07-28 10:25 ` [PATCH v2 1/3] ARM: at91/soc: add basic support for new " Nicolas Ferre
2015-07-29 13:52 ` Alexandre Belloni
2015-07-28 10:25 ` [PATCH v2 2/3] ARM: at91/dt: add basic dtsi for " Nicolas Ferre
2015-07-29 15:02 ` Alexandre Belloni
2015-07-30 10:22 ` Nicolas Ferre [this message]
2015-07-28 10:25 ` [PATCH v2 3/3] ARM: at91/dt: add minimal sama5d2 Xplained board Nicolas Ferre
2015-07-29 13:53 ` Alexandre Belloni
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=55B9FAE9.3030906@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox