On Thu, Sep 15, 2011 at 04:50:35PM -0600, Grant Likely wrote:
> We've got two competing approaches here. For reg and interrupts, the
> proposal on the table that we talked about at LPC is to do reg-names
> and interrupts-names so as to preserve the existing semantics of the
> reg and interrupts p
On Thu, Sep 15, 2011 at 02:54:16PM +0100, Mark Brown wrote:
> On Thu, Sep 15, 2011 at 04:52:05PM +0530, Rajendra Nayak wrote:
>
> > regulator = <®ulator1>,<®ulator2>;
> > regulator-names = "supply1","supply2";
> > };
>
> This syntax is really painful - we're relying on
On Thu, Sep 15, 2011 at 04:52:02PM +0530, Rajendra Nayak wrote:
> The helper routine defined here (of_get_fixed_voltage_config) can
> be used to extract information about fixed regulators (which are not
> software controlable) from device tree.
>
> Add documenation about additional bindings for fi
On Thu, Sep 15, 2011 at 04:52:01PM +0530, Rajendra Nayak wrote:
> Modify the twl regulator driver to extract the regulator_init_data from
> device tree when passed, instead of getting it through platform_data
> structures (on non-DT builds)
>
> Signed-off-by: Rajendra Nayak
> ---
> drivers/regul
On Thu, Sep 15, 2011 at 02:46:18PM +0100, Mark Brown wrote:
> On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
>
> > +Required properties:
> > +- compatible: Must be "regulator","ti,twl-reg";
>
> I'd expect listings for the specific chips too.
>
> > + xyz-regulator: regulator@0
On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
> Pass regulator_init_data information for omap4sdp from device tree so the
> regulator driver can then use the regulator helper
> routine to extract and use them during the driver probe().
>
> Add documentation for TWL regulator spec
On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
> The helper routine is meant to be used by regulator drivers
> to extract the regulator_init_data structure passed from device tree.
> 'consumer_supplies' which is part of regulator_init_data is not extracted
> as the regulator consum
On 09/15/2011 06:21 AM, Rajendra Nayak wrote:
> The helper routine is meant to be used by regulator drivers
> to extract the regulator_init_data structure passed from device tree.
> 'consumer_supplies' which is part of regulator_init_data is not extracted
> as the regulator consumer mappings are pa
On 09/15/2011 08:44 AM, Mark Brown wrote:
> On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
>
>> .../devicetree/bindings/regulator/regulator.txt| 37 +
>> drivers/of/Kconfig |6 ++
>> drivers/of/Makefile
Standarize and document the FPGA nodes used on Freescale QorIQ reference
boards. There are different kinds of FPGAs used on the boards, but
only two are currently standard: "pixis", "ngpixis", and "qixis". Although
there are minor differences among the boards that have one kind of FPGA, most
of t
Kumar Gala wrote:
>> >compatible = "fsl,p3060qds-fpga", "fsl,fpga-qixis";
> Right, I pulled those bits out of your patch.
I was hoping you'd notice that in v3 of my patch, I changed fsl,p3060qds-qixis
to fsl,p3060qds-fpga. I think
"fsl,p3060qds-qixis", "fsl,fpga-qixis";
looks kinda
On Sep 15, 2011, at 12:51 PM, Timur Tabi wrote:
> Gala Kumar-B11780 wrote:
>> I pulling the p3060qds bit out so drop that change from next patch.
>>
>
> Ok, I'm thinking it should look like this:
>
> compatible = "fsl,p3060qds-fpga", "fsl,fpga-qixis";
Right, I pulled those bits out of y
Gala Kumar-B11780 wrote:
> I pulling the p3060qds bit out so drop that change from next patch.
>
Ok, I'm thinking it should look like this:
compatible = "fsl,p3060qds-fpga", "fsl,fpga-qixis";
--
Timur Tabi
Linux kernel developer at Freescale
___
Benoit,
On 09/15/2011 08:52 AM, Cousson, Benoit wrote:
> On 9/15/2011 3:11 PM, Rob Herring wrote:
>> Benoit,
>>
>> On 09/15/2011 05:07 AM, Cousson, Benoit wrote:
>>> Hi Rob,
>>>
>>> On 9/15/2011 9:55 AM, Thomas Abraham wrote:
Hi Rob,
On 14 September 2011 22:01, Rob Herring wrote:
Kumar Gala wrote:
> What happened to looking at pixis vs ngpixis ?
Doh, I knew I was forgetting something.
--
Timur Tabi
Linux kernel developer at Freescale
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.o
On Sep 14, 2011, at 4:42 PM, Timur Tabi wrote:
> Standarize and document the FPGA nodes used on Freescale QorIQ reference
> boards. There are different kinds of FPGAs used on the boards, but
> only two are currently standard: "pixis" and "qixis". Although there are
> minor differences among the
On Thu, Sep 15, 2011 at 11:39:51PM +0800, Shawn Guo wrote:
> Hi Ben,
>
> Hopefully, you can pick up this version.
ok, will do it for the weekend.
> Thanks.
>
> Changes since v2:
> * Drop HS-I2C from binding document fsl-imx-i2c.txt
>
> Changes since v1:
> * Fix a couple of typo in fsl-imx-i
It adds device tree probe support for i2c-imx driver.
Signed-off-by: Shawn Guo
Cc: Grant Likely
Cc: Darius Augulis
Cc: Ben Dooks
Acked-by: Grant Likely
---
.../devicetree/bindings/i2c/fsl-imx-i2c.txt| 18 ++
drivers/i2c/busses/i2c-imx.c | 25
The init/exit hooks in platform data are being used nowhere, so can
be removed.
Signed-off-by: Shawn Guo
Cc: Darius Augulis
Cc: Ben Dooks
Acked-by: Grant Likely
Acked-by: Sascha Hauer
---
arch/arm/plat-mxc/include/mach/i2c.h |4
drivers/i2c/busses/i2c-imx.c | 21 +++---
Hi Ben,
Hopefully, you can pick up this version.
Thanks.
Changes since v2:
* Drop HS-I2C from binding document fsl-imx-i2c.txt
Changes since v1:
* Fix a couple of typo in fsl-imx-i2c.txt
Shawn Guo (2):
i2c-imx: remove init/exit hooks from platform data
i2c-imx: add device tree pr
On Thu, Sep 15, 2011 at 04:52:07PM +0530, Rajendra Nayak wrote:
> of_regulator_register_devices() registers all regulators
> as platform devices. Use this to register all twl regulators
> from the twl driver probe.
Regulators can be devices of any type, not just platform devices.
> drivers/mfd/t
On Thu, Sep 15, 2011 at 04:52:06PM +0530, Rajendra Nayak wrote:
> +#ifdef CONFIG_OF
> + struct device_node *node;
> + node = of_get_regulator(dev, id);
> + if (!node)
> + goto out;
> + list_for_each_entry(rdev, ®ulator_list, list)
> + if (node == rdev->node)
On Thu, Sep 15, 2011 at 04:52:05PM +0530, Rajendra Nayak wrote:
> regulator = <®ulator1>,<®ulator2>;
> regulator-names = "supply1","supply2";
> };
This syntax is really painful - we're relying on keeping two arrays in
sync which isn't good for legibility or robus
On 9/15/2011 3:11 PM, Rob Herring wrote:
Benoit,
On 09/15/2011 05:07 AM, Cousson, Benoit wrote:
Hi Rob,
On 9/15/2011 9:55 AM, Thomas Abraham wrote:
Hi Rob,
On 14 September 2011 22:01, Rob Herring wrote:
From: Rob Herring
This adds gic initialization using device tree data. The initializa
On Thu, Sep 15, 2011 at 04:52:03PM +0530, Rajendra Nayak wrote:
> Modify the fixed regulator driver to extract fixed_voltage_config from
> device tree when passed, instead of getting it through platform_data
> structures (on non-DT builds)
The code you added in the previous patch should be part of
On Thu, Sep 15, 2011 at 04:52:02PM +0530, Rajendra Nayak wrote:
> .../devicetree/bindings/regulator/regulator.txt| 19
> drivers/of/of_regulator.c | 31
>
> include/linux/of_regulator.h |7
> 3 file
On Wed, Sep 14, 2011 at 11:31:35AM -0500, Rob Herring wrote:
> From: Rob Herring
>
> This series introduces of_irq_init to scan the device tree for interrupt
> controller nodes and call their init functions in proper order. The GIC
> init function is then called from this function. The platform c
On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
> +Required properties:
> +- compatible: Must be "regulator","ti,twl-reg";
I'd expect listings for the specific chips too.
> + xyz-regulator: regulator@0 {
> + compatible = "regulator","ti,twl-reg";
> + t
On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
> .../devicetree/bindings/regulator/regulator.txt| 37 +
> drivers/of/Kconfig |6 ++
> drivers/of/Makefile|1 +
> drivers/of/of_regulator.c
On Thu, Sep 15, 2011 at 04:51:58PM +0530, Rajendra Nayak wrote:
> The parameters to set_consumer_device_supply() can be considered
> invalid (and hence it could return -EINVAL) if nether consumer_dev nor
> consumer_dev_name are passed, not when *both* are passed.
> Signed-off-by: Rajendra Nayak
On Thu, Sep 15, 2011 at 04:51:57PM +0530, Rajendra Nayak wrote:
> The TWL driver seems to set the default .valid_modes_mask to
> (REGULATOR_MODE_NORMAL | REGULATOR_MODE_STANDBY) and .valid_ops_mask
> to (REGULATOR_CHANGE_VOLTAGE | REGULATOR_CHANGE_MODE |
> REGULATOR_CHANGE_STATUS)
> for all the re
Benoit,
On 09/15/2011 05:07 AM, Cousson, Benoit wrote:
> Hi Rob,
>
> On 9/15/2011 9:55 AM, Thomas Abraham wrote:
>> Hi Rob,
>>
>> On 14 September 2011 22:01, Rob Herring wrote:
>>> From: Rob Herring
>>>
>>> This adds gic initialization using device tree data. The initialization
>>> functions are
On 9/15/2011 2:51 PM, Russell King - ARM Linux wrote:
On Thu, Sep 15, 2011 at 02:28:06PM +0200, Cousson, Benoit wrote:
The HW specs is obviously counting the IRQ number at the GIC interface.
That offset is not known outside the MPUSS. Please have a look at the
OMAP4430 TRM p4761 (NDA vM version)
On 09/15/2011 02:55 AM, Thomas Abraham wrote:
> Hi Rob,
>
> On 14 September 2011 22:01, Rob Herring wrote:
>> From: Rob Herring
>>
>> This adds gic initialization using device tree data. The initialization
>> functions are intended to be called by a generic OF interrupt
>> controller parsing fun
On Thu, Sep 15, 2011 at 02:28:06PM +0200, Cousson, Benoit wrote:
> The HW specs is obviously counting the IRQ number at the GIC interface.
> That offset is not known outside the MPUSS. Please have a look at the
> OMAP4430 TRM p4761 (NDA vM version).
As far as I know, I have no access to that. I
On 9/15/2011 12:29 PM, Russell King - ARM Linux wrote:
On Thu, Sep 15, 2011 at 12:07:25PM +0200, Cousson, Benoit wrote:
On OMAP4 the SoC interrupts external to the MPU (SPI) have an offset of
32. Only the internal PPI are between 0 and 31.
SGIs are 0 to 15, PPIs are 16 to 31, and SPIs are 32+
On Thu, Sep 15, 2011 at 08:32:02AM -0300, Benjamin Herrenschmidt wrote:
> On Wed, 2011-08-24 at 15:41 +0100, Jamie Iles wrote:
>
> > + chosen {
> > + bootargs = "console=ttyS0,115200 earlyprintk loglevel=9
> > root=ubi0:rootfs rw rootfstype=ubifs ubi.mtd=5,2048";
> > + linux
On Wed, 2011-08-24 at 15:41 +0100, Jamie Iles wrote:
> + chosen {
> + bootargs = "console=ttyS0,115200 earlyprintk loglevel=9
> root=ubi0:rootfs rw rootfstype=ubifs ubi.mtd=5,2048";
> + linux,stdout-path = &uart0;
> + };
Hrm... we don't normally put the bootargs i
The TWL driver seems to set the default .valid_modes_mask to
(REGULATOR_MODE_NORMAL | REGULATOR_MODE_STANDBY) and .valid_ops_mask
to (REGULATOR_CHANGE_VOLTAGE | REGULATOR_CHANGE_MODE | REGULATOR_CHANGE_STATUS)
for all the registered regulators.
There is no need for all the board files to pass this
The helper routine is meant to be used by regulator drivers
to extract the regulator_init_data structure passed from device tree.
'consumer_supplies' which is part of regulator_init_data is not extracted
as the regulator consumer mappings are passed through DT differently,
implemented in subsequent
With device tree, the consumer regulator mapping is deferred till
a regulator_get is called from the corresponding device driver,
instead of being done during regulator_register.
This avoids a complete scan of all DT nodes to identify consumers
for all regulators.
Devices can assocaite with one or
of_regulator_register_devices() registers all regulators
as platform devices. Use this to register all twl regulators
from the twl driver probe.
Signed-off-by: Rajendra Nayak
---
drivers/mfd/twl-core.c |3 +++
drivers/of/of_regulator.c| 30 ++
include/
Modify the fixed regulator driver to extract fixed_voltage_config from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Signed-off-by: Rajendra Nayak
---
drivers/regulator/fixed.c | 20 +++-
1 files changed, 19 insertions(+), 1
Pass regulator_init_data information for omap4sdp from device tree so the
regulator driver can then use the regulator helper
routine to extract and use them during the driver probe().
Add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak
---
.../bindings/regulator
Pass the fixed voltage regulator information for
omap4panda board from device tree.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-panda.dts | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
b/arch/arm/boot/dts/omap4-
The helper routine defined here (of_get_fixed_voltage_config) can
be used to extract information about fixed regulators (which are not
software controlable) from device tree.
Add documenation about additional bindings for fixed
regulators that can be passed through DT.
Signed-off-by: Rajendra Nay
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Signed-off-by: Rajendra Nayak
---
drivers/regulator/twl-regulator.c | 28 +---
1 files changed, 25
Hi Grant, Mark,
This RFC is an attempt to move the regulator mappings from
board files into device tree for OMAP. In the process I have
defined some helper routines for regulators and defined
the bindings for these.
The patches are based on top of Benoit's series which adds
DT support for i2c and
The parameters to set_consumer_device_supply() can be considered
invalid (and hence it could return -EINVAL) if nether consumer_dev nor
consumer_dev_name are passed, not when *both* are passed.
Signed-off-by: Rajendra Nayak
---
drivers/regulator/core.c |2 +-
1 files changed, 1 insertions(+)
Device nodes in DT can associate themselves with one or more
regulators by providing a list of phandles (to regulator nodes)
and corresponding supply names.
For Example:
devicenode: node@0x0 {
...
...
regulator = <®ulator1>,<®ulator2>;
On Wednesday 14 September 2011, Rob Herring wrote:
> From: Rob Herring
>
> This adds gic initialization using device tree data. The initialization
> functions are intended to be called by a generic OF interrupt
> controller parsing function once the right pieces are in place.
>
> PPIs are handle
On Wednesday 14 September 2011, Rob Herring wrote:
> From: Rob Herring
>
> of_irq_init will scan the devicetree for matching interrupt controller
> nodes. Then it calls an initialization function for each found controller
> in the proper order with parent nodes initialized before child nodes.
>
On Thu, Sep 15, 2011 at 12:07:25PM +0200, Cousson, Benoit wrote:
> On OMAP4 the SoC interrupts external to the MPU (SPI) have an offset of
> 32. Only the internal PPI are between 0 and 31.
SGIs are 0 to 15, PPIs are 16 to 31, and SPIs are 32+ - that's the
numbering given to us by the GIC.
> The
Hi Rob,
On 9/15/2011 9:55 AM, Thomas Abraham wrote:
Hi Rob,
On 14 September 2011 22:01, Rob Herring wrote:
From: Rob Herring
This adds gic initialization using device tree data. The initialization
functions are intended to be called by a generic OF interrupt
controller parsing function once
Hi,
On Wed, Sep 14, 2011 at 09:46:29AM -0600, Grant Likely wrote:
> On Wed, Sep 14, 2011 at 02:57:13PM +0100, Dave Martin wrote:
[...]
> > + of_property_read_u32(dp, "bus-width", bus_width);
>
> Shouldn't this be '&bus_width'?
On Wed, Sep 14, 2011 at 11:12:57PM +0400, Sergei Shtylyov wrote:
On Wed, Sep 14, 2011 at 11:31:35AM -0500, Rob Herring wrote:
> From: Rob Herring
>
> This series introduces of_irq_init to scan the device tree for interrupt
> controller nodes and call their init functions in proper order. The GIC
> init function is then called from this function. The platform c
On Thu, Sep 08, 2011 at 10:43:39AM +0100, Pawel Moll wrote:
> This patch adds Device Tree binding ("arm,versatile-i2c") and
> basic support (bus population) to versatile-i2c driver.
what happens when !CONFIG_OF ?
> Cc: Russell King
> Signed-off-by: Pawel Moll
> ---
> drivers/i2c/busses/i2c-ve
On Wed, Aug 24, 2011 at 03:41:43PM +0100, Jamie Iles wrote:
> This series adds support for Picochip picoXcell (PC3X2 and PC3X3)
> ARM1176JZ-S based devices. This is a device tree only platform and
> currently supports interrupt controllers and UARTs.
>
> This series is based off of Grant's device
Hi Rob,
On 14 September 2011 22:01, Rob Herring wrote:
> From: Rob Herring
>
> This adds gic initialization using device tree data. The initialization
> functions are intended to be called by a generic OF interrupt
> controller parsing function once the right pieces are in place.
>
> PPIs are ha
On Tue, Sep 13, 2011 at 09:46:03AM +0530, Thomas Abraham wrote:
> This patchset adds device tree support for Samsung's I2C driver.
I've applied these after a brief review. I'll give them a better
review before the weekend.
___
devicetree-discuss mailing
60 matches
Mail list logo
