All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-sh@vger.kernel.org, linus.walleij@linaro.org,
	linux-gpio@vger.kernel.org, magnus.damm@gmail.com,
	horms@verge.net.au, gnurou@gmail.com,
	linux-kernel@vger.kernel.org, kuninori.morimoto.gx@renesas.com
Subject: Re: [PATCH] gpio: gpio-rcar: init at postcore level
Date: Mon, 24 Feb 2014 11:46:34 +0400	[thread overview]
Message-ID: <530AF8DA.8050709@cogentembedded.com> (raw)
In-Reply-To: <530A477C.6070007@codethink.co.uk>

Hello Ben,

On 02/23/2014 11:09 PM, Ben Dooks wrote:
> On 23/02/14 16:37, vladimir.barinov@cogentembedded.com wrote:
>> From: Vladimir Barinov <vladimir.barinov@cogentembedded.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

WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] gpio: gpio-rcar: init at postcore level
Date: Mon, 24 Feb 2014 07:46:34 +0000	[thread overview]
Message-ID: <530AF8DA.8050709@cogentembedded.com> (raw)
In-Reply-To: <1393173467-12240-1-git-send-email-vladimir.barinov@cogentembedded.com>

Hello Ben,

On 02/23/2014 11:09 PM, Ben Dooks wrote:
> On 23/02/14 16:37, vladimir.barinov@cogentembedded.com wrote:
>> From: Vladimir Barinov <vladimir.barinov@cogentembedded.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

  reply	other threads:[~2014-02-24  7:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 16:37 [PATCH] gpio: gpio-rcar: init at postcore level vladimir.barinov
2014-02-23 16:37 ` vladimir.barinov
2014-02-23 16:37 ` vladimir.barinov
2014-02-23 19:09 ` Ben Dooks
2014-02-23 19:09   ` Ben Dooks
2014-02-24  7:46   ` Vladimir Barinov [this message]
2014-02-24  7:46     ` Vladimir Barinov
2014-02-24  2:57 ` Magnus Damm
2014-02-24  2:57   ` Magnus Damm
2014-02-24  7:42   ` Vladimir Barinov
2014-02-24  7:42     ` Vladimir Barinov
2014-02-24  7:55     ` Magnus Damm
2014-02-24  7:55       ` Magnus Damm

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=530AF8DA.8050709@cogentembedded.com \
    --to=vladimir.barinov@cogentembedded.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=gnurou@gmail.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.