On Mon, Mar 4, 2013 at 8:00 PM, Tony Lindgren t...@atomide.com wrote:
* Andreas Müller schnitzelt...@googlemail.com [130228 04:50]:
Can you please add a description here? Preferrably something
like With commit XYZ overo poweroff stopped working. Fix this
by blah blah blah so this can be
On Mon, Mar 4, 2013 at 8:00 PM, Tony Lindgren t...@atomide.com wrote:
* Andreas Müller schnitzelt...@googlemail.com [130228 04:50]:
Can you please add a description here? Preferrably something
like With commit XYZ overo poweroff stopped working. Fix this
by blah blah blah so this can be
When setting the GPMC device type, make sure any previous
bits are cleared down, before applying the new setting.
Signed-off-by: Mark Jackson m...@newflow.co.uk
---
Changes in v2:
- Change mux type to 2 bits
- Add extra mux types in gpmc.h
arch/arm/mach-omap2/gpmc.c |4
Commit 80ab72e1 (usb: musb: omap2430: fix the readiness check
in omap_musb_mailbox) made the check incorrect, as we will lose the
glue/link status during the normal built-in probe order (twl4030_usb is
probed after musb omap2430, but before musb core is ready).
As a result, if you boot with USB
Fix the following sparse warning:
drivers/usb/musb/omap2430.c:54:33: warning: symbol '_glue' was not declared.
Should it be static?
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
---
drivers/usb/musb/omap2430.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Commit 51482be9 (ARM: OMAP: USB: Add phy binding information) forgot to
add phy binding for RX-51, and as a result USB does not work anymore on
3.9-rc1. Add the missing binding.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
---
arch/arm/mach-omap2/board-rx51.c |2 ++
1 file changed, 2
On Tue, Mar 05, 2013 at 01:09:40PM +0200, Aaro Koskinen wrote:
Commit 51482be9 (ARM: OMAP: USB: Add phy binding information) forgot to
add phy binding for RX-51, and as a result USB does not work anymore on
3.9-rc1. Add the missing binding.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
On Mon, Mar 04, 2013 at 10:54:24AM -0800, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130304 10:56]:
Hi,
On Mon, Mar 04, 2013 at 10:46:50AM -0800, Tony Lindgren wrote:
The last three are caused by incorrect use of 'select':
warning: (MACH_OMAP_ZOOM2 MACH_OMAP_ZOOM3
On Tuesday 05 March 2013 05:06 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 01:09:40PM +0200, Aaro Koskinen wrote:
Commit 51482be9 (ARM: OMAP: USB: Add phy binding information) forgot to
add phy binding for RX-51, and as a result USB does not work anymore on
3.9-rc1. Add the missing binding.
These are misc fixes and improvements within omapdrm. There is one minor
omapdss fix here too, we get problems in omapdrm without it. The fixes do the
following:
- Make omapdrm smarter to choose the right overlay managers as it's crtcs. This
makes sure that omapdrm is functional for OMAP
modeset_init iterates through all the registered omapdss devices and has some
initial checks to see if the panel has a driver and the required driver ops for
it to be usable by omapdrm.
The function bails out from modeset_init if a panel doesn't meet the
requirements, and stops the registration
The omapdrm driver currently takes a config/module arg to figure out the number
of crtcs it needs to create. We could create as many crtcs as there are overlay
managers in the DSS hardware, but we don't do that because each crtc eats up
one DSS overlay, and that reduces the number of planes we can
The omapdrm driver requires omapdss panel drivers to expose ops like detect,
set_timings and check_timings. These can be NULL for fixed panel DPI, DBI, DSI
and SDI drivers. At some places, there are no checks to see if the panel driver
has these ops or not, and that leads to a crash.
The
The support outputs struct for overlay managers is incorrect for OMAP4. Make
these changes:
- DPI isn't supported via the LCD1 overlay manager, remove DPI as a supported
output.
- the TV manager can suppport DPI, but the omapdss driver doesn't support that
yet, we require some muxing at the
return -EPROBE_DEFER from dwc3_omap_mailbox in dwc3-omap.c, if the probe of
dwc3-omap has not yet been executed or failed.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c |7 +--
include/linux/usb/dwc3-omap.h |6 +++---
2 files changed, 8
While creating the child devices, *of_platform_populate* sets only
coherent_dma_mask but USBHCD sets *uses_dma* (determines whether the
controller is DMA'able) based on dma_mask. So If we haven't explicitly set
dma_mask, the HCD thinks the controller is not DMA'able and the
controller will fail.
No functional change. Replace *_* with *-* in property names of otg to
follow the general convention.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 12 ++--
drivers/usb/musb/omap2430.c|6 +++---
Added palmas-usb driver which is mainly used as comparator driver to
detect vbus/id events when a USB cable is connected and passes on the
event information to omap glue (dwc3-omap.c)
The other fixes include setting dma_mask for dwc3 device since device
tree doesn't fill dma_mask, returning
From: Graeme Gregory g...@slimlogic.co.uk
This is the driver for the OTG transceiver built into the Palmas chip. It
handles the various USB OTG events that can be generated by cable
insertion/removal.
Signed-off-by: Graeme Gregory g...@slimlogic.co.uk
Signed-off-by: Moiz Sonasath
On 3/4/2013 3:21 PM, Russell King - ARM Linux wrote:
Last nights automated ARM build found the following errors with randconfig.
All information as usual at http://www.arm.linux.org.uk/developer/build/
Versatile randconfig:
ERROR: irq_domain_add_simple [drivers/gpio/gpio-em.ko]
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR binding.
Signed-off-by: Jon Hunter
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11
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. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi ba...@ti.com
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. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |7 +++
1 file
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
This series applies cleanly in both for_3.9/dts and 3.8-rc6.
All the patches deal with modifying arch/arm/boot except one which modifies
Documentation/../usb/omap-usb.txt
Changes from v1:
Patch *ARM: dts:
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |8
1 file changed, 8 insertions(+)
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 14 ++
1 file changed, 14
Hi,
On Tue, Mar 05, 2013 at 08:07:03PM +0530, Kishon Vijay Abraham I wrote:
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay
Hello.
On 05-03-2013 18:37, Kishon Vijay Abraham I wrote:
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On 03/05/2013 08:34 AM, Mark Jackson wrote:
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR
On Tue, Mar 05, 2013 at 07:51:57PM +0530, Kishon Vijay Abraham I wrote:
While creating the child devices, *of_platform_populate* sets only
coherent_dma_mask but USBHCD sets *uses_dma* (determines whether the
controller is DMA'able) based on dma_mask. So If we haven't explicitly set
dma_mask,
On Tue, Mar 05, 2013 at 07:51:58PM +0530, Kishon Vijay Abraham I wrote:
return -EPROBE_DEFER from dwc3_omap_mailbox in dwc3-omap.c, if the probe of
dwc3-omap has not yet been executed or failed.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c |7
Hi,
On Tuesday 05 March 2013 08:26 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:58PM +0530, Kishon Vijay Abraham I wrote:
return -EPROBE_DEFER from dwc3_omap_mailbox in dwc3-omap.c, if the probe of
dwc3-omap has not yet been executed or failed.
Signed-off-by: Kishon Vijay Abraham I
Hi,
On Tuesday 05 March 2013 08:11 PM, Sergei Shtylyov wrote:
Hello.
On 05-03-2013 18:37, Kishon Vijay Abraham I wrote:
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Hi,
On Tuesday 05 March 2013 08:24 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:57PM +0530, Kishon Vijay Abraham I wrote:
While creating the child devices, *of_platform_populate* sets only
coherent_dma_mask but USBHCD sets *uses_dma* (determines whether the
controller is DMA'able)
On Tue, Mar 05, 2013 at 08:31:58PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:26 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:58PM +0530, Kishon Vijay Abraham I wrote:
return -EPROBE_DEFER from dwc3_omap_mailbox in dwc3-omap.c, if the probe of
dwc3-omap has not yet been
On Tue, Mar 05, 2013 at 08:29:34PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:24 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:57PM +0530, Kishon Vijay Abraham I wrote:
While creating the child devices, *of_platform_populate* sets only
coherent_dma_mask but USBHCD sets
Hi,
On Tuesday 05 March 2013 08:36 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 08:31:58PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:26 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:58PM +0530, Kishon Vijay Abraham I wrote:
return -EPROBE_DEFER from dwc3_omap_mailbox
On Tue, Mar 05, 2013 at 08:48:24PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:36 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 08:31:58PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:26 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 07:51:58PM +0530, Kishon Vijay
On Mon, 4 Mar 2013, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.8.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.8/20130218214403/
And here's the bloat data, which I usually try to append to the previous
report.
Boot-time memory
On 05/03/13 14:46, Jon Hunter wrote:
On 03/05/2013 08:34 AM, Mark Jackson wrote:
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add
* kishon kis...@ti.com [130305 03:46]:
On Tuesday 05 March 2013 05:06 PM, Felipe Balbi wrote:
On Tue, Mar 05, 2013 at 01:09:40PM +0200, Aaro Koskinen wrote:
Commit 51482be9 (ARM: OMAP: USB: Add phy binding information) forgot to
add phy binding for RX-51, and as a result USB does not work
On 03/05/2013 07:21 AM, Kishon Vijay Abraham I wrote:
From: Graeme Gregory g...@slimlogic.co.uk
This is the driver for the OTG transceiver built into the Palmas chip. It
handles the various USB OTG events that can be generated by cable
diff --git
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.9-rc1/fixes-signed
for you to fetch changes up to
On 03/05/2013 10:20 AM, Mark Jackson wrote:
On 05/03/13 14:46, Jon Hunter wrote:
On 03/05/2013 08:34 AM, Mark Jackson wrote:
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR
Hi Jon,
On Tue, Mar 5, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
This really highlights a weakness in the GPMC driver, particularly
for NOR, where the child device can only be probed once the parent
is probed. I don't see this as being DT specific issue, because
even on older OMAP
On 03/05/2013 11:43 AM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Mar 5, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
This really highlights a weakness in the GPMC driver, particularly
for NOR, where the child device can only be probed once the parent
is probed. I don't see this as
* Andreas Müller schnitzelt...@googlemail.com [130305 00:19]:
Sorry for the noise but I am newbie here and have one question:
Against which branch should patches send here be based on. Up to now I
used Linus' mainline branch - is that OK?
Yes that's perfect. It's usually best to use the most
On Fri, Mar 1, 2013 at 10:07 PM, Andreas Müller
schnitzelt...@googlemail.com wrote:
On Thu, Feb 28, 2013 at 5:27 PM, Andreas Müller
schnitzelt...@googlemail.com wrote:
Hi,
I am preparing 3.8 mainline for gumstix overo and have the following
issue: waking Monitor connected by HDMI from power
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 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 aaf44122..a13d710 100644
---
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 | 27 +++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git
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
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
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 80b6997..3b7ea20 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@
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
Acked-by: Sekhar Nori nsek...@ti.com
---
arch/arm/common/edma.c | 37
Changes since v7:
- Dropped dmaengine compat() patch. It is upstream.
- Submitted edma_alloc_slot() error checking bug fix separately,
now a dependency
- Fixed bisect issues due to 3/10 hunks that went into 1/10
- Fixed incorrect IS_ERRVALUE() use in 3/10
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 EDMA
crossbar event mux support. Enables build on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Sekhar Nori
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Sekhar Nori nsek...@ti.com
---
arch/arm/Kconfig |1 +
arch/arm/common/Kconfig|
Changes since v1:
- rebase to 3.9-rc1, previous dependencies upstream
This series adds DT DMA Engine Client support to the omap_hsmmc.
It leverages the generic DMA OF helpers in -next and the
dma_request_slave_channel_compat() wrapper introduced in the
AM33XX DMA Engine series to support
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports platforms booting
with or without DT populated.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
drivers/mmc/host/omap_hsmmc.c | 10 --
1 file changed, 8
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 | 26 +++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git
From: Santosh Shilimkar santosh.shilim...@ti.com
MMC driver probe will abort for DT case because of failed
platform_get_resource_byname() lookup. Fix it by skipping resource
byname lookup for device tree build.
Issue is hidden because hwmod popullates the IO resources which
helps to succeed
On Tuesday 05 March 2013, Matt Porter wrote:
Changes since v1:
- rebase to 3.9-rc1, previous dependencies upstream
This series adds DT DMA Engine Client support to the omap_hsmmc.
It leverages the generic DMA OF helpers in -next and the
dma_request_slave_channel_compat() wrapper
On 03/05/2013 11:30 AM, Jon Hunter wrote:
On 03/05/2013 10:20 AM, Mark Jackson wrote:
[snip]
But I can see in physmap_of.c that the device gets registered without any
call to
devm_pinctrl_get_select_default() and hence no probe deferring takes place
is the
pinctrl device hasn't yet been
This is the result of my my build tests on 3.9-rc1, mostly bugs
that I had not caught before the merge window, or where the fix
for some reason has not yet made it in.
I hope the subsystem maintainers can take care of applying these,
for the arch/arm/mach-* patches I can either apply them
The recent reorganization of OMAP header files caused a couple of
files that used to be implicitly included now missing from OMAP1.
This adds explicit inclusions of mach/irqs.h and mach/hardware.h
in all files that need them for an OMAP1 allyesconfig build.
Signed-off-by: Arnd Bergmann
On Tuesday 05 March 2013, Arnd Bergmann wrote:
The recent reorganization of OMAP header files caused a couple of
files that used to be implicitly included now missing from OMAP1.
This adds explicit inclusions of mach/irqs.h and mach/hardware.h
in all files that need them for an OMAP1
On Tuesday 05 March 2013, Tony Lindgren wrote:
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
On Tue, Mar 5, 2013 at 9:17 AM, Archit Taneja arc...@ti.com wrote:
modeset_init iterates through all the registered omapdss devices and has some
initial checks to see if the panel has a driver and the required driver ops
for
it to be usable by omapdrm.
The function bails out from
On Tue, Mar 5, 2013 at 9:17 AM, Archit Taneja arc...@ti.com wrote:
The omapdrm driver requires omapdss panel drivers to expose ops like detect,
set_timings and check_timings. These can be NULL for fixed panel DPI, DBI, DSI
and SDI drivers. At some places, there are no checks to see if the panel
* Arnd Bergmann a...@arndb.de [130305 14:31]:
On Tuesday 05 March 2013, Arnd Bergmann wrote:
The recent reorganization of OMAP header files caused a couple of
files that used to be implicitly included now missing from OMAP1.
This adds explicit inclusions of mach/irqs.h and mach/hardware.h
Hi Tony,
From: linux-arm-kernel [mailto:linux-arm-kernel-
boun...@lists.infradead.org] On Behalf Of Anil Kumar
Sent: Wednesday, February 27, 2013 8:03 AM
To: devicetree-disc...@lists.ozlabs.org; linux-omap@vger.kernel.org;
linux-ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Hi,
On Wed, Mar 06, 2013 at 02:23:12, Porter, Matt wrote:
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
77 matches
Mail list logo
