public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris BREZILLON <b.brezillon@overkiz.com>
To: Mark Rutland <mark.rutland@arm.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv2 1/8] ARM: at91: Add at91sam9rl DT SoC support
Date: Wed, 19 Feb 2014 18:28:56 +0100	[thread overview]
Message-ID: <5304E9D8.7090609@overkiz.com> (raw)
In-Reply-To: <20140219170020.GA25079@e106331-lin.cambridge.arm.com>

Hi Mark,

On 19/02/2014 18:00, Mark Rutland wrote:
> On Wed, Feb 19, 2014 at 03:32:24PM +0000, Alexandre Belloni wrote:
>> This adds preliminary DT support for the at91sam9rl.
>>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> ---
>>   arch/arm/boot/dts/at91sam9rl.dtsi | 628 ++++++++++++++++++++++++++++++++++++++
>>   arch/arm/mach-at91/at91sam9rl.c   |  16 +
>>   2 files changed, 644 insertions(+)
>>   create mode 100644 arch/arm/boot/dts/at91sam9rl.dtsi
>   
> [...]
>
>> +                       tcb0: timer@fffa0000 {
>> +                               compatible = "atmel,at91rm9200-tcb";
>> +                               reg = <0xfffa0000 0x100>;
>> +                               interrupts = <16 IRQ_TYPE_LEVEL_HIGH 0
>> +                                             17 IRQ_TYPE_LEVEL_HIGH 0
>> +                                             18 IRQ_TYPE_LEVEL_HIGH 0>;
>> +                       };
> Nit: please bracket list entries individually. Also for other list
> properties like reg and (*-)gpio(s).
>
> [...]
>
>> +                       adc0: adc@fffd0000 {
>> +                               compatible = "atmel,at91sam9260-adc";
>> +                               reg = <0xfffd0000 0x100>;
>> +                               interrupts = <20 IRQ_TYPE_LEVEL_HIGH 0>;
>> +                               atmel,adc-use-external-triggers;
>> +                               atmel,adc-channels-used = <0xf>;
>> +                               atmel,adc-vref = <3300>;
>> +                               atmel,adc-num-channels = <4>;
>> +                               atmel,adc-startup-time = <15>;
>> +                               atmel,adc-channel-base = <0x30>;
>> +                               atmel,adc-drdy-mask = <0x10000>;
>> +                               atmel,adc-status-register = <0x1c>;
>> +                               atmel,adc-trigger-register = <0x04>;
>> +                               atmel,adc-res = <8 10>;
>> +                               atmel,adc-res-names = "lowres", "highres";
>> +                               atmel,adc-use-res = "highres";
>> +
>> +                               trigger@0 {
>> +                                       trigger-name = "timer-counter-0";
>> +                                       trigger-value = <0x1>;
>> +                               };
> A unit-address should go with a reg value. Either this needs a reg and
> the parent node needs #address-cells and #size-cells, or the
> unit-address should go, and the names made unique through other means.
>
> [...]
>
>> +                       pinctrl@fffff400 {
>> +                               #address-cells = <1>;
>> +                               #size-cells = <1>;
>> +                               compatible = "atmel,at91rm9200-pinctrl", "simple-bus";
> NAK. Either this is a atmel,at91rm9200-pinctrl node or a simple-bus. Not
> both; that doesn't make any sense.
>
>> diff --git a/arch/arm/mach-at91/at91sam9rl.c b/arch/arm/mach-at91/at91sam9rl.c
>> index 3651517abedf..d6ee8bb47213 100644
>> --- a/arch/arm/mach-at91/at91sam9rl.c
>> +++ b/arch/arm/mach-at91/at91sam9rl.c
>> @@ -196,6 +196,22 @@ static struct clk_lookup periph_clocks_lookups[] = {
>>          CLKDEV_CON_ID("pioB", &pioB_clk),
>>          CLKDEV_CON_ID("pioC", &pioC_clk),
>>          CLKDEV_CON_ID("pioD", &pioD_clk),
>> +       /* more lookup table for DT entries */
>> +       CLKDEV_CON_DEV_ID("usart", "fffff200.serial", &mck),
>> +       CLKDEV_CON_DEV_ID("usart", "fffb0000.serial", &usart0_clk),
>> +       CLKDEV_CON_DEV_ID("usart", "ffffb400.serial", &usart1_clk),
>> +       CLKDEV_CON_DEV_ID("usart", "ffffb800.serial", &usart2_clk),
>> +       CLKDEV_CON_DEV_ID("usart", "ffffbc00.serial", &usart3_clk),
>> +       CLKDEV_CON_DEV_ID("t0_clk", "fffa0000.timer", &tc0_clk),
>> +       CLKDEV_CON_DEV_ID("t1_clk", "fffa0000.timer", &tc1_clk),
>> +       CLKDEV_CON_DEV_ID("t2_clk", "fffa0000.timer", &tc2_clk),
>> +       CLKDEV_CON_DEV_ID("mci_clk", "fffa4000.mmc", &mmc_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffa8000.i2c", &twi0_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffac000.i2c", &twi1_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffff400.gpio", &pioA_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffff600.gpio", &pioB_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffff800.gpio", &pioC_clk),
>> +       CLKDEV_CON_DEV_ID(NULL, "fffffa00.gpio", &pioD_clk),
> Why can't these clocks be described in the DT?

They're described in the DT in patch 6/8, but we need these static 
definitions
in case the user wants to support both legacy and DT boards.

The at91 CCF based implementation is only compatible with DT, and when 
legacy
board support is enabled this disables the CCF implementation in favor 
of the
old clk implementation.

Best Regards,

Boris
>
> Cheers,
> Mark.


  reply	other threads:[~2014-02-19 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 15:32 [PATCHv2 0/8] Device tree support for the at91sam9rlek Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 1/8] ARM: at91: Add at91sam9rl DT SoC support Alexandre Belloni
2014-02-19 16:01   ` Boris BREZILLON
2014-02-19 16:19     ` Jean-Jacques Hiblot
2014-02-19 17:10       ` Boris BREZILLON
2014-02-20  8:14         ` Nicolas Ferre
2014-02-19 17:00   ` Mark Rutland
2014-02-19 17:28     ` Boris BREZILLON [this message]
2014-02-19 17:31     ` Alexandre Belloni
2014-02-19 17:54       ` Mark Rutland
2014-02-20  8:59         ` Boris BREZILLON
2014-02-20  9:12           ` Nicolas Ferre
2014-02-21 20:04             ` Alexandre Belloni
2014-02-20  8:09     ` Maxime Ripard
2014-02-19 15:32 ` [PATCHv2 2/8] ARM: at91/defconfig: Add the sam9rl to the list of DT-enabled SOCs Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 3/8] ARM: at91: dt: sam9rl: Device Tree for the at91sam9rlek Alexandre Belloni
2014-02-19 17:02   ` Mark Rutland
2014-02-19 15:32 ` [PATCHv2 4/8] ARM: at91: prepare sam9 dt boards transition to common clk Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 5/8] ARM: at91: prepare common clk transition for sam9rl SoCs Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 6/8] ARM: at91/dt: define at91sam9rl clocks Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 7/8] ARM: at91/dt: define main clk frequency of at91sam9rlek Alexandre Belloni
2014-02-19 15:32 ` [PATCHv2 8/8] ARM: at91: switch sam9rl to common clock framework 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=5304E9D8.7090609@overkiz.com \
    --to=b.brezillon@overkiz.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=nicolas.ferre@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