From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: add AT91SAM9X5 dummy configuration variable
Date: Tue, 28 Jun 2011 14:13:39 +0200 [thread overview]
Message-ID: <4E09C573.2030607@atmel.com> (raw)
In-Reply-To: <20110628103549.GG2612@legolas.emea.dhcp.ti.com>
Le 28/06/2011 12:35, Felipe Balbi :
> On Tue, Jun 28, 2011 at 01:35:27PM +0200, Nicolas Ferre wrote:
>> Add this Kconfig variable to ease the submission of this chip support.
>> As this chip/board inclusion is dealayed due to deep consolidation of
>> arm/mach-at91 sources, we include this dummy configuration variable to allow
>> submission of SAM9x5 related drivers in other subsystems.
>
> Why are the drivers even depending on this ? They should be portable
> enough. Can you share a few drivers so we have a look ?
Yes sure. The dependence is only on the Kconfig side: I plan to make
some drivers dependent on this configuration variable.
The goal is to submit the final driver addition without having to send
again a correction to the Kconfig after the chip/board support is merged.
This will ease the submission process at the cost of a two lines dummy
patch and will remove interdependence between subsystem trees: it worth
it, is not it?
> IMHO, the whole idea of the consolidation is beyond arch/arm, drivers
> should be affected too.
Yes sure, I also understood like this.
I will not spread ARCH_AT91SAM9X5 ifdef in driver code...
Best regards,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: balbi@ti.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, plagnioj@jcrosoft.com,
avictor.za@gmail.com
Subject: Re: [PATCH] AT91: add AT91SAM9X5 dummy configuration variable
Date: Tue, 28 Jun 2011 14:13:39 +0200 [thread overview]
Message-ID: <4E09C573.2030607@atmel.com> (raw)
In-Reply-To: <20110628103549.GG2612@legolas.emea.dhcp.ti.com>
Le 28/06/2011 12:35, Felipe Balbi :
> On Tue, Jun 28, 2011 at 01:35:27PM +0200, Nicolas Ferre wrote:
>> Add this Kconfig variable to ease the submission of this chip support.
>> As this chip/board inclusion is dealayed due to deep consolidation of
>> arm/mach-at91 sources, we include this dummy configuration variable to allow
>> submission of SAM9x5 related drivers in other subsystems.
>
> Why are the drivers even depending on this ? They should be portable
> enough. Can you share a few drivers so we have a look ?
Yes sure. The dependence is only on the Kconfig side: I plan to make
some drivers dependent on this configuration variable.
The goal is to submit the final driver addition without having to send
again a correction to the Kconfig after the chip/board support is merged.
This will ease the submission process at the cost of a two lines dummy
patch and will remove interdependence between subsystem trees: it worth
it, is not it?
> IMHO, the whole idea of the consolidation is beyond arch/arm, drivers
> should be affected too.
Yes sure, I also understood like this.
I will not spread ARCH_AT91SAM9X5 ifdef in driver code...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-06-28 12:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:35 [PATCH] AT91: add AT91SAM9X5 dummy configuration variable Nicolas Ferre
2011-06-28 11:35 ` Nicolas Ferre
2011-06-28 10:35 ` Felipe Balbi
2011-06-28 10:35 ` Felipe Balbi
2011-06-28 12:13 ` Nicolas Ferre [this message]
2011-06-28 12:13 ` Nicolas Ferre
2011-06-28 12:26 ` Felipe Balbi
2011-06-28 12:26 ` Felipe Balbi
2011-06-28 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-29 9:30 ` Felipe Balbi
2011-06-29 9:30 ` Felipe Balbi
2011-06-29 15:24 ` Nicolas Ferre
2011-06-29 15:24 ` Nicolas Ferre
2011-06-29 15:39 ` Felipe Balbi
2011-06-29 15:39 ` Felipe Balbi
2011-07-02 9:49 ` Arnd Bergmann
2011-07-02 9:49 ` Arnd Bergmann
2011-07-04 9:23 ` Nicolas Ferre
2011-07-04 9:23 ` Nicolas Ferre
2011-07-05 5:32 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 5:32 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 11:25 ` Arnd Bergmann
2011-07-05 11:25 ` Arnd Bergmann
2011-06-28 16:03 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 16:03 ` Jean-Christophe PLAGNIOL-VILLARD
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=4E09C573.2030607@atmel.com \
--to=nicolas.ferre@atmel.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 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.