From: Ludovic Desroches
Still use i2c-gpio on boards which have a SoC with a TWI IP which
doesn't have clock stretching in transmission mode.
Signed-off-by: Ludovic Desroches
Acked-by: Nicolas Ferre
---
arch/arm/boot/dts/at91sam9g25ek.dts| 12
arch/arm/boot/dts/at91sam9m10g45
From: Ludovic Desroches
Add TWI nodes for atmel SoCs but keep i2c-gpio ones in order to let the
choice to the user in dts files.
Signed-off-by: Ludovic Desroches
Acked-by: Nicolas Ferre
---
arch/arm/boot/dts/at91sam9260.dtsi | 10 ++
arch/arm/boot/dts/at91sam9263.dtsi | 10 ++
From: Ludovic Desroches
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/at91sam9260.c | 1 +
arch/arm/mach-at91/at91sam9263.c | 1 +
arch/arm/mach-at91/at91sam9g45.c | 2 ++
arch/arm/mach-at91/at91sam9n12.c | 2 ++
arch/arm/mach-at91/at9
From: Ludovic Desroches
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
Acked-by: Nicolas Ferre
---
.../devicetree/bindings/i2c/atmel-i2c.txt | 30 +
drivers/i2c/busses/i2c-at91.c | 49 ++
2 files changed, 79 insertions(+)
From: Ludovic Desroches
As indicated in the datasheet, TWD and TWCK must not be programmed as
open-drain.
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/at91sam9261_devices.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
From: Ludovic Desroches
Use the id_table to store configuration structures which are depending
on SoC.
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/at91rm9200.c | 2 +-
arch/arm/mach-at91/at91rm9200_devices.c | 11 +
a
From: Ludovic Desroches
Some devices don't have clock streching in transmission mode. It can
lead to premature stop sendings if the latency to write data in the
transmission register is too long. In this case, prefer the i2c-gpio
driver.
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
From: Ludovic Desroches
Use managed resources to ease the cleanup.
Signed-off-by: Ludovic Desroches
Acked-by: Nikolaus Voss
Acked-by: Nicolas Ferre
---
drivers/i2c/busses/i2c-at91.c | 85 +--
1 file changed, 25 insertions(+), 60 deletions(-)
diff --gi
From: Ludovic Desroches
Hi,
This set of patches is based on Nikolaus at91_i2c driver.
Changes:
v3:
- only put multi-drive lines in the if...else statement (suggested
by Warner Losh)
v2:
- change driver name from xxx_i2c to i2c-xxx
- keep i2c-gpio nodes in dtsi files
- don't enable TWI
Hi,
On Tue, Sep 11, 2012 at 02:20:19PM +0200, Nicolas Ferre wrote:
> On 09/11/2012 02:07 PM, Fabio Porcedda :
> > Don't fail the initialization check for the platform_data
> > if there is avaiable an associated device tree node.
> >
> > This patch fix the dt support introduced in 3.4-rc1 by commi
On Wed, Sep 12, 2012 at 12:17 AM, Stephen Warren wrote:
> the drivers in this patch seem to invert the data-structures a
> little - in other words, instead of defining a global list of functions,
> they define a list of groups, and for each group, list the functions
> that can be selected on to i
On 09/10/2012 02:39 AM, Sebastian Hesselbarth wrote:
> From: Thomas Petazzoni
>
> The Armada 370 and XP SoCs have configurable muxing for a certain
> number of their pins, controlled through a pinctrl driver.
Hmmm. I'd be tempted just to put the entire node definition there;
putting in a .dtsi f
On 09/10/2012 02:39 AM, Sebastian Hesselbarth wrote:
> This patch adds a SoC specific pinctrl driver for Marvell Dove SoCs
> plus DT binding documentation. This driver will use the mvebu pinctrl
> driver core.
> diff --git a/drivers/pinctrl/pinctrl-dove.c b/drivers/pinctrl/pinctrl-dove.c
> +stati
On 09/11/2012 08:44 AM, Thomas Petazzoni wrote:
> Hello Sebastian,
>
> Sorry for getting back to you so late about this patch set. I have been
> very busy with other things.
>
> Le Mon, 10 Sep 2012 10:39:38 +0200,
> Sebastian Hesselbarth a écrit :
>
>> v3:
>> - list of functions is now built ou
From: Stephen Warren
Add DT property "maxim,system-power-controller" to indicate whether the
PMIC is in charge of controlling the system power. If this is set, the
driver will provide the pm_power_off() function.
Signed-off-by: Stephen Warren
---
Note: This is based on my patch "mfd: add MAX890
On Tue, Sep 11, 2012 at 10:26:55AM -0600, Stephen Warren wrote:
> On 09/11/2012 10:08 AM, Samuel Ortiz wrote:
> > Hi Stephen,
> >
> > On Tue, Sep 11, 2012 at 09:15:07AM -0600, Stephen Warren wrote:
> >> On 09/11/2012 04:46 AM, Thierry Reding wrote:
> >>> On Tue, Sep 11, 2012 at 06:25:14PM +0800, B
Hi Guennadi,
On 09/11/2012 05:51 PM, Guennadi Liakhovetski wrote:
> This patch adds a document, describing common V4L2 device tree bindings.
>
> Co-authored-by: Sylwester Nawrocki
> Signed-off-by: Guennadi Liakhovetski
> ---
> Documentation/devicetree/bindings/media/v4l2.txt | 143
>
On 09/11/2012 10:08 AM, Samuel Ortiz wrote:
> Hi Stephen,
>
> On Tue, Sep 11, 2012 at 09:15:07AM -0600, Stephen Warren wrote:
>> On 09/11/2012 04:46 AM, Thierry Reding wrote:
>>> On Tue, Sep 11, 2012 at 06:25:14PM +0800, Bill Huang wrote:
Hi all,
Could somebody review this?
>>>
>>>
Hi Stephen,
On Tue, Sep 11, 2012 at 09:15:07AM -0600, Stephen Warren wrote:
> On 09/11/2012 04:46 AM, Thierry Reding wrote:
> > On Tue, Sep 11, 2012 at 06:25:14PM +0800, Bill Huang wrote:
> >> Hi all,
> >>
> >> Could somebody review this?
> >
> > Given that I haven't been able to test yet (due t
Hi Bill,
On Sun, Aug 19, 2012 at 06:07:54PM -0700, Bill Huang wrote:
> This patch series add new property into regulator DT for telling whether or
> not
> to hook pmic's power off routine to system call "pm_power_off".
>
> Patch 1 add power off support for Tegra20 boards using TPS6586x
> Patch 2
Add a minimal dts for original OMAP3430/3530 version of the Beagle board. This
version of the Beagle board has 256MB of DDR and features the same TWL4030
power management IC (PMIC) as the Beagle board XM.
Given that the Beagle and Beagle-XM boards use the same PMIC, move the
definition of the VSIM
This patch adds a document, describing common V4L2 device tree bindings.
Co-authored-by: Sylwester Nawrocki
Signed-off-by: Guennadi Liakhovetski
---
Documentation/devicetree/bindings/media/v4l2.txt | 143 ++
1 files changed, 143 insertions(+), 0 deletions(-)
create mode 10
On 09/11/2012 08:02 AM, Guennadi Liakhovetski wrote:
> Hi Stephen
>
> Thanks for the review.
>
> On Wed, 5 Sep 2012, Stephen Warren wrote:
>
>> On 09/05/2012 04:57 AM, Guennadi Liakhovetski wrote:
>>> Hi all
>>>
>>> Version 5 of this RFC is a result of a discussion of its version 4, which
>>> t
On 09/11/2012 05:59 AM, Prashant Gaikwad wrote:
> On Monday 10 September 2012 10:47 PM, Stephen Warren wrote:
>> On 09/09/2012 07:17 PM, Shawn Guo wrote:
>>> On Fri, Sep 07, 2012 at 10:55:00AM -0600, Stephen Warren wrote:
Yes, that does solve the problem (well, with
s/late_init/late_initc
On 09/11/2012 04:46 AM, Thierry Reding wrote:
> On Tue, Sep 11, 2012 at 06:25:14PM +0800, Bill Huang wrote:
>> Hi all,
>>
>> Could somebody review this?
>
> Given that I haven't been able to test yet (due to time
> constraints) with PM_SLEEP_SMP enabled, I don't want to give you a
> Tested-by, bu
Hi Stephen
Thanks for the review.
On Wed, 5 Sep 2012, Stephen Warren wrote:
> On 09/05/2012 04:57 AM, Guennadi Liakhovetski wrote:
> > Hi all
> >
> > Version 5 of this RFC is a result of a discussion of its version 4, which
> > took place during the recent Linux Plumbers conference in San Dieg
On Tue, Sep 11, 2012 at 01:42:01PM +0300, Alexander Shishkin wrote:
> What about the other two patches? I guess they can go through arm tree
> so we don't have to send it through Greg, right?
>
Right, those two will go via arm-soc tree once the first one gets
applied on usb tree.
--
Regards,
Sha
On 09/11/2012 02:07 PM, Fabio Porcedda :
> Don't fail the initialization check for the platform_data
> if there is avaiable an associated device tree node.
>
> This patch fix the dt support introduced in 3.4-rc1 by commit
> ("d1494a3 USB: at91: Device udc add dt support").
>
> Tested on a at91sam
Don't fail the initialization check for the platform_data
if there is avaiable an associated device tree node.
This patch fix the dt support introduced in 3.4-rc1 by commit
("d1494a3 USB: at91: Device udc add dt support").
Tested on a at91sam9260 based board (PRO3-EVK).
Signed-off-by: Fabio Porc
On Monday 10 September 2012 10:47 PM, Stephen Warren wrote:
On 09/09/2012 07:17 PM, Shawn Guo wrote:
On Fri, Sep 07, 2012 at 10:55:00AM -0600, Stephen Warren wrote:
Yes, that does solve the problem (well, with s/late_init/late_initcall/).
As you imply, that change wouldn't help if cpu-tegra.c
On 09/11/2012 01:29 PM, Benoit Cousson wrote:
> Hi Jon,
>
> On 09/11/2012 12:57 AM, Jon Hunter wrote:
>> Add a minimal dts for original OMAP3430/3530 version of the Beagle board.
>> This
>> version of the Beagle board has 256MB of DDR and features the same TWL4030
>> power management IC (PMIC) as
+ Andrew,
On Thu, Sep 06, 2012 at 20:12:07, Cousson, Benoit wrote:
>
> On 09/05/2012 04:41 PM, Hiremath, Vaibhav wrote:
> ...
> > There are other patches which are pending,
> >
> > arm/dts: AM33XX: Convert all hex numbers to lower-case
> > https://patchwork.kernel.org/patch/1377351/
> > arm/dts:
On Tue, Sep 11, 2012 at 10:45:44AM +, B, Ravi wrote:
> >
> > Hi,
> >
> > On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
> > > This series of patches adds,
> > > a) Multi instances support in musb driver
> > > b) DT support for musb_dsps glue layer
> > > c) DT support for NOP trans
On Tue, Sep 11, 2012 at 16:54:37, ABRAHAM, KISHON VIJAY wrote:
> Hi,
>
> On Tue, Sep 11, 2012 at 3:23 PM, Vaibhav Hiremath wrote:
> >
> >
> > On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
> >> Added device tree support for omap musb driver and updated the
> >> Documentation with device tree
On Tue, Sep 11, 2012 at 16:59:05, Porter, Matt wrote:
> On Tue, Sep 11, 2012 at 04:57:08AM +, Hiremath, Vaibhav wrote:
> > On Mon, Sep 10, 2012 at 21:50:20, Porter, Matt wrote:
> > > On AM33xx, the datasheet and TRM refer to four GPIO instances that
> > > are 0-based, GPIO0-3.
> > >
> >
> > T
Hi Jon,
On 09/11/2012 12:57 AM, Jon Hunter wrote:
> Add a minimal dts for original OMAP3430/3530 version of the Beagle board. This
> version of the Beagle board has 256MB of DDR and features the same TWL4030
> power management IC (PMIC) as the Beagle board XM.
Thanks for the patch.
> Given that
On Tue, Sep 11, 2012 at 04:57:08AM +, Hiremath, Vaibhav wrote:
> On Mon, Sep 10, 2012 at 21:50:20, Porter, Matt wrote:
> > On AM33xx, the datasheet and TRM refer to four GPIO instances that
> > are 0-based, GPIO0-3.
> >
>
> Thanks Matt,
> I think Anil labeled it as gpio1-4 due to hwmod naming
Hi,
On Tue, Sep 11, 2012 at 3:23 PM, Vaibhav Hiremath wrote:
>
>
> On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
>> Added device tree support for omap musb driver and updated the
>> Documentation with device tree binding information.
>>
>> Signed-off-by: Kishon Vijay Abraham I
>> ---
>> D
On Tue, Sep 11, 2012 at 06:25:14PM +0800, Bill Huang wrote:
> Hi all,
>
> Could somebody review this?
Given that I haven't been able to test yet (due to time constraints)
with PM_SLEEP_SMP enabled, I don't want to give you a Tested-by, but the
code looks okay to me, so for both patches:
Reviewe
Hi all,
Could somebody review this?
Thanks,
Bill
>
> This patch series add new property into regulator DT for telling whether or
> not to hook pmic's power off routine to system call
> "pm_power_off".
>
> Patch 1 add power off support for Tegra20 boards using TPS6586x Patch 2 add
> power of
On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
> Added device tree support for omap musb driver and updated the
> Documentation with device tree binding information.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> Documentation/devicetree/bindings/usb/omap-usb.txt | 33
>
Hi,
On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
> This series of patches adds,
> a) Multi instances support in musb driver
> b) DT support for musb_dsps glue layer
> c) DT support for NOP transceiver
>
> AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
>
On 09/11/2012 11:09 AM, Kishon Vijay Abraham I wrote:
> The mailbox register for usb otg in omap is present in control module.
> On detection of any events VBUS or ID, this register should be written
> to send the notification to musb core.
>
> Till we have a separate control module driver to writ
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 33
drivers/usb/musb/omap2430.c| 54 +
The glue layer should directly write to mailbox register (present in
control module) instead of calling phy layer to write to mailbox
register. Writing to mailbox register notifies the core of events like
device connect/disconnect.
Currently writing to control module register is taken care in this
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes to
This patch series adds device tree support for MUSB.
The glue layer is now made to write to mailbox register (present in
control module) instead of calling phy layer to write to mailbox
register. Writing to mailbox register notifies the core of events like
device connect/disconnect.
Changes from
Hi,
On Mon, Sep 10, 2012 at 10:13 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Sep 10, 2012 at 06:17:03PM +0200, Benoit Cousson wrote:
>> > On 9/6/2012 8:25 PM, Kishon Vijay Abraham I wrote:
>> >> The mailbox register for usb otg in omap is present in control module.
>> >> On detection o
Hi,
On Tue, Sep 11, 2012 at 1:53 PM, Benoit Cousson wrote:
> Hi Kishon,
>
> On 09/11/2012 08:12 AM, Kishon Vijay Abraham I wrote:
>> Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
>> connected to ocp2scp, omap-usb2 dt data is added as a child node
>> of ocp2scp.
>
> Could y
Hi Praveen,
Praveen Paneri wrote:
> Changes from v3:
> Replaced susbsys_initcall()/module_exit() by module_platform_driver().
> Accordingly in the hsotg driver returned -EPROBE_DEFER until phy driver
> is registered
> Removed unnecessary devm_usb_put_phy() call from the hsotg driver remove.
>
> C
Hi Kishon,
On 09/11/2012 08:12 AM, Kishon Vijay Abraham I wrote:
> Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
> connected to ocp2scp, omap-usb2 dt data is added as a child node
> of ocp2scp.
Could you add more details about the omap-usb2?
You must update the Documentat
51 matches
Mail list logo
