On Sun, 2011-08-21 at 00:03 -0600, Paul Walmsley wrote:
On Thu, 18 Aug 2011, Tomi Valkeinen wrote:
Did you get a chance to look at this series? These fixes will allow us
to remove the temporary hacks from the DSS driver.
These have been queued for the 3.1-rc fixes series. Thanks for the
Hi Paul,
On Sat, 2011-08-20 at 00:26 -0600, Paul Walmsley wrote:
On Fri, 19 Aug 2011, Paul Walmsley wrote:
This one doesn't build when !CONFIG_OMAP2_DSS - the following is the
updated patch.
Looks like my previous update missed a warning. This also moves the
omap_dss_reset()
On Friday 19 August 2011 15:04:20 Tony Lindgren wrote:
It seems OK to me.
Thanks!
But for the -rc cycle it has potential for
fixes for features that never worked flame bait. If you guys
are OK to deal with that then go ahead.
Hrm, I have not thought about this. Not sure, if we want to go
On 22/08/11 08:13, Ujfalusi, Peter wrote:
On Friday 19 August 2011 15:04:20 Tony Lindgren wrote:
It seems OK to me.
Thanks!
But for the -rc cycle it has potential for
fixes for features that never worked flame bait. If you guys
are OK to deal with that then go ahead.
Hrm, I have not
After the patch-set [PATCHv2 0/5] OMAP DSS HWMOD fixes we can revert the DSS
hacks added to circumvent broken HWMOD data, and clean up unneeded clock
handling.
Tomi
Tomi Valkeinen (3):
Revert HACK: OMAP: DSS2: clk hack for OMAP2/3
Revert OMAP: DSS2: HDMI: fix hdmi clock name
OMAP: DSS2:
This reverts commit 9ede365aa6f74428a1f69c21ca1cf21213167576.
The hack is no longer needed, as the HWMOD data has been fixed.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dsi.c |5 +
drivers/video/omap2/dss/dss.c |5 -
This reverts commit df5d3ed23cf73ee0763a8963003bda9b69d9620f.
The HDMI clock name has been fixed in HWMOD data.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/hdmi.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Now that the HWMOD fmwk handles the fcks of DSS modules properly, the
DSS driver no longer needs to explicitely enable/disable the fck.
This patch removes the enables/disables of fck from dispc, dsi and dss.
The clk_get(fck) is still needed there, as the modules need to know the
frequency of the
These patches add support for the second DSI module on OMAP4 by fixing the DSI
device naming and adding necessary powers. Also DSI pad muxing is improved to
support OMAP4.
Tomi
Tomi Valkeinen (4):
OMAP: DSS2: Change DSI device naming
OMAP4: TWL: Add common omapdss supplies
OMAP: DSS2:
Currently, there are 2 differently named platform devices generated for
the 2 DSS DSI modules. In order to use the same driver, the dsi devices
should be 2 instances of the same platform device.
Change the platform device names from omapdss_dsi1 and omapdss_dsi2
to omapdss_dsi, and set the device
OMAP DSS normally gets power from VCXIO on OMAP4. Add configuration for
this into twl-common.c
Mark VCXIO as always_on, as VCXIO is used by multiple components,
including the MPU, and turning it off when DSS doesn't need it would
lead the device to halt.
Signed-off-by: Tomi Valkeinen
dsi_mux_pads() needs to know about the DSI HW module and the DSI lanes
used. Split the function into two, enable and disable, which take
necessary arguments, and add empty implementations for both.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/display.c | 14
Implement dsi_mux_pads for OMAP4. On enable the function enables the DSI
pins and disables pull down. On disable the function disables the pins
and enables pull down.
It is unclear from the TRM whether the pull down is active if the pins
are disabled, so this implementation may leave the pins
Some minor fixes for DSS.
Tomi
Tomi Valkeinen (4):
OMAP: OMAPFB: make omapfb start even when a display is missing a
driver
OMAP: DSS2: fix clock sources on error and uninit
OMAP: DSS2: Handle manager change in apply
OMAP: DSS2: Remove EXPERIMENTAL from Kconfig
DPI and DSI were not cleaning up the clock source in error or uninit
cases. Set the clock source back to PRCM.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dpi.c |4 +++-
drivers/video/omap2/dss/dsi.c |3 +++
2 files changed, 6 insertions(+), 1
Currently omapfb wants that all the display devices have a driver,
otherwise omapfb refuses to start. There's no real requirement to act
like that, and this patch will make omapfb give a warning and skip that
device.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
Currently when changing the manager of an overlay, set_manager() directly
calls dispc to set the overlay's destination.
Change this to be more in line with other overlay configurations, and
this will also remove the need to have dispc clocks enabled when calling
set_manager().
A new field is
On Saturday, August 20, 2011 04:40:09 AM Ming Lei wrote:
Hi,
2011/8/20 Thomas Renninger tr...@suse.de:
On Friday, August 19, 2011 05:04:04 PM tom.leim...@gmail.com wrote:
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
trace point, based
Cleanups for DSS driver, no functionality changed.
Tomi
Tomi Valkeinen (10):
OMAP: DSS2: Remove support for non-DISPC overlays
OMAP: DSS2: DISPC: use lookup tables for bit shifts
OMAP: DSS2: Add overlay caps to DSS features
OMAP: DSS2: Add GLOBAL_ALPHA PRE_MULT_ALPHA to ovl caps
DSS driver has not been experimental for many years now, so perhaps
it's time to remove the text from Kconfig titles.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/Kconfig|2 +-
drivers/video/omap2/omapfb/Kconfig |2 +-
2 files changed, 2
Remove support for non-DISPC overlays and overlay managers.
The support to possibly have non-DISPC overlays and managers was made to
make it possible to use CPU and/or sDMA to update RFBI or DSI command
mode displays. It is ok to remove the support, because:
- No one has used the feature.
-
Use lookup tables instead of switch/if in some DISPC functions to make
the code cleaner.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Acked-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/dispc.c | 204 ++-
1 files changed, 50
Add support to define overlay capabilities into dss_features. The
features are set to overlay-caps at initialization time.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Acked-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/dss_features.c | 55
Use strtobool and kstrto* functions when parsing sysfs inputs.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/display.c | 21 +
drivers/video/omap2/dss/manager.c | 37 +++--
drivers/video/omap2/dss/overlay.c
Add OMAP_DSS_OVL_CAP_GLOBAL_ALPHA and OMAP_DSS_OVL_CAP_PRE_MULT_ALPHA to
overlay capabilities. Use these instead of FEAT_GLOBAL_ALPHA,
FEAT_GLOBAL_ALPHA_VID1 and FEAT_PRE_MULT_ALPHA in code.
Remove FEAT_GLOBAL_ALPHA_VID1 and FEAT_PRE_MULT_ALPHA which are no
longer used. FEAT_GLOBAL_ALPHA is still
Use strtobool instead of kstrtoint when parsing bool from sysfs.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/omapfb/omapfb-sysfs.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/video/omap2/omapfb/omapfb-sysfs.c
The functions do not exist, so remove the prototypes.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dss.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/video/omap2/dss/dss.h b/drivers/video/omap2/dss/dss.h
index
Rename dispc's overlay related functions as follows:
- Remove prepending underscores, which were originally used to inform
that the clocks needs to be enabled. This meaning is no longer valid.
- Prepend the functions with dispc_ovl_*
- Remove plane from the name, e.g. dispc_set_plane_ba0 -
Group dispc's overlay and manager related functions.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dss.h | 47 +++-
1 files changed, 22 insertions(+), 25 deletions(-)
diff --git a/drivers/video/omap2/dss/dss.h
Rename dispc's manager related functions as follows:
- Remove prepending underscores, which were originally used to inform
that the clocks needs to be enabled. This meaning is no longer valid.
- Prepend the functions with dispc_mgr_*
- Remove channel from the name, e.g. dispc_enable_channel -
On Mon, 2011-08-22 at 11:27 +0300, Tomi Valkeinen wrote:
Cleanups for DSS driver, no functionality changed.
Tomi
Tomi Valkeinen (10):
OMAP: DSS2: Remove support for non-DISPC overlays
OMAP: DSS2: DISPC: use lookup tables for bit shifts
OMAP: DSS2: Add overlay caps to DSS features
Hi Tony,
Thanks for the reply.
On 08/10/2011 12:33 PM, Tony Lindgren wrote:
* Michael Jones michael.jo...@matrix-vision.de [110810 03:14]:
I would like to submit some patches to add support for a new OMAP board...
Is there a right or wrong time to post such patches to this list? How
does
Hi,
On Mon, Aug 22, 2011 at 09:59:46AM +0530, J, KEERTHY wrote:
+static const struct dev_pm_ops omap_temp_sensor_dev_pm_ops = {
+ .suspend = omap_temp_sensor_suspend,
+ .resume = omap_temp_sensor_resume,
+ .runtime_suspend = omap_temp_sensor_runtime_suspend,
+
Moi Tomi,
Have you ever encounter this error.
Looking some pointer what can cause checksum error.
Regards,
Sudipta
On 18 August 2011 17:35, Sudipta GHOSH sudipta...@gmail.com wrote:
Hi,
Working DSS Panel driver.
Sometime I am getting checksum error from DSI when framebuffers are
sent to
Hi,
Most likely it is caused by electrical interference with the transfer.
Or, while very unlikely if it happens only rarely, a HW bug in the panel
(or even in OMAP).
Tomi
On Mon, 2011-08-22 at 13:05 +0300, Sudipta GHOSH wrote:
Moi Tomi,
Have you ever encounter this error.
Looking some
On Mon, 2011-08-22 at 11:27 +0300, Tomi Valkeinen wrote:
Use strtobool and kstrto* functions when parsing sysfs inputs.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/display.c | 21 +
drivers/video/omap2/dss/manager.c | 37
Hi Kyle,
On Thu, Aug 11, 2011 at 10:33:11PM -0500, Kyle Manna wrote:
These patches add basic functionality to the twl4030-madc driver to make
it work on the BeagleBoard xM.
Version 2 adds fixes per Grazvydas Ignotas and the check for NULL pointer
patch.
Kyle Manna (4):
mfd:
From: Julia Lawall ju...@diku.dk
Test the just-initialized value rather than some other one.
The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
// smpl
@r@
identifier x,y,f!={PTR_ERR,ERR_PTR,ERR_CAST};
statement S;
@@
x = f(...);
(
if (\(x ==
Hi Anand,
On Thu, Aug 18, 2011 at 04:14:31PM +0530, Anand Gadiyar wrote:
This code section seems to have been accidentally copy pasted.
It causes incorrect bits to be set up in the TLL_CHANNEL_CONF
register and prevents the TLL mode from working correctly.
Patch applied, with Felipe's ACK and
Hi Felipe,
On Fri, Aug 19, 2011 at 12:36:15AM +0300, Felipe Balbi wrote:
Hi,
On Sat, Jul 09, 2011 at 05:09:00AM +0100, Mark Brown wrote:
On Thu, Jun 30, 2011 at 12:51:03PM +0300, Felipe Balbi wrote:
the following patches where boot-tested on beagle xM
and everything seems fine. MMC
Hi Tom,
On Fri, Aug 19, 2011 at 04:57:54PM +0800, tom.leim...@gmail.com wrote:
From: Ming Lei tom.leim...@gmail.com
The patch fixes the build failure:
Patch applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send
Hi Anhilash,
On Fri, Aug 19, 2011 at 05:19:33PM +0530, Abhilash K V wrote:
The current implementation almost assumes that only
TWL4030/TWL5030/TWl6030 are (or can be) used with the
OMAP processors. This is, however, not true.
I don't like the mfd/Kconfig change. Why would those drivers be
Hi Kevin,
Here are a couple of cleanups on top of your for_3.2/omap_device series
rebased on top of 3.1-rc2 to get your pm-fixes.
The goal is to help building core devices using device-tree by removing
direct reference to the device inside PM.
For that, I took and rebased the two patches done by
From: Nishanth Menon n...@ti.com
An API which translates a standard hwmod name to corresponding
omap_device is useful for drivers when they need to look up the
device associated with a hwmod name to map back into the device
structure pointers. These ideally should be used by drivers in
mach
Replace the struct device parameter of omap2_set_init_voltage
by the hwmod name. It will avoid having to store explicitely
the device pointer into a static variable.
Moreover, it will be a little bit more scalable if we introduce
new DVFS devices.
Signed-off-by: Benoit Cousson b-cous...@ti.com
From: Nishanth Menon n...@ti.com
Provide a quick set of access functions:
a) Convert omap_device to platform_device - This is the flip of
to_omap_device for equivalent usage
b) Convert omap_device to device pointer - This is useful for
most devices that need to go through standard linux
Since the device pointer is now retrieved using the hwmod name, remove
the static variables used to store the device pointers for DSP, MPU, IVA
and L3 devices for PM/DVFS usage.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/pm.c | 47
Replace the multiple omap2_get_XXX_device APIs with the new
omap_hwmod_name_get_dev that uses the hwmod name to get the proper
device.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c |4 ++--
1 files changed, 2
Most devices are using the same default omap_device_pm_latency structure
during device built. In order to avoid the duplication of the same
structure everywhere, add a default structure that will be used if
the device does not have an explicit one.
Next patches will clean the duplicated
Remove all these duplicated structures since a default one is now
available.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/devices.c| 46 +++--
arch/arm/mach-omap2/display.c| 11 +
From: Samuel Ortiz [sa...@linux.intel.com]
Sent: Monday, August 22, 2011 8:33 PM
To: Koyamangalath, Abhilash
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
linux-ker...@vger.kernel.org;
t...@atomide.com; li...@arm.linux.org.uk; Hilman, Kevin; Shilimkar, Santosh;
Op 22 aug. 2011, om 08:42 heeft javier Martin het volgende geschreven:
Hi Koen,
On 19 August 2011 17:07, Koen Kooi k...@beagleboard.org wrote:
Op 19 aug. 2011 om 14:39 heeft javier Martin
javier.mar...@vista-silicon.com het volgende geschreven:
Hi,
I've been digging into the
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
High level implementation:
1. Preparation of the PM QoS for the addition of a device PM QoS constraints
framework:
. rename and move of the PM QoS implementation files to kernel/power/qos.c
and
Hi,
On Mon, Aug 22, 2011 at 04:54:36PM +0200, Samuel Ortiz wrote:
On Fri, Aug 19, 2011 at 12:36:15AM +0300, Felipe Balbi wrote:
Hi,
On Sat, Jul 09, 2011 at 05:09:00AM +0100, Mark Brown wrote:
On Thu, Jun 30, 2011 at 12:51:03PM +0300, Felipe Balbi wrote:
the following patches
Hi Kevin,
This is an initial attempt to use a notifier in order to create an
omap_device from a platform_device bound to DT node as suggested by Grant.
For the moment, the informations are all extracted from the hwmod data.
The idea is to focus first on the devices / board static init removal.
Hi Kevin,
This is an initial attempt to use a notifier in order to create an
omap_device from a platform_device bound to DT node as suggested by Grant.
For the moment, the informations are all extracted from the hwmod data.
The idea is to focus first on the devices / board static init removal.
Add two helpers function to parse a property that contains multiple
strings.
These functions might be exported and moved to a common place if they
can to be useful elsewhere.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/omap_device.c |
Split the omap_device_build_ss into two smaller functions
that will allow to populate a platform_device already alocated by
device-tree.
The functionality of the omap_device_build_ss is still the same, but
the omap_device_alloc will be usable with devices already built by
device-tree.
Add a notifier called during device_add phase. If a of_node is present,
retrieve the hwmod entry in order to populate propely the omap_device
structure.
For the moment the resource from the device-tree are overloaded.
DT does not support named resource yet, and thus, most driver
will not work
On Monday, August 22, 2011, Kevin Hilman wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
High level implementation:
1. Preparation of the PM QoS for the addition of a device PM QoS constraints
framework:
. rename and move of the PM QoS implementation
Hello Tomi,
On Mon, 22 Aug 2011, Tomi Valkeinen wrote:
On Sat, 2011-08-20 at 00:26 -0600, Paul Walmsley wrote:
On Fri, 19 Aug 2011, Paul Walmsley wrote:
This one doesn't build when !CONFIG_OMAP2_DSS - the following is the
updated patch.
Looks like my previous update missed a
The oscillator that supplies GPT12_FCLK and WDT1_FCLK exists in the
WKUP powerdomain[1]. This resolves at least one boot-time warning:
omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
1. _OMAP34xx Multimedia High Security (HS) Device Silicon Revision 3.1.x
Security Addendum Version
Liam Girdwood l...@ti.com writes:
On 05/08/11 20:33, Hilman, Kevin wrote:
Mark Brown broo...@opensource.wolfsonmicro.com writes:
On Thu, Jul 28, 2011 at 02:48:57PM +0300, Tero Kristo wrote:
OMAP SMPS regulator driver provides access to OMAP voltage processor
controlled regulators. These
Koyamangalath, Abhilash abhilash...@ti.com writes:
Kevin Hilman wrote:
Abhilash K V abhilash...@ti.com writes:
From: Vaibhav Hiremath hvaib...@ti.com
In case of AM3517 AM3505, Smart Reflex is not applicable so
we must not enable it. So add check for am3517/05 cpu revision
in
On Thu, 18 Aug 2011, Pantelis Antoniou wrote:
Let me report that with this change Beagle board fails to boot,
hangs right on rootfs mount.
Confirmed here.
Commit f3637a5f2e2eb391ff5757bc83fb5de8f9726464 (irq: Always set
IRQF_ONESHOT if no primary handler is specified), merged as part of
On Fri, 19 Aug 2011, Felipe Balbi wrote:
On Thu, Aug 18, 2011 at 07:22:39PM +0200, Sebastian Andrzej Siewior wrote:
Pantelis Antoniou wrote:
Let me report that with this change Beagle board fails to boot,
hangs right on rootfs mount.
Can you provide some more information about the
Rajendra Nayak rna...@ti.com writes:
[...]
FWIK, its a one time requirement to set the clock rate to the
right rate the device can operate in based on what a platform
supports.
Except $SUBJECT patch hard-codes the clock rate for all platforms in the
driver.
If the clock rate is to be
On 8/23/2011 5:28 AM, Kevin Hilman wrote:
Rajendra Nayakrna...@ti.com writes:
[...]
FWIK, its a one time requirement to set the clock rate to the
right rate the device can operate in based on what a platform
supports.
Except $SUBJECT patch hard-codes the clock rate for all platforms in the
Patch series reworked from:
http://permalink.gmane.org/gmane.linux.ports.arm.omap/61674
Also added support for i2c1 controller on omap4 based panda
board.
Baseline:
=
git://git.secretlab.ca/git/linux-2.6.git
Branch: devicetree/test
The above branch is rebased with v3.1-rc2 mainline.
+
The omap_device requires new omap_device api to be added in order
to support omap dt.
The new api is added and new parameter device node pointer np is added
to existing api. The users of omap_device api is changed accordingly.
Build and boot tested on omap3 beagle for both dt and not dt build.
Add pd_size in the AUXDATA structure so that omap HWMOD which require
platform_data size can pass along with AUXDATA.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/of/platform.c |2 ++
include/linux/of_platform.h |5 +
2 files changed, 7 insertions(+), 0
Add omap3 soc file for handling omap3 soc i2c controllers existing
on l4-core bus.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 62 ++
1 files changed, 62 insertions(+), 0 deletions(-)
create mode 100644
Update omap3 beagle dts file with required clock frequencies for the i2c
client devices existing on beagle board.
Beagle custom board dts file is cleaned up so that it can coexist with omap3
soc dts file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
The generic board file is created and derived from beagle board file.
The beagle board file is migrated to boot from flattened device tree and
the cleanup of board specific file will happen in different stages.
The changes here focus on minimal configuration to boot beagle board with
dt enabled
Add omap-device to the i2c controllers compatible property.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3.dtsi |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index
The omap devices will use HWMOD for fetching device information
hence it needs to be handled seperately during platform bus
creation during dt build.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/of/platform.c | 41 -
1 files changed,
The device tree support has been added to i2c1 controller and
corresponding i2c initilization in generic board file is cleaned
up so that platfom device is registered through dt and omap device
and not through board i2c initilization.
These changes will not affect non dt builds and existing
Add omap4 soc dts file for handling omap4 soc i2c
controllers existing on l4-core bus.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts |7 +---
arch/arm/boot/dts/omap4.dtsi | 68 +
2 files changed, 69
Update omap4 panda dts file with required clock frequencies
for the i2c client devices existing on panda board.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git
The generic board file is created and derived from omap4 panda board file.
The changes here focus on minimal configuration to boot panda board with
dt enabled which provides basic platform for converting device drivers for
using dt.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
Enable dt support for omap4 i2c1 controller and cleanup
legacy i2c device registration in omap4 generic board file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap4-dt.c | 21 +++--
1 files changed, 15 insertions(+), 6 deletions(-)
diff
Add documentation for using omap i2c controller with device
tree support enabled.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
Documentation/devicetree/bindings/i2c/omap-i2c.txt | 57
1 files changed, 57 insertions(+), 0 deletions(-)
create mode 100644
Convert the omap-serial hardirq handler to a threaded IRQ handler. Without
this patch, OMAP boards which use the on-board OMAP UARTs and the
omap-serial driver will not boot to userspace after commit
f3637a5f2e2eb391ff5757bc83fb5de8f9726464 (irq: Always set IRQF_ONESHOT if
no primary handler
The oscillator that supplies GPT12_FCLK and WDT1_FCLK exists in the
WKUP powerdomain[1]. This resolves at least one boot-time warning:
omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
1. _OMAP34xx Multimedia High Security (HS) Device Silicon Revision 3.1.x
Security Addendum Version
Hi Tony,
The following changes since commit fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c:
Linux 3.1-rc3 (2011-08-22 11:42:53 -0700)
are available in the git repository at:
git://git.pwsan.com/linux-2.6 prcm-fixes-a-3.1rc
Note that for these changes to boot successfully on 3.1-rc3, the
85 matches
Mail list logo
