ret should be signed here for the error handling to work.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/usb/phy/omap-usb2.c b/drivers/usb/phy/omap-usb2.c
index 15ab3d6..d36c282 100644
--- a/drivers/usb/phy/omap-usb2.c
+++ b/drivers/usb/phy/omap-usb2.c
@@ -120,7
On 13/09/12 21:32, Rob Herring wrote:
On 09/13/2012 06:10 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch introduces of_get_child function to get a child node by its
name in a given parent node.
Without this patch each driver code has to
Add lis3lv02d device tree initialization code/API to take pdata
from device node. Also remove CONFIG_OF ifdef from the driver,
if CONFIG_OF is not defined then OF APIs returns 0.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
drivers/misc/lis3lv02d/lis3lv02d_spi.c |8 +---
1 file
Remove lis3lv02d driver device tree initialization from core driver
and move it to individual drivers. With the current implementation
some pdata parameters are missing if we use lis3lv02d_init_device()
in lis3lv02d_i2c driver.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status of I2C2 node to okay to use I2C2 bus. Also
added all the required platform data to am335x-evm.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
Add lis3lv02d device tree initialization code/API to take pdata
from device node. Also adds device tree init matching table
support to lis3lv02d_i2c driver. If the driver data is passed
from device tree, then this driver picks up platform data
from device node through common/generic lis3lv02d.c
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for lis331dlh driver to am335x-EVM. These
patches were tested on
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch series introduces of_get_child_by_name function to get a
child node by its name in a given parent node and also removes code
duplication in some of the existing driver code by using of_get_child_by_name.
Normally if a driver want
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch introduces of_get_child_by_name function to get a child node
by its name in a given parent node.
Without this patch each driver code has to iterate the parent and do
a string compare, However having of_get_child_by_name libary
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name instead.
Signed-off-by: Srinivas Kandagatla
On Thursday 13 September 2012, AnilKumar Ch wrote:
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status to okay to use I2C2 bus. Also added all the
required platform data to am335x-evm.
Hi Arnd,
Thanks for the review,
On Fri, Sep 14, 2012 at 13:56:06, Arnd Bergmann wrote:
On Thursday 13 September 2012, AnilKumar Ch wrote:
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status to
On Friday 14 September 2012, AnilKumar, Chimata wrote:
On Fri, Sep 14, 2012 at 13:56:06, Arnd Bergmann wrote:
On Thursday 13 September 2012, AnilKumar Ch wrote:
Why do you put the reg property here
Here I specified reg property because lis331dlh I2C slave address is 0x18.
Add a doc to describe the Xen ARM device tree bindings
Changes in v4:
- xen,xen should be last as it is less specific;
- update reg property using 2 address-cells and 2 size-cells.
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
CC: devicetree-discuss@lists.ozlabs.org
CC:
This patch adds device tree support for s3c-hsotg driver
used for Samsung platforms.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
.../devicetree/bindings/usb/s3c-hsotg.txt | 16
drivers/usb/gadget/s3c-hsotg.c
On 09/14/2012 03:19 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name
On 09/14/2012 03:18 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the code duplication in the
driver by replacing it with of_get_child_by_name
On Thu, Sep 13, 2012 at 10:34 PM, Rob Herring robherri...@gmail.com wrote:
On 09/13/2012 03:30 PM, Thomas Petazzoni wrote:
Dear Rob Herring,
On Thu, 13 Sep 2012 15:20:54 -0500, Rob Herring wrote:
On 09/13/2012 10:54 AM, Thomas Petazzoni wrote:
Signed-off-by: Thomas Petazzoni
Thanks for pointing the typo..
On 14/09/12 14:05, Rob Herring wrote:
On 09/14/2012 03:19 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch removes some of the
My bad...
Will skip this patch in next patch-set...
On 14/09/12 14:06, Rob Herring wrote:
On 09/14/2012 03:18 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
As follow-up to dt: introduce of_get_child_by_name to get child node by
name. patch, This patch
Hi Arnd,
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
On Thursday 13 September 2012, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
I think
On Friday 14 September 2012, Jon Hunter wrote:
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
+
+Client drivers should specify the DMA property using a phandle to the
controller
+followed by DMA controller specific data.
+
+Required property:
+- dmas: List of one or
On 09/14/2012 08:32 AM, Arnd Bergmann wrote:
On Friday 14 September 2012, Jon Hunter wrote:
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
+
+Client drivers should specify the DMA property using a phandle to the
controller
+followed by DMA controller specific data.
+
+Required property:
On Fri, 14 Sep 2012, Konrad Rzeszutek Wilk wrote:
On Fri, Sep 14, 2012 at 12:13:08PM +0100, Stefano Stabellini wrote:
Add a doc to describe the Xen ARM device tree bindings
Changes in v4:
- xen,xen should be last as it is less specific;
- update reg property using 2 address-cells
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2] to add
some basic device-tree helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
v5: - minor update to binding documentation
- added loop to exhaustively search for a slave channel
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition of
device-tree helper functions to extract the
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the capabilites of the hardware.
Thinking about DMA
On Friday 14 September 2012, Jon Hunter wrote:
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Stephen Warren swar...@nvidia.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Russell King li...@arm.linux.org.uk
Cc: Rob Herring rob.herr...@calxeda.com
Cc:
On Friday 14 September 2012, Jon Hunter wrote:
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition
On Friday 14 September 2012, AnilKumar, Chimata wrote:
Small question here, in my v2 version I have specified both
the compatible names lis3lv02d and lis331dlh is it fine or
only one is sufficient?
+static struct of_device_id lis3lv02d_i2c_dt_ids[] = {
+ { .compatible = st,lis3lv02d
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for lis331dlh
On 09/14/2012 05:18 PM, Jon Hunter :
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the
Allow a gpio-fan to be defined in devicetree, see binding documentation
for details.
Signed-off-by: Jamie Lentin j...@lentin.co.uk
Acked-by: Andrew Lunn and...@lunn.ch
---
Changes since V2:-
* Correct error message terminology
* Check of_gpio_count returns some GPIOs [Guenter Roeck]
* Whitespace
This patch adds a helper function for parsing videomodes from the devicetree.
The videomode can be either converted to a struct drm_display_mode or a
struct fb_videomode.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
Signed-off-by: Steffen Trumtrar s.trumt...@pengutronix.de
---
Hi!
The
On 09/13/2012 04:00 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
diff --git a/Documentation/devicetree/bindings/dma/dma.txt
On 09/13/2012 09:41 AM, Sebastian Hesselbarth wrote:
This patch set adds a core pinctrl driver for Marvell MVEBU SoCs and
SoC specific stubs for Armada 370, Armada XP, Dove, and Kirkwood.
The SoC specific stubs use the pinctrl-mvebu core driver that handles
pinctrl API and register accesses
On 09/14/2012 11:28 AM, Stephen Warren wrote:
On 09/13/2012 04:00 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
diff --git
On 09/14/2012 10:26 AM, Arnd Bergmann wrote:
On Friday 14 September 2012, Jon Hunter wrote:
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Stephen Warren swar...@nvidia.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Russell King li...@arm.linux.org.uk
On Fri, Sep 07, 2012 at 10:22:28AM -0700, Bjorn Helgaas wrote:
On Fri, Sep 7, 2012 at 10:00 AM, Thierry Reding
thierry.red...@avionic-design.de wrote:
On Fri, Sep 07, 2012 at 10:19:46AM -0600, Stephen Warren wrote:
On 08/15/2012 01:42 PM, Bjorn Helgaas wrote:
On Wed, Aug 15, 2012 at 1:28
On Fri, Sep 14, 2012 at 12:55 PM, Thierry Reding
thierry.red...@avionic-design.de wrote:
On Fri, Sep 07, 2012 at 10:22:28AM -0700, Bjorn Helgaas wrote:
On Fri, Sep 7, 2012 at 10:00 AM, Thierry Reding
thierry.red...@avionic-design.de wrote:
On Fri, Sep 07, 2012 at 10:19:46AM -0600, Stephen
On Fri, 14 Sep 2012 15:31:36 +
Arnd Bergmann a...@arndb.de wrote:
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is
On Friday 14 September 2012, Andrew Morton wrote:
On Fri, 14 Sep 2012 15:31:36 +
Arnd Bergmann a...@arndb.de wrote:
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual
On 09/13/2012 09:54 AM, Thomas Petazzoni wrote:
diff --git a/Documentation/devicetree/bindings/gpio/gpio-mvebu.txt
b/Documentation/devicetree/bindings/gpio/gpio-mvebu.txt
+- #interrupt-cells: specifies the number of celles needed to encode an
+ interrupt source
s/celles/cells/
What
On 09/13/2012 09:54 AM, Thomas Petazzoni wrote:
The gpioX aliases are needed so that the driver can use
of_alias_get_id() to get a 0-based number of the GPIO bank, which we
then use to compute the base GPIO of the bank being probed. This is
similar to what gpio-mxs.c is doing.
Hi all,
I apologise for sending out so many updates in quick succession before everyone
has had chance to review, however, I will be out of office next week and I know
that several people have been waiting for this. Normally, I would not send out
a series and disappear for a week, but Arnd agreed
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition of
device-tree helper functions to extract the
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the capabilites of the hardware.
Thinking about DMA
On 09/14/2012 04:41 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
The binding looks good to me now, so,
Reviewed-by: Stephen Warren
On Fri, Sep 14, 2012 at 04:54:08PM +0200, Thomas Petazzoni wrote:
Dear Linus Walleij,
On Fri, 14 Sep 2012 15:17:09 +0200, Linus Walleij wrote:
Yes, I know, but MAINTAINERS does not mention an alternate maintainer
for the GPIO subsystem. Who is the interim maintainer that will
On Fri, Sep 14, 2012 at 05:41:56PM -0500, Jon Hunter wrote:
3. Supporting legacy devices not using DMA Engine
These devices present a problem, as there may not be a uniform way to
easily
support them with regard to device tree. Ideally, these should be migrated
to DMA engine.
On Fri, Sep 14, 2012 at 07:28:33PM -0700, Guenter Roeck wrote:
On Fri, Sep 14, 2012 at 05:07:06PM +0100, Jamie Lentin wrote:
Allow a gpio-fan to be defined in devicetree, see binding documentation
for details.
Signed-off-by: Jamie Lentin j...@lentin.co.uk
Acked-by: Andrew Lunn
56 matches
Mail list logo
