[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <530AF8DA.8050709@cogentembedded.com>
Date: Mon, 24 Feb 2014 11:46:34 +0400
From: Vladimir Barinov <vladimir.barinov@...entembedded.com>
To: Ben Dooks <ben.dooks@...ethink.co.uk>
CC: linux-sh@...r.kernel.org, linus.walleij@...aro.org,
linux-gpio@...r.kernel.org, magnus.damm@...il.com,
horms@...ge.net.au, gnurou@...il.com, linux-kernel@...r.kernel.org,
kuninori.morimoto.gx@...esas.com
Subject: Re: [PATCH] gpio: gpio-rcar: init at postcore level
Hello Ben,
On 02/23/2014 11:09 PM, Ben Dooks wrote:
> On 23/02/14 16:37, vladimir.barinov@...entembedded.com wrote:
>> From: Vladimir Barinov <vladimir.barinov@...entembedded.com>
>>
>> This adds ability to use gpio API at board init_machine level.
>>
>> F.e. it can be used in the following situation.
>> Many reference hardware has onboard switches that selects which
>> periferals
>> to connect to the system. The gpio input state from switches can be used
>> in choosing platform devices runtime in board code instead of
>> ifdefs/defconfig
>> changes.
>
> Firstly, anyone still using platform_devices to describe their
> system needs to be stopped. We cannot go on supporting this when
> our primary boot method is supposed to be device-tree. If we keep
> doing this then we will not get any of the current issues fixed.
Understand. I see that this is not a time for such changes.
Hope that the DT model will take into account such kind of situation in
the future.
>
> Will it impact the devicetree bindings on rcar?
No
Regards,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists