On Thu, Dec 27, 2012 at 4:28 AM, Sylwester Nawrocki
sylvester.nawro...@gmail.com wrote:
On 12/24/2012 09:13 AM, Vivek Gautam wrote:
These two changes look good to me. For both of them:
Reviewed-by: Doug Andersondiand...@chromium.org
Well, I have another idea. Yes, I know, specific chip
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.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |4
1 file changed,
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |3 +++
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On Thu, 2012-12-13 at 09:29 +0100, Stefan Roese wrote:
Currently cfi_cmdset_0002.c does not support PPB locking of sectors. This
patch adds support for this locking/unlocking mechanism. It is needed on
some platforms, since newer U-Boot versions do support this PPB locking
and protect for
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/configs/mvebu_defconfig |5 -
1 files changed, 4 insertions(+),
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-db.dts |8
1 files changed, 8
The Armada 370 and Armada XP SoC has an Orion EHCI USB controller.
This patch adds support for this controller in Armada 370
and Armada XP SoC common device tree files.
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Signed-off-by: Gregory CLEMENT
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-mirabox.dts |8
1 files changed, 8
Hi,
This small patch set enables USB support on Armada 370 and Armada XP platforms.
It's based on Jason Cooper's mvebu/dt branch.
Any comments or feedback are welcome.
Ezequiel Garcia (6):
arm: mvebu: Add support for USB host controllers in Armada 370/XP
arm: mvebu: Enable USB controllers on
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts |9 +
1 files
Hello Ezequiel,
Le 01/15/13 10:54, Ezequiel Garcia a écrit :
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 440b13e..5e4fcde 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -24,6 +24,7 @@ config MACH_ARMADA_370_XP
select
Hi Linus W,
On Tuesday 08 January 2013 01:02 PM, Laxman Dewangan wrote:
From: Pritesh Raithatha praitha...@nvidia.com
NVIDIA's Tegra114 added two more configuration parameter in pinmux i.e.
rcv-sel and drive type.
rcv-sel: Select between High and Normal VIL/VIH receivers.
RCVR_SEL=1:
Hi Florian,
On 01/15/2013 07:23 AM, Florian Fainelli wrote:
Le 01/15/13 10:54, Ezequiel Garcia a écrit :
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 440b13e..5e4fcde 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -24,6 +24,7 @@
On Mon, Jan 14, 2013 at 05:13:09PM -0500, Nicolas Pitre wrote:
On Fri, 11 Jan 2013, Sascha Hauer wrote:
On Thu, Jan 03, 2013 at 04:55:00PM +0100, Tomasz Figa wrote:
Hi,
I'm observing strange behavior when booting 3.8-rc1 and -rc2 with
appended
DTB. The kernel hangs very
On Tue, Jan 15, 2013 at 09:53:08AM +0300, Dan Carpenter wrote:
sizeof(p) was intended instead of sizeof(data). data is a pointer and
p is a 7 character struct. It probably doesn't make a difference most
of the time, but it could result in using uninitialized data.
Signed-off-by: Dan
Hi Nicolas,
On Monday 14 of January 2013 17:13:09 Nicolas Pitre wrote:
On Fri, 11 Jan 2013, Sascha Hauer wrote:
On Thu, Jan 03, 2013 at 04:55:00PM +0100, Tomasz Figa wrote:
Hi,
I'm observing strange behavior when booting 3.8-rc1 and -rc2 with
appended DTB. The kernel hangs very
On Tue, Jan 15, 2013 at 02:08:34PM +0800, Peter Chen wrote:
For mxs-phy user i.mx6q, the PHY's clock is controlled by
hardware automatically, the software only needs to enable it
at probe, disable it at remove. During the runtime,
we don't need to control it. So for the usbphy clk policy:
-
On Mon, Jan 14, 2013 at 09:57:07AM +, Andrew Murray wrote:
On Sun, Jan 13, 2013 at 09:58:06AM +, Thierry Reding wrote:
On Sat, Jan 12, 2013 at 09:12:25PM +, Arnd Bergmann wrote:
On Saturday 12 January 2013, Thierry Reding wrote:
I already hinted at that in one of the other
On Mon, Jan 14, 2013 at 10:24:11PM +, Arnd Bergmann wrote:
On Monday 14 January 2013, Thierry Reding wrote:
It certainly sounds like a less complicated way to do it. But it also
involves adding a function with a made up name and drop a function with
a perfectly good name instead. I
Stefan,
This is a good-looking patch series, nice and small! A few comments:
On Tue, Jan 15, 2013 at 01:13:12PM +0100, Stefan Peter wrote:
In order to be able to use the ecc-mode, add the bch module to the default
settings for the kirwood boards and enable the activation in orin-nand.c
On Tuesday 15 January 2013, Thierry Reding wrote:
I'm not sure I follow you're reasoning here. Is it possible to use MSIs
without PCI? If not then I think there's little sense in keeping the
implementations separate.
Conceptually, you can use MSI for any device, but the Linux interfaces
for
On Tue, Jan 15, 2013 at 01:13:12PM +0100, Stefan Peter wrote:
In order to be able to use the ecc-mode, add the bch module to the default
settings for the kirwood boards and enable the activation in orin-nand.c
Signed-off-by: Stefan Peter s.pe...@mpl.ch
---
diff --git
Hi,
I am sorry, but I do not consider a function that was added a little
over a year ago as a canon. If you look at the uses of EADDRNOTAVAIL
it
is used predominantly in networking code to indicate that attempted
_network_ address is not available.
EBUSY might
On Tuesday 15 January 2013, Ezequiel Garcia wrote:
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
The patches look good, but
Changes from v3:
- Clubbed together arch enable patches for ehci/ohci and dwc3:
[PATCH v3 0/2] Enable ehci and ohci devices for exynos5250, and
[PATCH v3] ARM: Exynos5250: Enabling dwc3-exynos driver
- Dropped OF_DEV_AUXDATA entry in mach-exysno5-dt since we don't
need it.
- Splitted
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
---
.../devicetree/bindings/usb/exynos-usb.txt
Adding OHCI device tree node for Exynos5250 along with
the device base address.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
---
.../devicetree/bindings/usb/exynos-usb.txt | 15
Adding necessary device clock to exynos5 needed for
the DWC3 controller.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/mach-exynos/clock-exynos5.c | 24
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git
Adding DWC3 device tree node for Exynos5250 needed to
parse device tree data.
Also enabling XHCI support on exynos5250.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 14 ++
arch/arm/boot/dts/exynos5250.dtsi
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
+OMAP CONTROL USB
+
+Required properties:
+ - compatible: Should be ti,omap-control-usb
+ - reg : Address and length of the register set for the device. It contains
+ the address of control_dev_conf and otghs_control.
+ -
Hi,
This series adds DT support to da8xx-fb driver (device found on
DaVinci and AM335x SoC's). It does certain cleanup's in the process.
This series as compared to previous version handles configuration of
the LCDC input clock to required value if clock divider in IP cannot
take care of required
Replace __raw_readl/__raw_writel with readl/writel; this driver is
reused on ARMv7 (AM335x SoC).
Signed-off-by: Afzal Mohammed af...@ti.com
---
v2: new patch
drivers/video/da8xx-fb.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/da8xx-fb.c
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module
Replace existing resource handling in the driver with managed device
resource.
Signed-off-by: Afzal Mohammed af...@ti.com
---
drivers/video/da8xx-fb.c | 35 ++-
1 file changed, 6 insertions(+), 29 deletions(-)
diff --git a/drivers/video/da8xx-fb.c
Driver is provided a means to have the probe triggered by DT.
Signed-off-by: Afzal Mohammed af...@ti.com
---
.../devicetree/bindings/video/fb-da8xx.txt | 16
drivers/video/da8xx-fb.c |7 +++
2 files changed, 23 insertions(+)
create
Ensure that platform data is present before checking whether platform
callback is present (the one used to control backlight). So far this
was not an issue as driver was purely non-DT triggered, but now DT
support has been added.
Signed-off-by: Afzal Mohammed af...@ti.com
---
Move panel detection to a separate function, this helps in readability
as well as makes DT support cleaner.
Signed-off-by: Afzal Mohammed af...@ti.com
---
drivers/video/da8xx-fb.c | 42 ++
1 file changed, 26 insertions(+), 16 deletions(-)
diff --git
Obtain fb_videomode details for the connected lcd panel using the
display timing details present in DT.
Signed-off-by: Afzal Mohammed af...@ti.com
---
.../devicetree/bindings/video/fb-da8xx.txt | 21
drivers/video/da8xx-fb.c | 17
This driver is DT probe-able, hence ensure presence of platform data
only for non-DT boot.
Signed-off-by: Afzal Mohammed af...@ti.com
---
drivers/video/da8xx-fb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/da8xx-fb.c b/drivers/video/da8xx-fb.c
index
strcut lcd_ctrl_config information required for driver is currently
obtained via platform data. To handle DT probing, create
lcd_ctrl_config and populate it with default values, these values are
sufficient for the panels so far used with this controller to work.
Signed-off-by: Afzal Mohammed
LCDC IP has a clock divider to adjust pixel clock, this limits pixel
clock range to fck/255 - fck/2(fck - rate of input clock to LCDC IP).
In the case of AM335x, where this IP is present, default fck is not
sufficient to provide normal pixel clock rates, hence rendering this
driver unusable on
Add lcdc node.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index c2f14e8..432d4bb8 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++
Hi,
This series add DT sources for AM335x SoC as well as AM335x based
boards.
As compared to previous version, in this version, comment has been
added in dt source file about pinmux details so that user can easily
correlate to that mentioned in TRM. Also author of one of the patch
was actually
Update lcdc node with panel timings (typical) for AM335X-EVM.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index
From: Manjunathappa, Prakash prakash...@ti.com
Update pin mux information for lcd panel on AM335X-EVM
[af...@ti.com: comment specifying user understandable pinmux details]
Signed-off-by: Manjunathappa, Prakash prakash...@ti.com
Signed-off-by: Afzal Mohammed af...@ti.com
---
v2: correct
Update lcdc node with panel timings (typical) for AM335X-EVMSK.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/boot/dts/am335x-evmsk.dts | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm/boot/dts/am335x-evmsk.dts
Update pin mux information for lcd panel on AM335X-EVMSK.
Signed-off-by: Afzal Mohammed af...@ti.com
---
v2: add comment on pinmux entries
arch/arm/boot/dts/am335x-evmsk.dts | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git
Hi Arnd,
On 01/15/2013 10:07 AM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Ezequiel Garcia wrote:
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia
Hi Steffen,
On Mon, Jan 07, 2013 at 14:51:15, Mohammed, Afzal wrote:
On Mon, Jan 07, 2013 at 14:41:31, Steffen Trumtrar wrote:
On Mon, Jan 07, 2013 at 10:41:30AM +0530, Afzal Mohammed wrote:
+- display-timings: list of different videomodes supported by the lcd
+ panel, represented as
Hi Arnd,
On Tuesday 15 January 2013 07:06 PM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
+OMAP CONTROL USB
+
+Required properties:
+ - compatible: Should be ti,omap-control-usb
+ - reg : Address and length of the register set for the device. It contains
+
On Tuesday 15 January 2013 06:23 PM, Sergei Shtylyov wrote:
Hello.
On 15-01-2013 12:42, Kishon Vijay Abraham I wrote:
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by
Hi Arnd,
On Tuesday 15 January 2013 07:11 PM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act
On Tuesday 15 January 2013, kishon wrote:
Good point :-). Currently, none of the OMAP platforms have multiple
control modules and it doesn't seem to be in the future (AFAIK). While
it might be simpler to support multiple control devices with phandle, it
might face the same complications as
Quoting Afzal Mohammed (2013-01-15 05:44:36)
LCDC IP has a clock divider to adjust pixel clock, this limits pixel
clock range to fck/255 - fck/2(fck - rate of input clock to LCDC IP).
In the case of AM335x, where this IP is present, default fck is not
sufficient to provide normal pixel clock
On Tue, Jan 15, 2013 at 12:44:12PM +, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Thierry Reding wrote:
I'm not sure I follow you're reasoning here. Is it possible to use MSIs
without PCI? If not then I think there's little sense in keeping the
implementations separate.
On Tue, Jan 15, 2013 at 02:06:23PM +0100, Wolfram Sang wrote:
Hi,
I am sorry, but I do not consider a function that was added a little
over a year ago as a canon. If you look at the uses of
EADDRNOTAVAIL it
is used predominantly in networking code to indicate that
Hi,
On Tue, Jan 15, 2013 at 08:09:22PM +0530, kishon wrote:
Hi Arnd,
On Tuesday 15 January 2013 07:11 PM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module.
This has an
API to power on the USB2
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [121223 13:49]:
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack zon...@gmail.com wrote:
+
+Example for an AM33xx board:
+
+
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [121223 13:49]:
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack
On Tue, 15 Jan 2013, Tomasz Figa wrote:
Hi Nicolas,
On Monday 14 of January 2013 17:13:09 Nicolas Pitre wrote:
On Fri, 11 Jan 2013, Sascha Hauer wrote:
On Thu, Jan 03, 2013 at 04:55:00PM +0100, Tomasz Figa wrote:
Hi,
I'm observing strange behavior when booting 3.8-rc1 and
Artem,
Looks like this patch related to making GPMC work with DT was
never sent to linux-mtd or to you so adding to cc.
Is this OK to apply along with the GPMC patches, or do you want to
take this separately with the MTD patches?
Regards,
Tony
* Daniel Mack zon...@gmail.com [121214 02:39]:
* Ezequiel Garcia elezegar...@gmail.com [130115 10:13]:
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
OK thanks. Applying this set into omap-for-v3.9/gpmc.
Looks like we need ack from for one of the patches Artem
On Tue, 2013-01-15 at 10:52 -0800, Tony Lindgren wrote:
Artem,
Looks like this patch related to making GPMC work with DT was
never sent to linux-mtd or to you so adding to cc.
Is this OK to apply along with the GPMC patches, or do you want to
take this separately with the MTD patches?
Add support for MAX6581, MAX6602, MAX6622, MAX6636, MAX6689, MAX6693,
MAX6694, MAX6697, MAX6698, and MAX6699 temperature sensors
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Add suppport for platform data and devicetree based chip initialization
- Drop S_IRUGOWU macro:
* Artem Bityutskiy dedeki...@gmail.com [130115 11:12]:
On Tue, 2013-01-15 at 10:52 -0800, Tony Lindgren wrote:
Artem,
Looks like this patch related to making GPMC work with DT was
never sent to linux-mtd or to you so adding to cc.
Is this OK to apply along with the GPMC patches, or
On Tue, 2013-01-15 at 11:26 -0800, Tony Lindgren wrote:
* Artem Bityutskiy dedeki...@gmail.com [130115 11:12]:
On Tue, 2013-01-15 at 10:52 -0800, Tony Lindgren wrote:
Artem,
Looks like this patch related to making GPMC work with DT was
never sent to linux-mtd or to you so adding to
Hello Ezequiel,
On Tuesday 15 January 2013 06:59:57 Ezequiel Garcia wrote:
Hi,
This small patch set enables USB support on Armada 370 and Armada XP
platforms.
It's based on Jason Cooper's mvebu/dt branch.
Any comments or feedback are welcome.
I successfully tested this serie on a
Changes since v4:
- Fixed debug section mismatch in private edma api [01/14]
- Respun format-patch to catch the platform_data/edma.h rename [01/14]
- Removed address/size-cells from the EDMA binding [05/14]
Changes since v3:
- Rebased on 3.8-rc3
- No longer
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well. This just moves the
private EDMA API and enables it to build on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/Kconfig |1 +
Fix build on OMAP, the irqs are undefined on AM33xx.
These error interrupt handlers were hardcoded as disabled
so since they are unused code, simply remove them.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/common/edma.c | 37 -
1 file changed, 37
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data. Enables runtime PM support to
initialize the EDMA hwmod. Adds AM33XX EMDA crossbar event mux
support.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/common/edma.c | 314
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
---
drivers/dma/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index d4c1218..20ef955 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +
1 file changed, 49 insertions(+)
create mode 100644
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
instantiated via DT, the appropriate channel request call will be
made.
This allows for a much cleaner migration of drivers
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the
The EDMA DMAC has a hardware limitation that prevents supporting
scatter gather lists with any number of segments. The DMA Engine
API reports the maximum number of segments a channel can support
via the optional dma_get_channel_caps() API. If the nr_segs
capability is present, the value is used to
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 25 +++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git
Adds AM33XX MMC support for am335x-bone, am335x-evm, and
am335x-evmsk.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
arch/arm/boot/dts/am335x-evmsk.dts |
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git
Adds DMA resources to the AM33XX SPI nodes.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 278b75d..8fd3648 100644
---
On Tue, Jan 15, 2013 at 03:40:38PM +, Andrew Murray wrote:
On Tue, Jan 15, 2013 at 12:44:12PM +, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Thierry Reding wrote:
I'm not sure I follow you're reasoning here. Is it possible to use MSIs
without PCI? If not then I think there's
Hi Guenter,
On Tue, 15 Jan 2013 11:25:04 -0800, Guenter Roeck wrote:
Add support for MAX6581, MAX6602, MAX6622, MAX6636, MAX6689, MAX6693,
MAX6694, MAX6697, MAX6698, and MAX6699 temperature sensors
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Add suppport for platform data
On Tue, Jan 15, 2013 at 10:50:34PM +0100, Jean Delvare wrote:
Hi Guenter,
On Tue, 15 Jan 2013 11:25:04 -0800, Guenter Roeck wrote:
Add support for MAX6581, MAX6602, MAX6622, MAX6636, MAX6689, MAX6693,
MAX6694, MAX6697, MAX6698, and MAX6699 temperature sensors
Signed-off-by: Guenter
Add support for MAX6581, MAX6602, MAX6622, MAX6636, MAX6689, MAX6693,
MAX6694, MAX6697, MAX6698, and MAX6699 temperature sensors
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Add suppport for platform data and devicetree based chip initialization
- Drop S_IRUGOWU macro:
Florian,
On 01/15/2013 04:54 PM, Florian Fainelli wrote:
On Tuesday 15 January 2013 06:59:57 Ezequiel Garcia wrote:
Hi,
This small patch set enables USB support on Armada 370 and Armada XP
platforms.
It's based on Jason Cooper's mvebu/dt branch.
Any comments or feedback are welcome.
I
On Mon, Jan 07, 2013 at 11:58:36AM +, Will Deacon wrote:
On Thu, Jan 03, 2013 at 06:06:43PM +, Pratik Patel wrote:
On Sun, Dec 23, 2012 at 11:32:39AM +, Will Deacon wrote:
On Fri, Dec 21, 2012 at 10:18:28PM +, Pratik Patel wrote:
What user interface do you plan to provide
On Wed, Jan 16, 2013 at 09:48:57AM +0800, Shawn Guo wrote:
On Wed, Jan 16, 2013 at 09:18:46AM +0800, Peter Chen wrote:
On Tue, Jan 15, 2013 at 07:33:16PM +0800, Shawn Guo wrote:
On Tue, Jan 15, 2013 at 02:08:34PM +0800, Peter Chen wrote:
For mxs-phy user i.mx6q, the PHY's clock is
On 1/15/2013 9:02 PM, Mike Turquette wrote:
Quoting Afzal Mohammed (2013-01-15 05:44:36)
LCDC IP has a clock divider to adjust pixel clock, this limits pixel
clock range to fck/255 - fck/2(fck - rate of input clock to LCDC IP).
In the case of AM335x, where this IP is present, default fck is
On Tue, Jan 15, 2013 at 7:08 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Grant
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
---
Changes from v4:
- Added gpio line for VBUS of
Hi Ravi,
On Tuesday 15 January 2013 09:36 PM, B, Ravi wrote:
Hi,
On Tue, Jan 15, 2013 at 08:09:22PM +0530, kishon wrote:
Hi Arnd,
On Tuesday 15 January 2013 07:11 PM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of
Hi,
Then, I added the example code in the documentation using EADDRNOTAVAIL.
Yes, I was brave with this one. Yet, EINVAL, EBUSY, ENOENT, did not
really cut it and are so heavily used in drivers that they turned into a
generic something is wrong error. I tried here to use a not overloaded
On Sun, Dec 02, 2012 at 05:12:43AM -0500, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
In case of error, function of_clk_get() returns ERR_PTR()
and never returns NULL. The NULL test in the return value
check should be replaced with IS_ERR().
Signed-off-by: Wei
1 - 100 of 105 matches
Mail list logo
