On Tue, 2011-12-13 at 11:26 +0530, mythr...@ti.com wrote:
From: Mythri P K mythr...@ti.com
Disables the internal pull resistor for SDA and SCL which are enabled by
default, as there are expernal pull up's in 4460 and 4430 ES2.3
Typo above with external.
SDP, Blaze and Panda Boards, It is
Hi Benoit,
diff --git a/arch/arm/mach-omap2/common.h b/arch/arm/mach-omap2/common.h
index 012bac7..bcfccc2 100644
--- a/arch/arm/mach-omap2/common.h
+++ b/arch/arm/mach-omap2/common.h
@@ -156,6 +156,16 @@ void omap3_intc_resume_idle(void);
void omap2_intc_handle_irq(struct pt_regs *regs);
Hi,
On Thursday 08 December 2011 01:59 PM, Tomi Valkeinen wrote:
On Wed, 2011-12-07 at 18:35 +0530, Archit Taneja wrote:
Hi,
On Tuesday 22 November 2011 02:52 PM, Tomi Valkeinen wrote:
Add checks for overlay and manager settings. The checks are a bit
complex, as we need to observe the bigger
This series adds DT support for TWL regulator driver and
passes regulator data for two OMAP4 boards (OMAP4 panda and
OMAP4 sdp) from device tree.
Patches are based on for-next of the regulator tree[1] with
omap i2c/twl DT adaptation patches[2] from Benoit pulled in
and are available here:
Pass the adjustable voltage regulator information for
omap4sdp board from device tree.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 36
1 files changed, 36 insertions(+), 0 deletions(-)
diff --git
Pass the adjustable voltage regulator information for
omap4panda board from device tree.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 24
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Also add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
Under some error conditions the i2c driver may do a reset.
Adding a reset field and support in the device-specific code to aid
error-recovery.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
arch/arm/plat-omap/i2c.c |2 ++
include/linux/i2c-omap.h |1 +
2 files changed, 3
Add a function omap_device_reset() to reset all the hwmods in the hwmod
device.
This is intended to be used by device drivers to reset all the hwmods in the
device. This is needed to support some ips like i2c which may have to do
reset
in error paths or in errata.
The series attempts to do the following
- The reset should not be done in the driver
have support for the same.
- Remove the sysc register access in the driver.
Incorporated review comments:
- Fix the indentation of the code.
- Restore in the error path is not needed as we are
doing a
For I2C clockactivity field is added for OMAP3 and OMAP4 that defines how the
interface (OCP) and functional (system) clocks behave when the I2C module is
idle.
The configuration of the clock activity bit field (per TRM) is as follows:
0x0: Both clocks can be cut off
0x1: Only OCP clock must be
- The reset in the driver at init is not needed anymore as the
hwmod framework takes care of reseting it.
- Reset is removed from omap_i2c_init, which was called
not only during probe, but also after time out and error handling.
device_reset were added in those places to effect the
The SYSC register should not accessed in the driver removing the
define from the driver.
Also clean up the syscstate from the omap_i2c_dev struct.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |5 -
On Tue, 2011-12-13 at 15:32 +0530, Archit Taneja wrote:
Hi,
On Thursday 08 December 2011 01:59 PM, Tomi Valkeinen wrote:
On Wed, 2011-12-07 at 18:35 +0530, Archit Taneja wrote:
Hi,
On Tuesday 22 November 2011 02:52 PM, Tomi Valkeinen wrote:
Add checks for overlay and manager
On Mon, 2011-12-12 at 11:47 +0530, Archit Taneja wrote:
These are some minor fixes for DSS2.
Based on Tomi's master branch in:
git://gitorious.org/linux-omap-dss2/linux.git
Archit Taneja (3):
OMAPDSS: DSI: Fix HSDIV related PLL info in dsi_dump_clocks()
OMAPDSS: Panel NEC: Set
Hi Tony/kevin,
On Fri, Nov 11, 2011 at 3:27 PM, Govindraj.R govindraj.r...@ti.com wrote:
Converting uart driver to adapt to pm runtime API's.
Code re-org + cleanup.
Moving some functionality from serial.c to omap-serial.c
Changes involves:
1.) Cleaning up certain uart
Hi,
I'm trying to boot Pandaboard ES with DT, but failing. I've debugged the
problem enough to see that the bootloader properly loads the DT blob,
and passes it to the kernel, but the kernel sees only garbage at that
address, and the devtree-magic check fails in setup_machine_fdt(). I
presume
On Mon, Dec 12, 2011 at 10:55 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Mon, Dec 12, 2011 at 9:12 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Dec 12, 2011 at 08:30:49PM +0200, Felipe Contreras wrote:
The short version is this: either we revert this patch[1], or we apply
this
On Tuesday 13 December 2011 06:33 PM, Tomi Valkeinen wrote:
Hi,
I'm trying to boot Pandaboard ES with DT, but failing. I've debugged the
problem enough to see that the bootloader properly loads the DT blob,
and passes it to the kernel, but the kernel sees only garbage at that
address, and the
Hi Tomi,
On 12/13/2011 2:03 PM, Tomi Valkeinen wrote:
Hi,
I'm trying to boot Pandaboard ES with DT, but failing. I've debugged the
problem enough to see that the bootloader properly loads the DT blob,
and passes it to the kernel, but the kernel sees only garbage at that
address, and the
On Tue, 2011-12-13 at 18:49 +0530, Rajendra Nayak wrote:
On Tuesday 13 December 2011 06:33 PM, Tomi Valkeinen wrote:
Hi,
I'm trying to boot Pandaboard ES with DT, but failing. I've debugged the
problem enough to see that the bootloader properly loads the DT blob,
and passes it to the
On Tuesday 13 December 2011 06:50 PM, Cousson, Benoit wrote:
I've just sent a patch to add the default DT config for OMAP. It will
add these config into the OMAP2plus Kconfig.
+select USE_OF
+select ARM_APPENDED_DTB
+select ARM_ATAG_DTB_COMPAT
+select PROC_DEVICETREE
In theory
Hi,
On Tue, 2011-12-06 at 17:49 +0100, Benoit Cousson wrote:
devicetree will become the mandatory boot method for OMAP2+.
In order to avoid cluttering the OMAP code with #ifdef CONFIG_OF,
select USE_OF by default for every OMAP2+ systems.
Select as well the APPENDED_DTB and ATAG_DTB_COMPAT to
On 12/13/2011 2:25 PM, Rajendra Nayak wrote:
On Tuesday 13 December 2011 06:50 PM, Cousson, Benoit wrote:
I've just sent a patch to add the default DT config for OMAP. It will
add these config into the OMAP2plus Kconfig.
+ select USE_OF
+ select ARM_APPENDED_DTB
+ select ARM_ATAG_DTB_COMPAT
+
From: Mythri P K mythr...@ti.com
HDMI even if enabled by default should be powered on only when the cable is
connected. This is supported by the Hot-plug feature.
Now when HDMI is enabled the following steps are followed:
-Display enable for HDMI is based on Hot-plug-detect(HPD).
-It registers to
From: Mythri P K mythr...@ti.com
Add support for HPD GPIO configuration in board file.
Also remove the enabling of GPIO's required for HDMI from
hdmi driver file to display.c based on the GPIO #'s sent from
board file.
Signed-off-by: Mythri P K mythr...@ti.com
---
From: Mythri P K mythr...@ti.com
Add option in the panel to enable HDMI in HPD mode to enable the interrupt to
detect cable connect/disconnect, HDMI will be powered on only when the cable is
connected and powered down when cable is disconnected.
Signed-off-by: Mythri P K mythr...@ti.com
---
From: Mythri P K mythr...@ti.com
GPIO based handling of connect/disconnect of the HDMI cable
(Hot-plug detect)is added to the HDMI driver.
Signed-off-by: Mythri P K mythr...@ti.com
---
drivers/video/omap2/dss/dss.h |2 +
drivers/video/omap2/dss/hdmi.c | 76
On 12/13/2011 2:27 PM, Tomi Valkeinen wrote:
Hi,
On Tue, 2011-12-06 at 17:49 +0100, Benoit Cousson wrote:
devicetree will become the mandatory boot method for OMAP2+.
In order to avoid cluttering the OMAP code with #ifdef CONFIG_OF,
select USE_OF by default for every OMAP2+ systems.
Select as
Hi,
On Mon, Dec 12, 2011 at 7:38 PM, Samuel Ortiz sa...@linux.intel.com wrote:
On Sun, Nov 27, 2011 at 07:17:41AM +1100, NeilBrown wrote:
The recent tidying up of twl4030-irq seems to have left it broken.
At least it doesn't work for me on my gta04 (www.gta04.org). The
first interrupt from
Hi Kevin,
On Wednesday 07 December 2011 05:51 AM, Kevin Hilman wrote:
Govindraj.Rgovindraj.r...@ti.com writes:
Converting uart driver to adapt to pm runtime API's.
Code re-org + cleanup.
Moving some functionality from serial.c to omap-serial.c
Alan, can you confirm your Ack's are still
Kevin,
-Original Message-
From: Vishwanath Sripathy [mailto:vishwanath...@ti.com]
Sent: Friday, December 02, 2011 10:29 PM
To: Kevin Hilman
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: RE: [PATCHv2 0/7]ARM: OMAP3PLUS PM: Add IO DaisyChain
support
Rajendra Nayak rna...@ti.com writes:
Hi Kevin,
On Wednesday 07 December 2011 05:51 AM, Kevin Hilman wrote:
Govindraj.Rgovindraj.r...@ti.com writes:
Converting uart driver to adapt to pm runtime API's.
Code re-org + cleanup.
Moving some functionality from serial.c to omap-serial.c
Alan,
* Alex al...@meprolight.com [111212 06:49]:
This patch adds DSS2 support to the LogicPD OMAP 35x Torpedo boardfile. LCD
and
TV-out are supported.
Signed-off-by: Alex Gershgorin al...@meprolight.com
This one should be OK to go via Tomi's DSS tree:
Acked-by: Tony Lindgren t...@atomide.com
Govindraj govindraj...@gmail.com writes:
[...]
I have re-based this patch series against LO master
commit id: deee6d5359969a0ce4e2760cfd7b9f379bd5698a
Same is available here [1]
I have tested this patch series along with:
1.) Tero's V11 irq chaining series
Vishwanath Sripathy vishwanath...@ti.com writes:
Kevin,
-Original Message-
From: Vishwanath Sripathy [mailto:vishwanath...@ti.com]
Sent: Friday, December 02, 2011 10:29 PM
To: Kevin Hilman
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: RE: [PATCHv2
Jean,
Could you pull the following I2C fixes for the OMAP platform for v3.2?
The first one belongs in stable (change log already Cc's sta...@vger.kernel.org)
Since this is an embedded platform, I have asked Ben Dooks a few times
but gotten no response, so am hoping you can queue these before
On Mon, Dec 12, 2011 at 11:44:45AM -0800, Tony Lindgren wrote:
* Felipe Contreras felipe.contre...@gmail.com [111208 11:52]:
On Thu, Dec 8, 2011 at 4:40 PM, Heikki Krogerus kro...@gmail.com wrote:
On Wed, Dec 07, 2011 at 09:56:56PM +0200, Felipe Contreras wrote:
From: Heikki Krogerus
On Mon, Dec 12, 2011 at 9:44 PM, Tony Lindgren t...@atomide.com wrote:
* Felipe Contreras felipe.contre...@gmail.com [111208 11:52]:
On Thu, Dec 8, 2011 at 4:40 PM, Heikki Krogerus kro...@gmail.com wrote:
On Wed, Dec 07, 2011 at 09:56:56PM +0200, Felipe Contreras wrote:
From: Heikki Krogerus
Hi Neil,
On Tue, Dec 13, 2011 at 08:39:59AM +1100, NeilBrown wrote:
The following 4 patches make it work for me and addresses some other
less critical issues like a typo in a comment :-)
Thanks, I applied all 4 of them.
Thanks. I have a couple of other twl4030 patches, these ones
From: Charulatha V ch...@ti.com
In omap3, save/restore context is implemented for GPIO banks 2-6 as GPIO bank1
is in wakeup domain. Instead of identifying bank's power domain by bank id,
use 'loses_context' flag which is filled by pwrdm_can_ever_lose_context()
during dev_init.
For getting the
From: Charulatha V ch...@ti.com
Currently gpio_context array used to save gpio bank's context, is used only for
OMAP3 architecture. Move gpio_context as part of gpio_bank structure so that it
can be specific to each gpio bank and can be used for any OMAP architecture
Signed-off-by: Charulatha V
It is not required to use hard-coded offsets any more in context save and
restore functions and instead use the generic offsets which have been correctly
initialized during device registration.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Signed-off-by: Charulatha V ch...@ti.com
From: Nishanth Menon n...@ti.com
GPIO debounce registers need to be saved and restored for proper functioning
of driver.
Signed-off-by: Nishanth Menon n...@ti.com
tarun.ka...@ti.com: Debounce context save is moved to _set_gpio_debounce()
as part of dynamic context save to remove overhead.
From: Charulatha V ch...@ti.com
Use regs-pinctrl field instead of using the macro OMAP1510_GPIO_PIN_CONTROL
Signed-off-by: Charulatha V ch...@ti.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap1/gpio15xx.c |1
From: Charulatha V ch...@ti.com
The gpio_bank_count is the count of number of GPIO devices in a SoC. Remove this
dependency from the driver by using list. Also remove the dependency on array of
pointers to gpio_bank struct of all GPIO devices.
Signed-off-by: Charulatha V ch...@ti.com
From: Nishanth Menon n...@ti.com
GPIO IP revisions such as those used in OMAP4 have a set_dataout
while the previous revisions used a single dataout register.
Depending on what is available restore the dataout settings
to the right register.
Signed-off-by: Nishanth Menon n...@ti.com
This series is continuation of cleanup of OMAP GPIO driver and fixes.
The cleanup include getting rid of cpu_is_* checks wherever possible,
use of gpio_bank list instead of static array, use of unique platform
specific value associated data member to OMAP platforms to avoid
cpu_is_* checks. The
Modify omap_gpio_prepare_for_idle() omap_gpio_resume_after_idle() functions
to handle save context restore context respectively in the OMAP GPIO driver
itself instead of calling these functions from pm specific files.
For this, in gpio_prepare_for_idle(), call *_get_context_loss_count() and in
From: Charulatha V ch...@ti.com
Remove cpu-is checks while enabling/disabling OMAP GPIO module during a gpio
request/free.
Signed-off-by: Charulatha V ch...@ti.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/gpio.c
From: Nishanth Menon n...@ti.com
Setup the dataout register before restoring OE. This is to make
sure that we have valid data in dataout register which would be
made available in output pins as soon as OE is enabled. Else,
there is risk of unknown data getting out into gpio pins.
Signed-off-by:
Context is now saved dynamically in respective functions whenever and
whichever registers are modified. This avoid overhead of saving all
registers context in the runtime suspend callback.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Reviewed-by: Santosh Shilimkar
Getting rid of ifdefs within the function by adding register offset intctrl
and associating OMAP_GPIO_INT_CONTROL in respective SoC specific files.
Also, use wkup_status register consistently instead of referring to wakeup
clear and wakeup set register offsets. Get rid of cpu_is_ checks in
From: Charulatha V ch...@ti.com
In all OMAP1 SoCs, the MPUIO bank width is 16 bits. But, in OMAP7xx,
it is wrongly initialised to 32. Fix this.
Signed-off-by: Charulatha V ch...@ti.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
Remove un-necessary bit masking. Since the register are 4 byte aligned
and readl would work as is. The 'enabled' mask is already taking care
to mask for bank width.
Signed-off-by: Charulatha V ch...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Reviewed-by: Santosh Shilimkar
Call runtime pm APIs pm_runtime_get_sync() and pm_runtime_put()
for enabling/disabling clocks appropriately. Remove syscore_ops and
instead use SET_RUNTIME_PM_OPS macro.
There is no more need to call omap_device_disable_idle_on_suspend
since driver is PM runtime adapted now.
Signed-off-by:
With register offsets now defined for respective OMAP versions we can get rid
of cpu_class_* checks. This function now has common initialization code for
all OMAP versions. Initialization specific to OMAP16xx has been moved within
omap16xx_gpio_init().
Signed-off-by: Tarun Kanti DebBarma
Wakeup enable register offset initialized according to OMAP versions
during device registration. Use this to avoid version checks.
Starting with OMAP4, legacy registers should not be used in combination
with the updated regsiters. Use wkup_en register consistently for
all SoCs wherever applicable.
There is no need to operate on all the banks every time the function is called.
Just operate on the current bank passed by the framework.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/gpio/gpio-omap.c | 54
The dbck_enable_mask indicates which all GPIOs within a bank have debounce
enabled and dbck is enabled/disabled based upon this. But there is no
mechanism to track the dbck state. In order to manage the dbck state we need
additional flag and logic so that turning off/on dbck is synchronized with
From: Nishanth Menon n...@ti.com
Setup the interrupt enable registers only after we have configured the
required edge and required configurations, not before, to prevent
spurious events as part of restore routine.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Tarun Kanti DebBarma
From: Charulatha V ch...@ti.com
Non-wakeup GPIOs are available only in OMAP2. Avoid cpu_is checks by making
non_wakeup_gpios as part of pdata.
Signed-off-by: Charulatha V ch...@ti.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
Enable debounce clock before writing/reading debounce registers.
Disable the clock at the end so that it is synchronized with the
pm_runtime_get/put_sync calls.
Enable debounce clock per module. This call is mandatory because
in omap_gpio_request() when *_runtime_get_sync() is called,
By adding level and edge detection register offsets and then initializing them
correctly according to OMAP versions during device registrations we can now
remove
lot of revision checks in these functions.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Signed-off-by: Charulatha V
Since *_prepare_for_idle() and *_resume_after_idle() are called
with interrupts disabled they should be kept as simple as possible.
So, moving most of the stuff to *_runtime_suspend/resume() callbacks.
To avoid invalid context restore happening in *_runtime_resume()
callback as a result of
From: Charulatha V ch...@ti.com
The only bank-type (method) used in the OMAP GPIO driver is MPUIO type as they
need to be handled separately. Identify the same using a flag and remove all
METHOD_* macros.
mpuio_init() function is defined under #ifdefs. It is required only in case
of MPUIO bank
Hi Felipe,
On Tue, Dec 13, 2011 at 04:12:02PM +0200, Felipe Contreras wrote:
Hi,
On Mon, Dec 12, 2011 at 7:38 PM, Samuel Ortiz sa...@linux.intel.com wrote:
On Sun, Nov 27, 2011 at 07:17:41AM +1100, NeilBrown wrote:
The recent tidying up of twl4030-irq seems to have left it broken.
At
Hi Tero
On Mon, 12 Dec 2011, Tero Kristo wrote:
From: R, Govindraj govindraj.r...@ti.com
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the
Hi
On Mon, 12 Dec 2011, Tero Kristo wrote:
From: R, Govindraj govindraj.r...@ti.com
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given
On Mon, Dec 12, 2011 at 9:09 AM, Jarkko Nikula jarkko.nik...@bitmer.com wrote:
Indeed yes. I checked that in 3.0 it still works but not in 3.1 so some
non isp1704_charger change has broke it as there hasn't been changes on it.
Actually it's broken in 3.0 as well, try this configuration:
Hi Govindraj, Tero,
another question about this patch:
On Tue, 13 Dec 2011, Paul Walmsley wrote:
diff --git a/arch/arm/mach-omap2/omap_hwmod.c
b/arch/arm/mach-omap2/omap_hwmod.c
index 207a2ff..ec19841 100644
--- a/arch/arm/mach-omap2/omap_hwmod.c
+++ b/arch/arm/mach-omap2/omap_hwmod.c
@@
What's the best way to enable sys_clkout2 (DM3730, latest kernel)?
I've managed to set it up properly and it runs in U-Boot, but the
kernel is disabling it. It's a bit of a tangle trying to figure out
not only what piece of code is undoing my work, but how to get the
clock to keep running. I
* Felipe Contreras felipe.contre...@gmail.com [111213 11:33]:
On Mon, Dec 12, 2011 at 9:44 PM, Tony Lindgren t...@atomide.com wrote:
* Felipe Contreras felipe.contre...@gmail.com [111208 11:52]:
On Thu, Dec 8, 2011 at 4:40 PM, Heikki Krogerus kro...@gmail.com wrote:
On Wed, Dec 07, 2011 at
On Tue, 13 Dec 2011, Gary Thomas wrote:
What's the best way to enable sys_clkout2 (DM3730, latest kernel)?
I've managed to set it up properly and it runs in U-Boot, but the
kernel is disabling it. It's a bit of a tangle trying to figure out
not only what piece of code is undoing my work, but
Hi
a question
On Mon, 12 Dec 2011, Tero Kristo wrote:
So the patch description says:
From: R, Govindraj govindraj.r...@ti.com
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
But the code does:
+ for (i = 0; i hmux-nr_pads; i++) {
+
Hi
one error:
On Tue, 13 Dec 2011, Paul Walmsley wrote:
struct clk *c;
c = clk_get(dev_name(dev), fck);
This should just be
c = clk_get(dev, fck);
sorry about that...
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
* Paul Walmsley p...@pwsan.com [111213 13:44]:
Hi
a question
On Mon, 12 Dec 2011, Tero Kristo wrote:
So the patch description says:
From: R, Govindraj govindraj.r...@ti.com
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
But the code does:
On Tue, 13 Dec 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [111213 13:44]:
On Mon, 12 Dec 2011, Tero Kristo wrote:
So the patch description says:
From: R, Govindraj govindraj.r...@ti.com
Add API to determine IO-PAD wakeup event status for a given
hwmod
* Cousson, Benoit b-cous...@ti.com [111213 05:02]:
On 12/13/2011 2:27 PM, Tomi Valkeinen wrote:
Hi,
On Tue, 2011-12-06 at 17:49 +0100, Benoit Cousson wrote:
devicetree will become the mandatory boot method for OMAP2+.
In order to avoid cluttering the OMAP code with #ifdef CONFIG_OF,
select
On Mon, Dec 12, 2011 at 2:32 PM, Tony Lindgren t...@atomide.com wrote:
Hi Arnd Olof,
Please pull omap hsmmc platform code changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap hsmmc
Ideally arch/arm/mach-omap2/hsmmc.c file will completely
disappear with device
Hi,
On Mon, Dec 12, 2011 at 2:46 PM, Tony Lindgren t...@atomide.com wrote:
Hi Arnd Olof,
Please pull two non-critical DMA fixes from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
fixes-non-critical
These are workarounds for corner cases. There's no rush
to get them
* Paul Walmsley p...@pwsan.com [111213 14:06]:
On Tue, 13 Dec 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [111213 13:44]:
On Mon, 12 Dec 2011, Tero Kristo wrote:
So the patch description says:
From: R, Govindraj govindraj.r...@ti.com
Add API to
On Tue, Dec 13, 2011 at 11:19:52PM +0200, Felipe Contreras wrote:
On Mon, Dec 12, 2011 at 9:09 AM, Jarkko Nikula jarkko.nik...@bitmer.com
wrote:
Indeed yes. I checked that in 3.0 it still works but not in 3.1 so some
non isp1704_charger change has broke it as there hasn't been changes on
On Wed, Dec 14, 2011 at 12:53 AM, Felipe Balbi ba...@ti.com wrote:
On Tue, Dec 13, 2011 at 11:19:52PM +0200, Felipe Contreras wrote:
On Mon, Dec 12, 2011 at 9:09 AM, Jarkko Nikula jarkko.nik...@bitmer.com
wrote:
Indeed yes. I checked that in 3.0 it still works but not in 3.1 so some
non
On 2011-12-13 14:56, Paul Walmsley wrote:
On Tue, 13 Dec 2011, Gary Thomas wrote:
What's the best way to enable sys_clkout2 (DM3730, latest kernel)?
I've managed to set it up properly and it runs in U-Boot, but the
kernel is disabling it. It's a bit of a tangle trying to figure out
not only
Govindraj govindraj...@gmail.com writes:
[...]
I have re-based this patch series against LO master
commit id: deee6d5359969a0ce4e2760cfd7b9f379bd5698a
Same is available here [1]
I have tested this patch series along with:
1.) Tero's V11 irq chaining series
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Hwmod is queried from the OMAP_PM layer to manage the power domains
nit: changelog needs a refresh as this isn't called from OMAP PM layer.
wake-up latency constraints. Hwmod retrieves the correct power domain
and if it
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
The MPU latency figures for cpuidle include the MPU itself and also
the peripherals needed for the MPU to execute instructions (e.g.
main memory, caches, IRQ controller, MMU etc). On OMAP3 those
peripherals belong to the MPU
Hi Jean,
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
. Implement the devices wake-up latency constraints using the global
device PM QoS notification handler which applies the constraints to the
underlying layer
. Implement the low level code which controls the
Benoit Cousson b-cous...@ti.com writes:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add documentation for omap i2c controller binding.
Based on original patches from Manju and Grant.
Signed-off-by: Benoit Cousson
Adds board support for an MT9M032 based camera to omap3evm.
Signed-off-by: Martin Hostettler mar...@neutronstar.dyndns.org
---
arch/arm/mach-omap2/Makefile|3 +-
arch/arm/mach-omap2/board-omap3evm-camera.c | 155 +++
On Tue, 13 Dec 2011, Gary Thomas wrote:
On 2011-12-13 14:56, Paul Walmsley wrote:
I presume you have some external device that relies on sys_clkout2 for
its clock input?
Precisely.
Okay, so the clean way to do this is to write a short driver for that
device, if there isn't one already,
On Tue, 13 Dec 2011, Tony Lindgren wrote:
Hmm yes that's even more true :) Maybe the right approach would be to
copy the OMAP_DEVICE_PAD_WAKEUP pins also to the dynamic list to
avoid going through all of them.
Looking at this further, it seems that the best thing to do for now is to
just add
Hi
so I've updated this patch to change the SCM PADCTRL registers if the
hwmod is currently idle, and _set_idle_ioring_wakeup() is called.
Otherwise calling _set_idle_ioring_wakeup() would be useless under those
conditions, since the new I/O ring wakeup values wouldn't be written back
to
Hi Tero
looking at this patch:
On Mon, 12 Dec 2011, Tero Kristo wrote:
From: R, Govindraj govindraj.r...@ti.com
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
It seems that your last patch drops the
From: Mike Turquette mturque...@ti.com
The common clk framework is an attempt to define a generic struct clk
which most platforms can use to build a clk tree and perform a set of
well-defined operations.
The previous patchset, v3, can be found at,
The common clk framework provides clk_prepare and clk_unprepare
implementations. Create an entry for HAVE_CLK_PREPARE so that
GENERIC_CLK can select it.
Signed-off-by: Mike Turquette mturque...@linaro.org
Acked-by: Shawn Guo shawn@linaro.org
---
drivers/clk/Kconfig |3 +++
1 files
Represents the clk tree as a directory hieraching in debugfs. Each clk
is a directory filled with the following read-only entries:
clk_rate
clk_flags
clk_prepare_count
clk_enable_count
clk_notifier_count
This commit borrows some code from Yong Shen's patch to export clkdev
clk's to debugfs:
Provide documentation for the common clk structures and APIs. This code
can be found in drivers/clk/ and include/linux/clk.h.
Signed-off-by: Mike Turquette mturque...@linaro.org
Cc: Jeremy Kerr jeremy.k...@canonical.com
---
Documentation/clk.txt | 312
The common clk framework is an attempt to define a common struct clk
which can be used by most platforms, and an API that drivers can always
use safely for managing clks.
The net result is consolidation of many different struct clk definitions
and platform-specific clk framework implementations.
1 - 100 of 127 matches
Mail list logo
