* Ryan Mallon wrote:
> On 23/02/12 19:14, Thierry Reding wrote:
> > * Ryan Mallon wrote:
[...]
> >> pwmchip_add should probably verify that the initialisation of the
> >> pwm_chip structure is sane to avoid problems like this.
> >
> > Absolutely. What would be the best response to an invalid struc
* Arnd Bergmann wrote:
> On Thursday 23 February 2012, Thierry Reding wrote:
> > * Arnd Bergmann wrote:
> > > On Wednesday 22 February 2012, Thierry Reding wrote:
> > > > This patch adds helpers to support device tree bindings for the generic
> > > > PWM API. Device tree binding documentation for P
On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -113,5 +113,31 @@
#size-cells =<0>;
ti,hwmods = "i2c3";
};
+
+ mmc1: mmc@1 {
+
On Thursday 23 February 2012 09:01 PM, Mark Brown wrote:
On Thu, Feb 23, 2012 at 05:05:53PM +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)
Th
On Thu, Feb 23, 2012 at 10:22:15PM +0100, Sebastian Andrzej Siewior wrote:
> On 02/23/2012 08:56 PM, Grant Likely wrote:
> >On Wed, Feb 1, 2012 at 11:06 AM, Grant Likely
> >wrote:
> >>On Wed, Feb 1, 2012 at 7:17 AM, Sebastian Andrzej Siewior
> >> wrote:
> >>>* Grant Likely | 2012-01-30 12:58:42
On 02/23/2012 08:56 PM, Grant Likely wrote:
On Wed, Feb 1, 2012 at 11:06 AM, Grant Likely wrote:
On Wed, Feb 1, 2012 at 7:17 AM, Sebastian Andrzej Siewior
wrote:
* Grant Likely | 2012-01-30 12:58:42 [-0700]:
Ugh. This isn't easy. The legacy mapping really needs all the
Feel free to mer
On Thu, Feb 23, 2012 at 2:11 PM, Jason wrote:
> On Thu, Feb 23, 2012 at 01:18:55PM -0700, Grant Likely wrote:
>> On Thu, Feb 23, 2012 at 12:52 PM, Jason Cooper wrote:
>> > Initially, copied guruplug-setup.c and did s/guruplug/dreamplug/g.
>> > Then, switched to SPI based NOR flash.
>> >
>> > Afte
On Thu, Feb 23, 2012 at 01:18:55PM -0700, Grant Likely wrote:
> On Thu, Feb 23, 2012 at 12:52 PM, Jason Cooper wrote:
> > Initially, copied guruplug-setup.c and did s/guruplug/dreamplug/g.
> > Then, switched to SPI based NOR flash.
> >
> > After talking to Arnd Bergman, chose an incremental approa
On Thu, Feb 23, 2012 at 12:52 PM, Jason Cooper wrote:
> Initially, copied guruplug-setup.c and did s/guruplug/dreamplug/g.
> Then, switched to SPI based NOR flash.
>
> After talking to Arnd Bergman, chose an incremental approach to adding
> devicetree support. First, we use the dtb to tell us we
On Wed, Feb 1, 2012 at 11:06 AM, Grant Likely wrote:
> On Wed, Feb 1, 2012 at 7:17 AM, Sebastian Andrzej Siewior
> wrote:
>> * Grant Likely | 2012-01-30 12:58:42 [-0700]:
>>
>>>Ugh. This isn't easy. The legacy mapping really needs all the
>>
>> Feel free to merge this patch. I don't have the ti
Initially, copied guruplug-setup.c and did s/guruplug/dreamplug/g.
Then, switched to SPI based NOR flash.
After talking to Arnd Bergman, chose an incremental approach to adding
devicetree support. First, we use the dtb to tell us we are on the
dreamplug, then we gradually port over drivers.
Driv
This uart is the primary console for the dreamplug. Removed
kirkwood_uart0_init() call from board-dt.c.
Signed-off-by: Jason Cooper
---
Changes from v1
- moved serial config from kirkwood.dtsi to kirkwood-dreamplug.dts as
suggested by Arnd Bergman.
arch/arm/boot/dts/kirkwood-dreampl
This patch series provides initial support for devicetree on kirkwood for the
dreamplug platform. After discussing the approach with Arnd Bergman last week
at ELC, we decided to take an incremental approach to the conversion. First, I
would detect that we were on the dreamplug via the devicetree
On Thu, Feb 23, 2012 at 11:56:46AM -0700, Grant Likely wrote:
> On Thu, Feb 23, 2012 at 9:12 AM, Jason wrote:
> > On Thu, Feb 23, 2012 at 07:34:33AM +, Arnd Bergmann wrote:
> >> On Thursday 23 February 2012, Rob Herring wrote:
> >> > On 02/22/2012 01:18 PM, Jason Cooper wrote:
...
> >> > > +
>
On Thu, Feb 23, 2012 at 07:34:33AM +, Arnd Bergmann wrote:
> On Thursday 23 February 2012, Rob Herring wrote:
> > On 02/22/2012 01:18 PM, Jason Cooper wrote:
>
> > > diff --git a/arch/arm/mach-kirkwood/Kconfig
> > > b/arch/arm/mach-kirkwood/Kconfig
> > > index 7fc603b..6095884 100644
> > > --
Dave,
On Thu, Feb 23, 2012 at 09:16:30AM +, Dave Martin wrote:
> On Wed, Feb 22, 2012 at 11:26:19PM +0100, Uwe Kleine-K?nig wrote:
> > On Wed, Feb 22, 2012 at 07:18:44PM +, Jason Cooper wrote:
> > >
> > > Signed-off-by: Jason Cooper
> > /me claims prior art:
> >
> >
> > http://mid.
On Wed, Feb 22, 2012 at 08:55:27PM +, Arnd Bergmann wrote:
> On Wednesday 22 February 2012, Jason Cooper wrote:
> > This uart is common to all kirkwood SoC's, so I placed it in the
> > kirkwood.dtsi.
> >
> > Signed-off-by: Jason Cooper
>
> I'm not sure how we are handling this for other plat
This patch series provides initial support for devicetree on kirkwood for the
dreamplug platform. After discussing the approach with Arnd Bergman last week
at ELC, we decided to take an incremental approach to the conversion. First, I
would detect that we were on the dreamplug via the devicetree
This uart is common to all kirkwood SoC's, so I placed it in the
kirkwood.dtsi.
Signed-off-by: Jason Cooper
---
NOTE: first version of this patch, no changelog.
arch/arm/boot/dts/kirkwood.dtsi |8
arch/arm/mach-kirkwood/board-dt.c |2 --
2 files changed, 8 insertions(+), 2 de
Signed-off-by: Jason Cooper
---
NOTE: This is the first version of this patch, so no change history.
arch/arm/boot/.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/.gitignore b/arch/arm/boot/.gitignore
index ce1c5ff..3c79f85 100644
--- a/arch/arm
Initially, copied guruplug-setup.c and did s/guruplug/dreamplug/g.
Then, switched to SPI based NOR flash.
After talking to Arnd Bergman, chose an incremental approach to adding
devicetree support. First, we use the dtb to tell us we are on the
dreamplug, then we gradually port over drivers.
Driv
Thanks Andy and Timur for correcting the statement.
I will make sure of this in future patches.
--Prabhakar
> -Original Message-
> From: Andy Fleming [mailto:aflem...@gmail.com]
> Sent: Saturday, February 18, 2012 4:56 AM
> To: Tabi Timur-B04825
> Cc: Kushwaha Prabhakar-B32579; Goyal Akh
On Fri, Feb 17, 2012 at 10:41:32AM +0100, Nicolas Ferre wrote:
> On 02/13/2012 03:43 PM, Nicolas Ferre :
> > irq_to_gpio() macro will be removed from AT91 GPIO interrupt
> > controller. So we replace it with the use of gpio_to_irq()
> > and a reworked test.
> >
> > Signed-off-by: Nicolas Ferre
>
On Thu, 16 Feb 2012 02:09:01 -0700
Grant Likely wrote:
>
> This series generalizes the "irq_host" infrastructure from powerpc
> so that it can be used by all architectures and renames it to "irq_domain".
drivers/mfd/twl-core.c is fairly horked on i386 allmodconfig:
drivers/mfd/twl-core.c: In f
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -113,5 +113,31 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + mmc1: mmc@1 {
> + compatible = "ti,omap2-hsmmc";
> +
On Thu, Feb 23, 2012 at 9:12 AM, Jason wrote:
> On Thu, Feb 23, 2012 at 07:34:33AM +, Arnd Bergmann wrote:
>> On Thursday 23 February 2012, Rob Herring wrote:
>> > On 02/22/2012 01:18 PM, Jason Cooper wrote:
>>
>> > > diff --git a/arch/arm/mach-kirkwood/Kconfig
>> > > b/arch/arm/mach-kirkwood
* Arnd Bergmann wrote:
> On Thursday 23 February 2012, Thierry Reding wrote:
> > > Is this only used for the device tree functions? If so, I would recommend
> > > making it less generic and always search for a device node.
> >
> > It is currently only used to look up a struct pwm_chip for a given
On 2/23/2012 4:51 PM, Nicolas Ferre wrote:
On 02/23/2012 11:03 AM, Cousson, Benoit :
Salut Nico,
Coucou Benoit ;-)
On 2/22/2012 11:59 AM, Nicolas Ferre wrote:
On 01/27/2012 06:29 PM, Cousson, Benoit :
Add some basic helpers to retrieve a DMA controller device_node
and the DMA request line
On 02/23/2012 11:03 AM, Cousson, Benoit :
> Salut Nico,
Coucou Benoit ;-)
> On 2/22/2012 11:59 AM, Nicolas Ferre wrote:
>> On 01/27/2012 06:29 PM, Cousson, Benoit :
>>> Add some basic helpers to retrieve a DMA controller device_node
>>> and the DMA request line number.
>>>
>>> For legacy reason a
On Thu, Feb 23, 2012 at 05:05:53PM +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)
This doesn't apply to current -next, I expect because of
On Thursday 23 February 2012, Thierry Reding wrote:
> > Is this only used for the device tree functions? If so, I would recommend
> > making it less generic and always search for a device node.
>
> It is currently only used to look up a struct pwm_chip for a given struct
> device_node, yes. But I
On Thursday 23 February 2012, Thierry Reding wrote:
> * Arnd Bergmann wrote:
> > On Wednesday 22 February 2012, Thierry Reding wrote:
> > > This patch adds helpers to support device tree bindings for the generic
> > > PWM API. Device tree binding documentation for PWM controllers is also
> > > prov
Add device tree based discovery support for max8997.
Cc: MyungJoo Ham
Cc: Rajendra Nayak
Cc: Rob Herring
Cc: Grant Likely
Signed-off-by: Thomas Abraham
---
.../devicetree/bindings/regulator/max8997-pmic.txt | 134 +++
drivers/mfd/max8997.c | 72
Add irq domain support for max8997 interrupts. The reverse mapping method
used is linear mapping since the sub-drivers of max8997 such as regulator
and charger drivers can use the max8997 irq_domain to get the linux irq
number for max8997 interrupts. All uses of irq_base in platform data and
max899
Changes since v2:
- Atleast one voltage level has to be specfied for Buck 1/2/5 even if GPIO
DVS option is not used (suggested by MyungJoo Ham).
- Reworked the irq_domain support based the v5 of irq_domain generalization
patches.
MAX8997 is a multi-function device which includes support for re
On Thursday 23 February 2012 05:31 PM, Rajendra Nayak wrote:
This series adds device tree support for OMAP hsmmc
driver. The series is dependent on a couple other series,
to add TWL regulator DT support[1] and another to clean
the pdev->id usage within the hsmmc driver[2]
all patches including t
Add omap mmc related device tree data for OMAP3.
Currenly limited to only omap3-beagle board.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3.dtsi | 26 ++
2 files changed, 32 insertions(+), 0 deletions(-
Add omap mmc related device tree data for OMAP4.
Currenly limited to only omap4-panda and omap4-sdp
boards.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-panda.dts | 10 ++
arch/arm/boot/dts/omap4-sdp.dts | 16
arch/arm/boot/dts/omap4.dtsi | 31 +
This series adds device tree support for OMAP hsmmc
driver. The series is dependent on a couple other series,
to add TWL regulator DT support[1] and another to clean
the pdev->id usage within the hsmmc driver[2]
all patches including the dependent series can be
found here
git://gitorious.org/omap-
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 31 +
drivers/mmc/host/omap_hsmmc.c |
When booting with Device tree, the omap_hsmmc driver does not
program the pbias cell (inside OMAP control module) during
a regulator voltage change.
In case of non-dt boot, this is handled using callbacks
from within platform_data and implemented in machine code.
To be able to do this with device t
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)
Also add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak
---
.../bindings/regulator/twl-reg
Pass all the voltage regulator information for
twl6030/twl4030 PMIC from device tree.
Signed-off-by: Rajendra Nayak
Signed-off-by: Benoit Cousson
---
arch/arm/boot/dts/omap3-beagle.dts |6 +++
arch/arm/boot/dts/twl4030.dtsi | 18 +++
arch/arm/boot/dts/twl6030.dtsi | 60 +
Re-sending as these patches did not make it to the lists due to
issues with my 'git send-email'
v3 has mainly 2 differences from v2
-1- TWL driver now uses just one table for both dt and
non-dt based lookup for driver data.
-2- All common regulator nodes for twl4030 and twl6030 are
now defined in
On Saturday 04 February 2012 06:12 PM, Aneesh V wrote:
This series adds device tree support for TI EMIF SDRAM controller
driver. For this, a binding has been added for representing AC timing
parameters and other details of LPDDR2 memories.
Ping! Any comments on this series?
br,
Aneesh
Salut Nico,
On 2/22/2012 11:59 AM, Nicolas Ferre wrote:
On 01/27/2012 06:29 PM, Cousson, Benoit :
Add some basic helpers to retrieve a DMA controller device_node
and the DMA request line number.
For legacy reason another API will export the DMA request number
into a Linux resource of type IORE
On 23/02/12 19:14, Thierry Reding wrote:
> * Ryan Mallon wrote:
>> On 23/02/12 02:17, Thierry Reding wrote:
>>
>>> This commit adds a generic PWM framework driver for the PWFM controller
>>> found on NVIDIA Tegra SoCs. The driver is based on code from the
>>> Chromium kernel tree and was originall
On Wed, Feb 22, 2012 at 11:26:19PM +0100, Uwe Kleine-K?nig wrote:
> On Wed, Feb 22, 2012 at 07:18:44PM +, Jason Cooper wrote:
> >
> > Signed-off-by: Jason Cooper
> /me claims prior art:
>
>
> http://mid.gmane.org/1323808612-14976-1-git-send-email-u.kleine-koe...@pengutronix.de
Multip
* Ryan Mallon wrote:
> On 23/02/12 02:17, Thierry Reding wrote:
>
> > This commit adds a generic PWM framework driver for the PWFM controller
> > found on NVIDIA Tegra SoCs. The driver is based on code from the
> > Chromium kernel tree and was originally written by Gary King (NVIDIA)
> > and later
* Arnd Bergmann wrote:
> On Wednesday 22 February 2012, Thierry Reding wrote:
>
> > #include
> > +#include
> > #include
>
> You should probably reorder the patches for bisectability, or move the
> of_* related changes out of this patch into patch 3. At the point
> where patch 2 is applied, l
50 matches
Mail list logo
