-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony
The following changes since commit 8f0d8163b50e01f398b14bcd4dc039ac5ab18d64:
Linux 3.7-rc3 (2012-10-28 12:24:48 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
tags/omap
Here's the updated patch for this one.
- Paul
From: Tero Kristo
Date: Mon, 29 Oct 2012 22:02:13 -0600
Subject: [PATCH 1/3] ARM: OMAP: hwmod: wait for sysreset complete after
enabling hwmod
When waking up from off-mode, some IP blocks are reset automatically by
hardware. For this reason, soft
Hi
On Wed, 31 Oct 2012, Jean Pihet wrote:
> Paul,
> Could you please check with the 2 calls to PM QoS from the I2C code
> commented out? This will rule out the PM QoS impact.
Will be happy to do a test run for you, after the boot log from your local
test run is posted:
http://marc.info/?l=linu
On 10/31/2012 10:57 AM, Pantelis Antoniou wrote:
> This simple patch enables dynamic changes of the DT tree on runtime
> to be visible to the device-tree proc interface.
>
> Signed-off-by: Pantelis Antoniou
Acked-by: Rob Herring
> ---
> arch/arm/include/asm/prom.h | 2 ++
> 1 file changed, 2
On Wed, Oct 31, 2012 at 3:07 PM, Pantelis Antoniou
wrote:
>
> On Oct 31, 2012, at 11:55 PM, Russ Dill wrote:
>
>> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
>> wrote:
>>> Introducing capebus; a bus that allows small boards (capes) to connect
>>> to a complex SoC using simple expansion con
* Lokesh Vutla [121029 00:03]:
> Is the above discussion fine for you ?
> Will you pick this patch or
> you want any more modifications ?
Let's see what Arnd says.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.k
* Laurent Pinchart [121031 16:03]:
> Hi Tony,
>
> On Wednesday 31 October 2012 13:58:50 Tony Lindgren wrote:
> > * Tony Lindgren [121030 16:55]:
> > > This code should be private to mach-omap2.
> > >
> > > The only use for it in for omap1 has been in dmtimer.c
> > > to check for context loss. H
Hi Tony,
On Wednesday 31 October 2012 13:58:50 Tony Lindgren wrote:
> * Tony Lindgren [121030 16:55]:
> > This code should be private to mach-omap2.
> >
> > The only use for it in for omap1 has been in dmtimer.c
> > to check for context loss. However, omap1 does not
> > lose context during idle,
* Tony Lindgren [121030 16:54]:
> Let's make the omap2+ specific parts private to mach-omap2.
>
> This leaves just a minimal shared code into plat-omap like
> it should be.
Found an error with make randconfig if we have
CONFIG_OMAP4_ERRATA_I688 enabled, I'll fold in the
following fix to this pat
Hi,
On Wed, Oct 31, 2012 at 11:36:25PM +0200, Pantelis Antoniou wrote:
> > * Pantelis Antoniou [121031 13:14]:
> >> On Oct 31, 2012, at 9:55 PM, Benoit Cousson wrote:
> >>>
> >>> Yeah, I do agree. I'm confused as well. Only OMAP IPs under PRCM control
> >>> could have an hwmod and thus must be h
* Pantelis Antoniou [121031 15:02]:
>
> So when device's node is 'disabled' of_platform_device_create_pdata()
> will not create the device.
>
> Now, of course it is possible to re-trigger the platform's probe method
> to be called, and in fact I do so in the capebus patches.
You should fix this
As discussed on linux-arm-kernel, we want to avoid
relative includes for the arch/arm/*omap* code:
http://www.spinics.net/lists/linux-omap/msg80520.html
Fix serial.h by moving it to mach/serial.h.
Signed-off-by: Tony Lindgren
diff --git a/arch/arm/mach-omap2/include/mach/debug-macro.S
b/arch/
On Oct 31, 2012, at 11:55 PM, Russ Dill wrote:
> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
> wrote:
>> Introducing capebus; a bus that allows small boards (capes) to connect
>> to a complex SoC using simple expansion connectors.
>>
[snip]
>> + if (drv) {
>> + /* ca
Hi Russ,
On Oct 31, 2012, at 11:56 PM, Russ Dill wrote:
> On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
> wrote:
>> Capebus is created to address the problem of many SoCs that can provide a
>> multitude of hardware interfaces but in order to keep costs down the main
>> boards only support a
Hi Tony,
On Oct 31, 2012, at 11:43 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 14:38]:
>>
>> There a a whole bunch of conflicting capes. There's no
>> way to instantiate them together. They must be instantiated
>> only after their EEPROMs are read and they are matched
>> to their cor
On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
wrote:
> Capebus is created to address the problem of many SoCs that can provide a
> multitude of hardware interfaces but in order to keep costs down the main
> boards only support a limited number of them. The rest are typically brought
> out to
On Wed, Oct 31, 2012 at 9:52 AM, Pantelis Antoniou
wrote:
> Introducing capebus; a bus that allows small boards (capes) to connect
> to a complex SoC using simple expansion connectors.
>
> Up to now to support these kind of boards, one had to hack the board files,
> and do all sort of gymnastics t
As discussed on linux-arm-kernel, we want to avoid
relative includes for the arch/arm/*omap* code:
http://www.spinics.net/lists/linux-omap/msg80520.html
Fix includes for fpga.h by making fpga.h local
to mach-omap1. The common code in plat-omap just
needs to know the struct h2p2_dbg_fpga, which ca
* Pantelis Antoniou [121031 14:38]:
>
> There a a whole bunch of conflicting capes. There's no
> way to instantiate them together. They must be instantiated
> only after their EEPROMs are read and they are matched
> to their corresponding cape drivers.
You don't need to instantiate the capes dur
Tony,
On Oct 31, 2012, at 11:26 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 13:14]:
>> On Oct 31, 2012, at 9:55 PM, Benoit Cousson wrote:
>>>
>>> Yeah, I do agree. I'm confused as well. Only OMAP IPs under PRCM control
>>> could have an hwmod and thus must be handled by an omap_devic
* Pantelis Antoniou [121031 13:14]:
> On Oct 31, 2012, at 9:55 PM, Benoit Cousson wrote:
> >
> > Yeah, I do agree. I'm confused as well. Only OMAP IPs under PRCM control
> > could have an hwmod and thus must be handled by an omap_device.
> >
> > Any devices that is created later cannot be omap_d
* Tony Lindgren [121030 16:55]:
> As discussed on linux-arm-kernel, we want to avoid
> relative includes for the arch/arm/*omap* code:
>
> http://www.spinics.net/lists/linux-omap/msg80520.html
>
> Note that eventually when the omap1 specific drivers
> are fixed to not use cpu_is_omap macros and
Hi Kevin,
On Wed, Oct 31, 2012 at 6:49 AM, Kevin Hilman
wrote:
> Hi Jean,
>
> Jean Pihet writes:
>
> [...]
>
>>> Based on a very quick look, I'd say the original patch 3db11fe is broken.
>>> I don't see how it can ensure that its PM_QOS_CPU_DMA_LATENCY request is
>>> honored when CONFIG_CPU_IDLE
* Tony Lindgren [121030 16:55]:
> This code should be private to mach-omap2.
>
> The only use for it in for omap1 has been in dmtimer.c
> to check for context loss. However, omap1 does not
> lose context during idle, so the code is not needed.
> Further, omap1 timer has OMAP_TIMER_ALWON set, so o
Hi,
On Thu, Nov 01, 2012 at 01:21:36AM +0530, Venkatraman S wrote:
> On Wed, Oct 31, 2012 at 5:56 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Oct 31, 2012 at 05:27:36PM +0530, Hebbar, Gururaja wrote:
> >> HSMMC IP on AM33xx need a special setting to handle High-speed cards.
> >> Other platfor
Hi Benoit,
On Oct 31, 2012, at 9:55 PM, Benoit Cousson wrote:
> Hi Panto,
>
> On 10/31/2012 07:09 PM, Tony Lindgren wrote:
>> * Pantelis Antoniou [121031 11:05]:
>>> Hi Tony,
>>>
>>> On Oct 31, 2012, at 7:52 PM, Tony Lindgren wrote:
>>>
* Pantelis Antoniou [121031 10:26]:
> It is pa
Linus Walleij writes:
> On Tue, Oct 30, 2012 at 12:34 PM, Mark Brown
> wrote:
>> On Sun, Oct 28, 2012 at 09:12:52PM +0100, Linus Walleij wrote:
>
>>> Moving this handling to bus code or anywhere else
>>> invariably implies that resource acquisition/release order
>>> does not matter, and my point
Hi Panto,
On 10/31/2012 07:09 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 11:05]:
>> Hi Tony,
>>
>> On Oct 31, 2012, at 7:52 PM, Tony Lindgren wrote:
>>
>>> * Pantelis Antoniou [121031 10:26]:
It is painless to move the adapter DT devices to arch/arm/mach-omap2
However
On Wed, Oct 31, 2012 at 20:47:27, Cousson, Benoit wrote:
> Hi,
>
> On 10/29/2012 09:21 AM, Vaibhav Hiremath wrote:
> > From: Mugunthan V N
> >
> > Add CPSW and MDIO related device tree data for AM33XX.
> > Also enable them into board/evm dts files by providing
> > respective phy-id.
>
> Is ther
On Wed, Oct 31, 2012 at 5:56 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Oct 31, 2012 at 05:27:36PM +0530, Hebbar, Gururaja wrote:
>> HSMMC IP on AM33xx need a special setting to handle High-speed cards.
>> Other platforms like TI81xx, OMAP4 may need this as-well. This depends
>> on the HSMMC IP tim
Hi Aaro,
On Wednesday, October 31, 2012 08:03:46 PM Aaro Koskinen wrote:
> Add Retu power button driver.
>
> Cc: linux-in...@vger.kernel.org
> Acked-by: Felipe Balbi
> Signed-off-by: Aaro Koskinen
> ---
> drivers/input/misc/Kconfig | 10 +++
> drivers/input/misc/Makefile |
On 10/31/2012 07:43 PM, Pantelis Antoniou wrote:
>
> On Oct 31, 2012, at 8:36 PM, Lars-Peter Clausen wrote:
>
>> On 10/31/2012 07:12 PM, Pantelis Antoniou wrote:
>>>
>>> On Oct 31, 2012, at 8:07 PM, Lars-Peter Clausen wrote:
>>>
On 10/31/2012 06:55 PM, Pantelis Antoniou wrote:
> [...]
>>
On Oct 31, 2012, at 8:36 PM, Lars-Peter Clausen wrote:
> On 10/31/2012 07:12 PM, Pantelis Antoniou wrote:
>>
>> On Oct 31, 2012, at 8:07 PM, Lars-Peter Clausen wrote:
>>
>>> On 10/31/2012 06:55 PM, Pantelis Antoniou wrote:
[...]
>> }
>>
>> indio_dev->channels = chan_array;
>
On Wed, Oct 31, 2012 at 08:03:44PM +0200, Aaro Koskinen wrote:
> Retu is a multi-function device found on Nokia Internet Tablets
> implementing at least watchdog, RTC, headset detection and power button
> functionality.
>
> This patch implements minimum functionality providing register access,
> I
On Wed, Oct 31, 2012 at 08:03:43PM +0200, Aaro Koskinen wrote:
> Add i2c driver to enable access to devices behind CBUS on Nokia Internet
> Tablets.
>
> The patch also adds CBUS I2C configuration for N8x0 which is one of the
> users of this driver.
>
> Cc: linux-...@vger.kernel.org
> Acked-by: Fe
On 10/31/2012 07:12 PM, Pantelis Antoniou wrote:
>
> On Oct 31, 2012, at 8:07 PM, Lars-Peter Clausen wrote:
>
>> On 10/31/2012 06:55 PM, Pantelis Antoniou wrote:
>>> [...]
> }
>
> indio_dev->channels = chan_array;
> + indio_dev->num_channels = channels;
> +
> + size =
* Keshava Munegowda [121031 07:29]:
> The USB2 Host device node is extracted and used in the probe
> of the driver to initialize the usb ports and controller. The
> platform specific initialization is also performed.
>
> Signed-off-by: Keshava Munegowda
> ---
> arch/arm/mach-omap2/usb-host.c
On Oct 31, 2012, at 8:09 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 11:05]:
>> Hi Tony,
>>
>> On Oct 31, 2012, at 7:52 PM, Tony Lindgren wrote:
>>
>>> * Pantelis Antoniou [121031 10:26]:
It is painless to move the adapter DT devices to arch/arm/mach-omap2
However I
* Loic PALLARDY [121031 01:48]:
>
> Hi Omar,
>
> On 10/31/2012 08:22 AM, Omar Ramirez Luna wrote:
> >
> > As part of plat-omap code cleanup, I was planning to move omap-mailbox
> > framework to a newly drivers/mailbox folder, right now this code is
> > specific to OMAP platforms, but with some c
On Oct 31, 2012, at 1:55 PM, Pantelis Antoniou wrote:
>
> On Oct 31, 2012, at 7:52 PM, Lars-Peter Clausen wrote:
>
>> On 11/01/2012 04:24 PM, Pantelis Antoniou wrote:
>>> Add an IIO map interface that consumers can use.
>>
>> Hi,
>>
>> Looks like you overlooked the review comments I had inlin
On Oct 31, 2012, at 8:07 PM, Lars-Peter Clausen wrote:
> On 10/31/2012 06:55 PM, Pantelis Antoniou wrote:
>> [...]
}
indio_dev->channels = chan_array;
+ indio_dev->num_channels = channels;
+
+ size = (channels + 1) * sizeof(struct iio_map);
+ adc_dev->
* Pantelis Antoniou [121031 11:05]:
> Hi Tony,
>
> On Oct 31, 2012, at 7:52 PM, Tony Lindgren wrote:
>
> > * Pantelis Antoniou [121031 10:26]:
> >> It is painless to move the adapter DT devices to arch/arm/mach-omap2
> >>
> >> However I got bit by the __init at omap_build_device family functio
On 10/31/2012 06:55 PM, Pantelis Antoniou wrote:
> [...]
>>> }
>>>
>>> indio_dev->channels = chan_array;
>>> + indio_dev->num_channels = channels;
>>> +
>>> + size = (channels + 1) * sizeof(struct iio_map);
>>> + adc_dev->map = kzalloc(size, GFP_KERNEL);
>>> + if (adc_dev->map == NU
On Oct 31, 2012, at 7:55 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 10:41]:
>> Introduce beaglebone capebus board support.
> ...
>
>> --- /dev/null
>> +++ b/drivers/capebus/boards/Kconfig
>> @@ -0,0 +1,6 @@
>> +config CAPEBUS_BONE_CONTROLLER
>> +bool "Beaglebone capebus board co
Introduce Retu watchdog driver.
Cc: linux-watch...@vger.kernel.org
Acked-by: Felipe Balbi
Acked-by: Tony Lindgren
Signed-off-by: Aaro Koskinen
---
drivers/watchdog/Kconfig| 12 +++
drivers/watchdog/Makefile |1 +
drivers/watchdog/retu_wdt.c | 178 ++
Add i2c driver to enable access to devices behind CBUS on Nokia Internet
Tablets.
The patch also adds CBUS I2C configuration for N8x0 which is one of the
users of this driver.
Cc: linux-...@vger.kernel.org
Acked-by: Felipe Balbi
Acked-by: Tony Lindgren
Signed-off-by: Aaro Koskinen
---
arch/ar
Retu is a multi-function device found on Nokia Internet Tablets
implementing at least watchdog, RTC, headset detection and power button
functionality.
This patch implements minimum functionality providing register access,
IRQ handling and power off functions.
Cc: sa...@linux.intel.com
Acked-by: F
Hi Tony,
On Oct 31, 2012, at 7:52 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [121031 10:26]:
>> It is painless to move the adapter DT devices to arch/arm/mach-omap2
>>
>> However I got bit by the __init at omap_build_device family functions.
>> If you don't remove it, crashes every time you
Add Retu power button driver.
Cc: linux-in...@vger.kernel.org
Acked-by: Felipe Balbi
Signed-off-by: Aaro Koskinen
---
drivers/input/misc/Kconfig | 10 +++
drivers/input/misc/Makefile |1 +
drivers/input/misc/retu-pwrbutton.c | 118 +++
3 f
This patch set introduces drivers for CBUS access and Retu multifunction
chip found on Nokia Internet Tablets (770, N800, N810). It would be
nice get these patches applied as the functionality of these devices is
severely lacking without Retu. E.g. watchdog support is mandatory at
least on Nokia N8
* Pantelis Antoniou [121031 10:41]:
> Introduce beaglebone capebus board support.
...
> --- /dev/null
> +++ b/drivers/capebus/boards/Kconfig
> @@ -0,0 +1,6 @@
> +config CAPEBUS_BONE_CONTROLLER
> + bool "Beaglebone capebus board controller"
> + depends on CAPEBUS && ARCH_OMAP2PLUS && OF &&
On Oct 31, 2012, at 7:52 PM, Lars-Peter Clausen wrote:
> On 11/01/2012 04:24 PM, Pantelis Antoniou wrote:
>> Add an IIO map interface that consumers can use.
>
> Hi,
>
> Looks like you overlooked the review comments I had inline last time. I've
> put them in again, see below.
>
>>
>> Signed-o
On 11/01/2012 04:24 PM, Pantelis Antoniou wrote:
> Add an IIO map interface that consumers can use.
Hi,
Looks like you overlooked the review comments I had inline last time. I've
put them in again, see below.
>
> Signed-off-by: Pantelis Antoniou
> ---
> drivers/iio/adc/ti_am335x_adc.c | 60
>
* Pantelis Antoniou [121031 10:26]:
> It is painless to move the adapter DT devices to arch/arm/mach-omap2
>
> However I got bit by the __init at omap_build_device family functions.
> If you don't remove it, crashes every time you instantiate a device
> at runtime, or you load the cape driver as
Introducing capebus; a bus that allows small boards (capes) to connect
to a complex SoC using simple expansion connectors.
Up to now to support these kind of boards, one had to hack the board files,
and do all sort of gymnastics to handle all the different cases of
conflict resolution.
Capebus pr
Introducing beaglebone generic cape support.
With this you can create almost any kind of cape driver
that doesn't require complex interconnection of the parts.
Most beaglebone capes can be created with this, including
all the display capes (DVI/VGA/LCD) with touchscreen or not,
capes that only us
Support beaglebone's geiger cape.
The geiger cape allows you to measure the amount of
ionising radiation in your area, and as an example
of how to create a complex non-generic cape driver.
Signed-off-by: Pantelis Antoniou
---
drivers/capebus/capes/Kconfig| 7 +
drivers/capebus/cap
Update the common beaglebone's DTS with the required DT
entries for all known working capes as of now.
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 689 --
1 file changed, 659 insertions(+), 30 deletions(-)
diff --git a/arch/arm/bo
Small summary of capebus.
Signed-off-by: Pantelis Antoniou
---
Documentation/capebus/capebus-summary | 40 +++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/capebus/capebus-summary
diff --git a/Documentation/capebus/capebus-summary
b/Documen
Describe capebus DT bindings in detail.
Signed-off-by: Pantelis Antoniou
---
.../capebus/bone-capebus-slot-override.txt | 28 +++
.../devicetree/bindings/capebus/bone-capebus.txt | 50 +++
.../bindings/capebus/bone-geiger-cape.txt | 78 +
.../bindin
Introduce beaglebone capebus board support.
This patch creates the beaglebone's board cape bus controller.
The board controller is responsible for the probing of capes
at the well defined I2C address for capes, parsing the EEPROM
info and matching them to specific cape drivers.
On top of that, a
Capebus is created to address the problem of many SoCs that can provide a
multitude of hardware interfaces but in order to keep costs down the main
boards only support a limited number of them. The rest are typically brought
out to pin connectors on to which other boards, named capes are connected
The MFD parent device now uses a regmap, instead of direct
memory access. Use the same method in the sub devices to avoid
nasty surprises.
Please not that this driver can't really deal with the case of the regmap
call failing in anyway. So that's why there's no error handling.
I think it's best t
It's common not for both the touchscreen & adc to be activated
at the same time. Deal with this case.
Signed-off-by: Pantelis Antoniou
---
drivers/mfd/ti_am335x_tscadc.c | 34 +++---
include/linux/mfd/ti_am335x_tscadc.h | 8 +++-
2 files changed, 26 inserti
Add an IIO map interface that consumers can use.
Signed-off-by: Pantelis Antoniou
---
drivers/iio/adc/ti_am335x_adc.c | 60 +
1 file changed, 49 insertions(+), 11 deletions(-)
diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
omap_device is going private.
Move the da8xx-dt adapter device to arch/arm/mach-omap2.
Signed-off-by: Pantelis Antoniou
---
arch/arm/mach-omap2/Makefile | 3 +
arch/arm/mach-omap2/da8xx-dt.c | 197 +
2 files changed, 200 insertions(+)
create mode 100
Marking omap_device_build && omap_device_build_ss as __init is
really bad when you want to instantiate a device later in the
boot sequence, or from a module.
Removing them makes the crashes go away.
Signed-off-by: Pantelis Antoniou
---
arch/arm/plat-omap/omap_device.c | 4 ++--
1 file changed,
omap_device is going private.
Move the ti-tscadc-dt adapter device to arch/arm/mach-omap2.
Signed-off-by: Pantelis Antoniou
---
arch/arm/mach-omap2/Makefile | 1 +
arch/arm/mach-omap2/ti-tscadc-dt.c | 155 +
2 files changed, 156 insertions(+)
create
It is painless to move the adapter DT devices to arch/arm/mach-omap2
However I got bit by the __init at omap_build_device family functions.
If you don't remove it, crashes every time you instantiate a device
at runtime, or you load the cape driver as a module.
Pantelis Antoniou (3):
omap-device
Hi,
On 10/29/2012 09:21 AM, Vaibhav Hiremath wrote:
> From: Mugunthan V N
>
> Add CPSW and MDIO related device tree data for AM33XX.
> Also enable them into board/evm dts files by providing
> respective phy-id.
Is there any bindings documentation for that device?
> Signed-off-by: Mugunthan V N
On 21:12 Sun 28 Oct , Linus Walleij wrote:
> On Wed, Oct 24, 2012 at 7:28 PM, Dmitry Torokhov
> wrote:
>
> >> drivers/spi/spi-pl022.c
> >
> > Default/sleep transitions could be moved into bus code.
>
> No that's not a good idea as long as we have both the platform bus
> and the AMBA bus doin
Hi Felipe,
On Wed, Oct 31, 2012 at 7:08 PM, Felipe Balbi wrote:
> Hi,
> On Tue, Oct 16, 2012 at 02:15:56PM +0530, Vivek Gautam wrote:
>> This patch adds support to parse probe data for
>> dwc3-exynos driver using device tree.
>>
>> Signed-off-by: Vivek Gautam
>
> does not apply to my dwc3 branch
Hi Balbi,
On Thursday 27 September 2012 11:15 AM, Afzal Mohammed wrote:
This series is made over over Balbi's usb "master" branch.
It applies cleanly over "musb" branch too.
Please ignore this series, a new series has been posted,
"usb: musb: dsps: fixes for -rc".
Regards
Afzal
--
To unsubs
OMAP3 Beagle-XM board specific data for usb2 host device tree node
is included.
In Beagle XM board , the port 2 of usb host is connected to a hub
with ethernet interface.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 32
1 file ch
The port2 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb2) port 2 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/oma
Since TLL channels clocks are dummy(virtual) nodes for OMAP3.
The device names for these clocks are set to NULL.
Signed-off-by: Keshava Munegowda
---
arch/arm/mach-omap2/clock3xxx_data.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/clock3xxx_da
The USB2 Host driver of OMAP3/OMAP4 are device tree complaiant with
this patch series.
The device tree data of UHH, EHCI, OHCI and TLL are included.
The drivers are updated to extract and use the register set and
interrupt numbers delivered by these device tree structures.
Keshava Munegowda (11):
The device tree node details of usb2 host and tll components
are included for OMAP3
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap3.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 69
The USB TLL device node is extracted and used in the probe
of the driver to initialize the driver data.
This TLL driver exports an API to usbhs driver to perform
the port configuration. The usb2 hs driver invoke the same
API in its driver probe to initialize the ports.
Signed-off-by: Keshava Muneg
The USB2 Host device node is extracted and used in the probe
of the driver to initialize the usb ports and controller. The
platform specific initialization is also performed.
Signed-off-by: Keshava Munegowda
---
arch/arm/mach-omap2/usb-host.c |2 -
drivers/mfd/omap-usb-host.c
The usbhs core driver data is used by the ehci driver, because
the ehci driver is child of usbhs core. The unused ehci, ohci
and tll specific structures are removed.
platform device creation of usbhs and tll using hwmod is
removed.
Signed-off-by: Keshava Munegowda
---
arch/arm/mach-omap2/usb-hos
OMAP4 panda board specific device tree node is included.
In OMAP4 panda board, the port 1 is used in ULPI PHY mode.
The port 1 is connected to a on board hub with ethernet
interface.
TODO:
The clock bindings are not yet avilable for OMAP4.
hence , USB hub specific clocks are exported as dev
The port1 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb1) port 1 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap4-panda.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda.d
The tll ports clock names are renamed as channel clocks.
This is change is just adhere to TRM words
Signed-off-by: Keshava Munegowda
---
drivers/mfd/omap-usb-tll.c | 46 ++--
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/drivers/mfd/oma
The device tree node details of usb2 host and tll components
are included for OMAP4 SOC
Signed-off-by: Keshava Munegowda
---
.../devicetree/bindings/usb/omap-usb-host.txt | 24
.../devicetree/bindings/usb/omap-usb-tll.txt | 21 +
arch/arm/boot/
DT bindings normally use '-' (hyphens) instead of '_' (underscore),
driver has it the proper way, but binding documentation does not
reflect it, fix it.
Signed-off-by: Afzal Mohammed
---
Documentation/devicetree/bindings/usb/am33xx-usb.txt | 8
1 file changed, 4 insertions(+), 4 deletio
On 31/10/12 13:57, Hiremath, Vaibhav wrote:
> On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
>>
>> If I try the latest mainline U-Boot (or the TI branch), I just get to
>> "Starting kernel ..." and then
>> hangs.
>>
>
>
> I am using Mainline u-boot and it works for me. Can you paste u-boo
This reverts commit d8c3ef256f88b7c6ecd673d03073b5645be9c5e4.
Above mentioned change was made along with multi usb phy change and
adding DT support for nop transceiver. But other two changes did not
make it to mainline. This in effect makes dsps musb wrapper unusable
even for single instance.
Hen
Hi Balbi,
This series contains a couple of fixes for musb dsps wrapper.
First one restores capability to support at least one instance of musb.
Without it, even a single instance can't be supported as change which
is reverted by it was made along with multi phy changes and nop
transciever dt supp
On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
> On 30/10/12 14:48, Vaibhav Hiremath wrote:
> >
> >
> > On 10/30/2012 6:09 PM, Hiremath, Vaibhav wrote:
> >>
> >> Mark,
> >>
> >> MMC is dependent on EDMA-DMA conversion patches from Matt, which he has
> >> already submitted to the list rece
On Sat, Oct 27, 2012 at 07:05:54PM +0530, Kishon Vijay Abraham I wrote:
> ocp2scp was not having pdata support which makes *musb* fail for non-dt
> boot in OMAP platform. The pdata will have information about the devices
> that is connected to ocp2scp. ocp2scp driver will now make use of this
> inf
Hi,
On Tue, Oct 16, 2012 at 02:15:56PM +0530, Vivek Gautam wrote:
> This patch adds support to parse probe data for
> dwc3-exynos driver using device tree.
>
> Signed-off-by: Vivek Gautam
does not apply to my dwc3 branch. Care to respin ?
--
balbi
signature.asc
Description: Digital signature
Hi,
On Wed, Oct 31, 2012 at 05:46:38PM +0530, Keshava Munegowda wrote:
> The USB2 Host driver of OMAP3/OMAP4 are device tree complaiant with
> this patch series.
> The device tree data of UHH, EHCI, OHCI and TLL are included.
> The drivers are updated to extract and use the register set and
> inte
On 30/10/12 14:48, Vaibhav Hiremath wrote:
>
>
> On 10/30/2012 6:09 PM, Hiremath, Vaibhav wrote:
>>
>> Mark,
>>
>> MMC is dependent on EDMA-DMA conversion patches from Matt, which he has
>> already submitted to the list recently. So MMC support will come along with
>> EDMA support. DMA-EDMA patc
Hi,
On Wed, Oct 31, 2012 at 05:27:36PM +0530, Hebbar, Gururaja wrote:
> HSMMC IP on AM33xx need a special setting to handle High-speed cards.
> Other platforms like TI81xx, OMAP4 may need this as-well. This depends
> on the HSMMC IP timing closure done for the high speed cards.
>
> From AM335x TR
The port2 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb2) port 2 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/oma
The port1 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb1) port 1 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap4-panda.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda.d
The usbhs core driver data is used by the ehci driver, because
the ehci driver is child of usbhs core. The unused ehci, ohci
and tll specific structures are removed.
platform device creation of usbhs and tll using hwmod is
removed.
Signed-off-by: Keshava Munegowda
---
arch/arm/mach-omap2/usb-hos
The USB2 Host device node is extracted and used in the probe
of the driver to initialize the usb ports and controller. The
platform specific initialization is also performed.
Signed-off-by: Keshava Munegowda
---
arch/arm/mach-omap2/usb-host.c |2 -
drivers/mfd/omap-usb-host.c
The USB TLL device node is extracted and used in the probe
of the driver to initialize the driver data.
This TLL driver exports an API to usbhs driver to perform
the port configuration. The usb2 hs driver invoke the same
API in its driver probe to initialize the ports.
Signed-off-by: Keshava Muneg
1 - 100 of 151 matches
Mail list logo
