Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com
---
Hi,
Here is a first attempt to add device tree support to atmel_serial driver.
RS485 data are not handled for the moment. My feeling is that they should be
added as a generic DT biding set.
On Wed, Sep 28, 2011 at 1:31 PM, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
Right, but your modification was to the MFD core so it's going to affect
other devices...
But only when they start using the newly added functionality. At this
point, it affects nobody except vx855.
Grant,
On Mon, Oct 03, 2011 at 12:00:56PM +0200, Nicolas Ferre wrote:
diff --git a/arch/arm/mach-at91/board-dt.c b/arch/arm/mach-at91/board-dt.c
new file mode 100644
index 000..7bcb9a9
--- /dev/null
+++ b/arch/arm/mach-at91/board-dt.c
@@ -0,0 +1,122 @@
+/*
+ * Setup code for AT91SAM
On Mon, Oct 03, 2011 at 09:40:10AM +0100, Daniel Drake wrote:
On Wed, Sep 28, 2011 at 1:31 PM, Mark Brown
Right, but your modification was to the MFD core so it's going to affect
other devices...
But only when they start using the newly added functionality. At this
point, it affects nobody
On Mon, Oct 03, 2011 at 11:39:47AM +0100, Daniel Drake wrote:
On Mon, Oct 3, 2011 at 11:28 AM, Mark Brown
I'd really expect that if we're adding stuff to the framework then it
should be suitable for random drivers to use.
It is suitable. If other drivers would otherwise run into the data
On Mon, Oct 3, 2011 at 1:16 PM, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
It seems to me like either the IP block is heavily dependant on the core
and shouldn't be split out in the device tree at all (but should instead
be part of the core node) or the IP block is very isolated from
On Mon, Oct 03, 2011 at 01:30:15PM +0100, Daniel Drake wrote:
On Mon, Oct 3, 2011 at 1:16 PM, Mark Brown
It seems to me like either the IP block is heavily dependant on the core
and shouldn't be split out in the device tree at all (but should instead
be part of the core node) or the IP
On Mon, Oct 3, 2011 at 1:40 PM, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
So, I made two suggestions above and it sounds like you want the second
one but you've only responded to the first one without commenting on the
second. My second suggestion was that if the block is
+ devicetree-discuss, lkml
On Mon, 3 Oct 2011, Cousson, Benoit wrote:
But at that time, device tree was not there...
Now, the whole dev_attr stuff will be replaced because device tree is able to
provide the driver any kind of custom information that can be retrieved
directly from the driver
On 10/03/2011 04:51 AM, Nicolas Ferre wrote:
Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com
---
Hi,
Here is a first attempt to add device tree support to atmel_serial driver.
RS485 data are not handled for the moment. My feeling is that they should be
added as a generic DT biding
On 09/02/2011 10:10 AM, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
Add devicetree match table to ahci platform driver for Calxeda Highbank
AHCI controller.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Jeff Garzik jgar...@pobox.com
Cc: linux-...@vger.kernel.org
On Friday 30 September 2011 05:48 PM, Mark Brown wrote:
On Fri, Sep 30, 2011 at 04:39:02PM +0530, Rajendra Nayak wrote:
The regulator-supplies is used to specific the regulator *parent*.
Same as what was earlier passed by using the
supply_regulator field of regulator_init_data structure.
Grant
12 matches
Mail list logo
