On Thu, Mar 07, 2013 at 12:23:25AM +0200, Aaro Koskinen wrote:
> omap_udc platform device is not registered properly anymore:
> CONFIG_USB_GADGET_OMAP was deleted by 193ab2a6 (usb: gadget: allow
> multiple gadgets to be built) already in v3.1.
>
> Fix by using CONFIG_USB_OMAP instead. Tested on No
On Wednesday 06 March 2013 06:15 AM, Rob Clark wrote:
On Tue, Mar 5, 2013 at 9:17 AM, Archit Taneja 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,
Hi,
On 03/06/2013 06:53 PM, Tony Lindgren wrote:
> * Anil Kumar [130305 18:40]:
>> 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.o
On Wed, Mar 6, 2013 at 6:15 PM, Matt Porter wrote:
> 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.
> --- a/arch/arm/c
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Porter, Matt
> Sent: Thursday, March 07, 2013 9:47 AM
> To: Krishnamoorthy, Balaji T; Chris Ball; Cousson, Benoit; Tony
> Lindgren; Russell King
> Cc: Devicetree Discuss;
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_slave_sg_limits() API. If the max_nr_segs
limit is present, the value is used t
Adds AM33XX MMC support for am335x-bone, am335x-evm, and
am335x-evmsk.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
arch/arm/boot/dts/am335x-evmsk.dts |7 +++
arch/arm/boot/dt
This series enable MMC support on AM33xx platforms. Support for
platforms incorporating the EDMA DMAC is added using the
dma_get_slave_sg_limits() api. AM33xx DTS supported is added for
Beaglebone, AM335x-EVM, and AM335x-EVMSK.
These patches were split out from the v5 version of the AM33xx
DMA ser
On 03/06/2013 04:39 PM, Jon Hunter wrote:
>
> On 03/05/2013 04:13 AM, Mark Jackson wrote:
>> When setting the GPMC device type, make sure any previous
>> bits are cleared down, before applying the new setting.
>>
>> Signed-off-by: Mark Jackson
>> ---
>> Changes in v2:
>> - Change mux type to 2 b
On 03/05/2013 04:13 AM, Mark Jackson wrote:
> When setting the GPMC device type, make sure any previous
> bits are cleared down, before applying the new setting.
>
> Signed-off-by: Mark Jackson
> ---
> Changes in v2:
> - Change mux type to 2 bits
> - Add extra mux types in gpmc.h
>
> arch/arm/
omap_udc platform device is not registered properly anymore:
CONFIG_USB_GADGET_OMAP was deleted by 193ab2a6 (usb: gadget: allow
multiple gadgets to be built) already in v3.1.
Fix by using CONFIG_USB_OMAP instead. Tested on Nokia 770 by checking
that omap_udc is probed & working properly when built
On Wed, Mar 06, 2013 at 09:20:16PM +0100, Pali Rohár wrote:
> On Wednesday 06 March 2013 21:12:06 Pali Rohár wrote:
> > On Sunday 17 February 2013 20:03:03 Aaro Koskinen wrote:
> > > On Sun, Feb 17, 2013 at 04:16:49PM +0100, Pali Rohár wrote:
> > > > +/*
> > > > + * arch/arm/mach-omap2/board-rx51-c
Hi,
Adding Mike, Paul and Rajendra.
* Piotr Haber [130306 08:30]:
>
> I run into same problem, 3.9-rc1 builds fail to boot on mu panda
> have all the things mentioned above in my .config
...
Hmm this seems to be related to the recent generic clock conversion
and CONFIG_DEBUG_SLAB=y in your .co
On Wed, Mar 06, 2013 at 08:24:06PM +, Peter Korsgaard wrote:
> > "Matt" == Matt Porter writes:
>
> Matt> The binding definition is based on the generic DMA controller
> Matt> binding.
>
> Matt> Signed-off-by: Matt Porter
> Matt> ---
> Matt> Documentation/devicetree/bindings/dma/ti
> "Matt" == Matt Porter writes:
Matt> The binding definition is based on the generic DMA controller
Matt> binding.
Matt> Signed-off-by: Matt Porter
Matt> ---
Matt> Documentation/devicetree/bindings/dma/ti-edma.txt | 49
+
Matt> 1 file changed, 49 insertions(+)
On Wednesday 06 March 2013 21:12:06 Pali Rohár wrote:
> On Sunday 17 February 2013 20:03:03 Aaro Koskinen wrote:
> > Hi,
> >
> > On Sun, Feb 17, 2013 at 04:16:49PM +0100, Pali Rohár wrote:
> > > +/*
> > > + * arch/arm/mach-omap2/board-rx51-camera.c
> > > + *
> > > + * Copyright (C) 2008 Nokia Corp
On Sunday 17 February 2013 20:03:03 Aaro Koskinen wrote:
> Hi,
>
> On Sun, Feb 17, 2013 at 04:16:49PM +0100, Pali Rohár wrote:
> > I'm sending ADP1653 flash torch board code for Nokia RX-51.
> > Kernel driver ADP1653 is already in upstream kernel. Board
> > code was extracted from this big camera
On Wednesday 06 March 2013 18:51:21 Tony Lindgren wrote:
> * Pali Rohár [130306 06:13]:
> > On Monday 04 March 2013 19:58:06 Tony Lindgren wrote:
> > > * Nishanth Menon [130301 06:42]:
> > > > On Fri, Mar 1, 2013 at 1:47 AM, Ивайло Димитров
> >
> > wrote:
> > > > > They look similar, but they a
On 03/06/2013 11:00 AM, Jon Hunter wrote:
>
> On 03/06/2013 10:48 AM, Mark Jackson wrote:
>> On 06/03/13 16:44, Jon Hunter wrote:
>>>
>>> On 03/06/2013 07:30 AM, Mark Jackson wrote:
On 06/03/13 10:23, Mark Jackson wrote:
>>
>>
>>
> [1.541884] gpmc_probe_nor_child 1
> [1.5454
* Arnd Bergmann [130306 03:27]:
> On Wednesday 06 March 2013, Tony Lindgren wrote:
> > * Arnd Bergmann [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 n
* Anil Kumar [130305 18:40]:
> 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...@vge
* Pali Rohár [130306 06:13]:
> On Monday 04 March 2013 19:58:06 Tony Lindgren wrote:
> > * Nishanth Menon [130301 06:42]:
> > > On Fri, Mar 1, 2013 at 1:47 AM, Ивайло Димитров
> wrote:
> > > > They look similar, but they are not equivalent :). The
> > > > first major difference is here (code ta
On 03/06/2013 10:48 AM, Mark Jackson wrote:
> On 06/03/13 16:44, Jon Hunter wrote:
>>
>> On 03/06/2013 07:30 AM, Mark Jackson wrote:
>>> On 06/03/13 10:23, Mark Jackson wrote:
>
>
>
[1.541884] gpmc_probe_nor_child 1
[1.545483] GPMC_CS_CONFIG7_0 : 0f48
[1.549621] G
On Wed, Mar 6, 2013 at 1:46 PM, Jon Hunter wrote:
>
> On 03/06/2013 05:58 AM, Ezequiel Garcia wrote:
>> I'll submit this driver by the end of this week, in case you want
>> to take a look at it.
>
> Ok, but this is not for omap right?
>
No, this is a new driver for a memory controller that's avai
On 06/03/13 16:44, Jon Hunter wrote:
>
> On 03/06/2013 07:30 AM, Mark Jackson wrote:
>> On 06/03/13 10:23, Mark Jackson wrote:
>>> [1.541884] gpmc_probe_nor_child 1
>>> [1.545483] GPMC_CS_CONFIG7_0 : 0f48
>>> [1.549621] GPMC_CS_CONFIG7_1 : 0f58
>>> [1.553812] GPMC_CS_CON
On 03/06/2013 05:58 AM, Ezequiel Garcia wrote:
> Jon,
>
> On Tue, Mar 5, 2013 at 6:34 PM, Jon Hunter wrote:
>>
>> By the way, with this version you should remove "simple-bus" from your
>> gpmc node compatible strings. I now call of_platform_device_create() to
>> create the child device during th
On 03/06/2013 07:30 AM, Mark Jackson wrote:
> On 06/03/13 10:23, Mark Jackson wrote:
>> On 05/03/13 21:34, Jon Hunter wrote:
>>>
>>> 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 get
On 03/06/2013 07:56 AM, Matt Porter wrote:
> On Wed, Mar 06, 2013 at 07:12:29PM +0530, Balaji T K wrote:
>> On Wednesday 06 March 2013 02:43 AM, Matt Porter wrote:
>>> From: Santosh Shilimkar
>>>
>>> MMC driver probe will abort for DT case because of failed
>>> platform_get_resource_byname() look
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
Acked-by: Sekhar Nori
---
arch/arm/Kconfig |1 +
arch/arm/common/Kconfig|3 +
arch/arm/common/Makefi
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/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 OMA
The binding definition is based on the generic DMA request binding
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 27 +++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/spi/omap-spi.txt
b/Do
Adds DMA resources to the AM33XX SPI nodes.
Signed-off-by: Matt Porter
---
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 cbea5ab..c3c781a 100644
--- a/arch/arm/boot/dts/am33xx.dt
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt
diff --git
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter
---
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
@@ -222,7 +222,7 @@
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
Acked-by: Sekhar Nori
---
arch/arm/common/edma.c | 37 -
1 file chan
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
Acked-by: Sekhar Nori
---
arch/arm/common/edma.c
Changes since v8:
- Removed edma node interrupt-parent property, it is inherited
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 d
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
Acked-by: Arnd Bergmann
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 26 +++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/Docum
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
Acked-by: Tony Lindgren
Acked-by: Arnd Bergmann
---
drivers/mmc/host/omap_hsmmc.c | 10 --
1 file changed, 8 insertio
Changes since v2:
- dropped skip platform_get_resource_byname() patch
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 and the
dma_request_slave_channel_com
On Monday 04 March 2013 19:58:06 Tony Lindgren wrote:
> * Nishanth Menon [130301 06:42]:
> > On Fri, Mar 1, 2013 at 1:47 AM, Ивайло Димитров
wrote:
> > > They look similar, but they are not equivalent :). The
> > > first major difference is here (code taken from
> > > omap-smc.S)
> > >
> > >> E
On Wed, Mar 06, 2013 at 04:19:58AM +, Kumar, Anil wrote:
> 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
> > ---
> > arch
On Wed, Mar 06, 2013 at 07:12:29PM +0530, Balaji T K wrote:
> On Wednesday 06 March 2013 02:43 AM, Matt Porter wrote:
> >From: Santosh Shilimkar
> >
> >MMC driver probe will abort for DT case because of failed
> >platform_get_resource_byname() lookup. Fix it by skipping resource
> >byname lookup f
On Wednesday 06 March 2013 02:43 AM, Matt Porter wrote:
From: Santosh Shilimkar
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 reso
On Tue, Mar 05, 2013 at 09:26:01PM +, Arnd Bergmann wrote:
> 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
On 06/03/13 10:23, Mark Jackson wrote:
> On 05/03/13 21:34, Jon Hunter wrote:
>>
>> 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_pinctr
Jon,
On Tue, Mar 5, 2013 at 6:34 PM, Jon Hunter wrote:
>
> By the way, with this version you should remove "simple-bus" from your
> gpmc node compatible strings. I now call of_platform_device_create() to
> create the child device during the GPMC probe. I think that this is a
> safer approach.
>
On Wednesday 06 March 2013, Tony Lindgren wrote:
> * Arnd Bergmann [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 expl
On 05/03/13 21:34, Jon Hunter wrote:
>
> 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 defer
> Оригинално писмо
>От: Aaro Koskinen
>Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround
>До: Ивайло Димитров
>Изпратено на: Събота, 2013, Март 2 01:51:39 EET
>
>
>On Fri, Mar 01, 2013 at 12:09:12PM +0200, Ивайло Димитров wrote:
>> Unfortunately
On Wednesday 06 March 2013 02:49 PM, Felipe Balbi wrote:
Hi,
On Wed, Mar 06, 2013 at 02:25:48PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
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 d
Hi,
On Wed, Mar 06, 2013 at 02:25:48PM +0530, kishon wrote:
> Hi,
>
> On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
> >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 fil
2013/3/5 Andreas Müller :
> On Fri, Mar 1, 2013 at 10:07 PM, Andreas Müller
> wrote:
>> On Thu, Feb 28, 2013 at 5:27 PM, Andreas Müller
>> wrote:
>>> Hi,
>>>
>>> I am preparing 3.8 mainline for gumstix overo and have the following
>>> issue: waking Monitor connected by HDMI from power save makes
Hi,
On Tuesday 05 March 2013 05:11 PM, kishon wrote:
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
Hi,
On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
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/devicet
56 matches
Mail list logo