OMAP4 has two different Devices IVA and DSP. DSP is bound
with IVA for DVFS. The registration of IVA dev in API
'omap2_init_processor_devices' was missing. Init dev for
'iva_dev' is added.
This also fixes the following error seen during boot as
omap2_set_init_voltage can now find the iva device
On Fri, Mar 11, 2011 at 06:29:06PM -0600, Omar Ramirez Luna wrote:
Hi Greg,
Please consider to apply this patch in the staging tree, as the
description says it fixes a crash in tidspbridge driver, this bug
was already present but it seems to have surfaced by recent tests
made by Felipe and
Vasiliy Kulikov (20):
mach-ux500: mbox-db5500: world-writable sysfs fifo file
leds: lp5521: world-writable sysfs engine* files
leds: lp5523: world-writable engine* sysfs files
misc: ep93xx_pwm: world-writable sysfs files
rtc: rtc-ds1511: world-writable sysfs nvram file
scsi: aic94xx:
The following series uses the
- proposed platform support for async platform data
http://marc.info/?l=linux-kernelm=129996915023642w=2
- proposed usb core and usbnet use of async platform data
http://marc.info/?l=linux-kernelm=129996960824035w=2
in order to configure onboard USB -
This is part of an RFC patch series introducing asynchronous platform
data, which may be attached to discovered bus devices at probe time
based on the device path.
As part of the series, platform_data is enabled in usbnet layer.
This patch defines the usbnet platform data, allowing the panda
Introduce a generic helper function that can set a MAC address using
data from the OMAP unqiue CPU ID register.
Signed-off-by: Andy Green andy.gr...@linaro.org
---
arch/arm/mach-omap2/id.c | 13 +
arch/arm/mach-omap2/include/mach/id.h |1 +
2 files changed, 14
This adapts the register offsets used to read the CPU DIE ID registers
when run on 44XX so they match what is in the OMAP4430 Reference Manual
page 269
Signed-off-by: Andy Green andy.gr...@linaro.org
---
arch/arm/mach-omap2/id.c | 13 +
1 files changed, 13 insertions(+), 0
This is part of an RFC patch series introducing asynchronous platform
data, which may be attached to discovered bus devices at probe time
based on the device path.
As part of the series, platform_data is enabled in usbnet layer.
This patch used the usbnet platform data in the panda board
This is part of an RFC patch series introducing asynchronous platform
data, which may be attached to discovered bus devices at probe time
based on the device path.
As part of the series, platform_data is enabled in usbnet layer.
This patch allows smsc95xx usbnet driver to understand that the MAC
On Sat, Mar 12, 2011 at 7:36 PM, Greg KH g...@kroah.com wrote:
On Fri, Mar 11, 2011 at 06:29:06PM -0600, Omar Ramirez Luna wrote:
Please consider to apply this patch in the staging tree, as the
description says it fixes a crash in tidspbridge driver, this bug
was already present but it seems
On Sat, Mar 12, 2011 at 10:50:39PM +, Andy Green wrote:
This is part of an RFC patch series introducing asynchronous platform
data, which may be attached to discovered bus devices at probe time
based on the device path.
As part of the series, platform_data is enabled in usbnet layer.
On Sun, Mar 13, 2011 at 01:42:35AM +0200, Felipe Contreras wrote:
On Sat, Mar 12, 2011 at 7:36 PM, Greg KH g...@kroah.com wrote:
On Fri, Mar 11, 2011 at 06:29:06PM -0600, Omar Ramirez Luna wrote:
Please consider to apply this patch in the staging tree, as the
description says it fixes a
pm44xx.c is built only when CONFIG_PM is setup,
remove redundant CONFIG_PM check.
This also fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=25022
Reported-by: Martin Etti ettl.mar...@gmx.de
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/pm44xx.c |2 --
1 files
13 matches
Mail list logo
