Hi,
On Thu, Sep 15, 2011 at 11:27 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2011-09-15 at 11:11 +0530, K, Mythri P wrote:
Hi,
On Wed, Sep 14, 2011 at 7:41 PM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Yes, you are right, detect() does not know if the monitor has changed
2011/9/13 Barry Song 21cn...@gmail.com:
2011/9/13 Jassi Brar jaswinder.si...@linaro.org:
On 13 September 2011 13:16, Barry Song 21cn...@gmail.com wrote:
if test pass, to the patch, and even for the moment, to the API's idea
Acked-by: Barry Song baohua.s...@csr.com
one issue i noticed is with
On Thu, 2011-09-15 at 11:54 +0530, K, Mythri P wrote:
Hi,
On Thu, Sep 15, 2011 at 11:27 AM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
On Thu, 2011-09-15 at 11:11 +0530, K, Mythri P wrote:
Hi,
On Wed, Sep 14, 2011 at 7:41 PM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Yes,
On 15 September 2011 12:01, Barry Song 21cn...@gmail.com wrote:
2011/9/13 Barry Song 21cn...@gmail.com:
2011/9/13 Jassi Brar jaswinder.si...@linaro.org:
On 13 September 2011 13:16, Barry Song 21cn...@gmail.com wrote:
if test pass, to the patch, and even for the moment, to the API's idea
2011/9/15 Jassi Brar jaswinder.si...@linaro.org:
On 15 September 2011 12:01, Barry Song 21cn...@gmail.com wrote:
2011/9/13 Barry Song 21cn...@gmail.com:
2011/9/13 Jassi Brar jaswinder.si...@linaro.org:
On 13 September 2011 13:16, Barry Song 21cn...@gmail.com wrote:
if test pass, to the patch,
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Thursday, September 15, 2011 6:02 AM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org; Hilman, Kevin; p...@pwsan.com; linux-arm-
ker...@lists.infradead.org
Subject: Re: [RFC PATCH-V2 0/4] Introducing TI's
These patches add support for the LCD and PicoDLP outputs for 4430SDP board.
Tomi
Tomi Valkeinen (3):
OMAP: DSS2: Taal: remove external backlight support
OMAP4: 4430SDP: Add panel support to board file
OMAP4: 4430SDP: Add picodlp support to board file
arch/arm/mach-omap2/board-4430sdp.c
Taal panel driver supports two kinds of backlight control: 1) using DSI
commands sent to the panel to control the backlight, 2) calling function
pointers going to the board file to control the backlight.
The second option is a bit hacky, and will no longer be needed when the
PWM driver supports
4430SDP has two Taal DSI panels, connected to DSI 1 and DSI 2 modules.
The panels use a common PWM backlight, which will be implemented later
when the PWM driver has been improved to support the backlight.
Until the PWM driver has been improved, the following hack added to
An on-board projector named picodlp is available for OMAP4430 SDP.
Entry for this picodlp as a panel is being added in dss_devices array to
the board file. It needs 4 GPIO pins for interfacing with host
processor and these are defined and two of them are configured in board
file. Two GPIOs
On Thu, Sep 15, 2011 at 11:25 AM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Wed, Sep 14, 2011 at 10:20 PM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Keshava,
On 8/25/2011 9:01 AM, Munegowda, Keshava wrote:
From: Benoit Coussonb-cous...@ti.com
Following 4 hwmod structures are
The patch below does not apply to the 3.0-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to sta...@kernel.org.
thanks,
greg k-h
-- original commit in Linus's tree
2011/9/15 Jassi Brar jaswinder.si...@linaro.org:
On 15 September 2011 12:01, Barry Song 21cn...@gmail.com wrote:
2011/9/13 Barry Song 21cn...@gmail.com:
2011/9/13 Jassi Brar jaswinder.si...@linaro.org:
On 13 September 2011 13:16, Barry Song 21cn...@gmail.com wrote:
if test pass, to the patch,
Hi Tony,
On Thu, Sep 15, 2011 at 11:12:53, DebBarma, Tarun Kanti wrote:
On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren t...@atomide.com wrote:
* Tarun Kanti DebBarma tarun.ka...@ti.com [110908 13:36]:
removed from timer code. New set of timers present on
OMAP4 are now supported.
Also, as
Paul, Rafael, Kevin,
Ping on this patch set.
IIUC the intention is to have this series merged in 3.2, is that correct?
Regards,
Jean
On Fri, Sep 2, 2011 at 3:13 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
. create a PM layer plugin for per-device constraints, compiled under
Hi Santosh,
On 9/14/2011 7:22 PM, Shilimkar, Santosh wrote:
On Wednesday 14 September 2011 10:48 PM, Tony Lindgren wrote:
* Santoshsantosh.shilim...@ti.com [110914 09:40]:
On Wednesday 14 September 2011 10:38 PM, Tony Lindgren wrote:
* Santoshsantosh.shilim...@ti.com[110914 09:16]:
On Wed, Sep 14, 2011 at 02:57:13PM -0400, Ohad Ben-Cohen wrote:
On Wed, Sep 14, 2011 at 5:07 PM, Joerg Roedel joerg.roe...@amd.com wrote:
Without this patch it is possible to select the VIDEO_OMAP3
driver which then selects OMAP_IOVMM. But the omap iommu
driver is not compiled without
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)
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/regulator/twl-regulator.c | 28 +---
1
The parameters to set_consumer_device_supply() can be considered
invalid (and hence it could return -EINVAL) if nether consumer_dev nor
consumer_dev_name are passed, not when *both* are passed.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/regulator/core.c |2 +-
1 files changed, 1
Modify the fixed regulator driver to extract fixed_voltage_config from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/regulator/fixed.c | 20 +++-
1 files changed, 19
Pass the fixed voltage regulator information for
omap4panda board from device tree.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
The helper routine is meant to be used by regulator drivers
to extract the regulator_init_data structure passed from device tree.
'consumer_supplies' which is part of regulator_init_data is not extracted
as the regulator consumer mappings are passed through DT differently,
implemented in
The helper routine defined here (of_get_fixed_voltage_config) can
be used to extract information about fixed regulators (which are not
software controlable) from device tree.
Add documenation about additional bindings for fixed
regulators that can be passed through DT.
Signed-off-by: Rajendra
The TWL driver seems to set the default .valid_modes_mask to
(REGULATOR_MODE_NORMAL | REGULATOR_MODE_STANDBY) and .valid_ops_mask
to (REGULATOR_CHANGE_VOLTAGE | REGULATOR_CHANGE_MODE | REGULATOR_CHANGE_STATUS)
for all the registered regulators.
There is no need for all the board files to pass
Hi Grant, Mark,
This RFC is an attempt to move the regulator mappings from
board files into device tree for OMAP. In the process I have
defined some helper routines for regulators and defined
the bindings for these.
The patches are based on top of Benoit's series which adds
DT support for i2c and
of_regulator_register_devices() registers all regulators
as platform devices. Use this to register all twl regulators
from the twl driver probe.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/mfd/twl-core.c |3 +++
drivers/of/of_regulator.c| 30
Pass regulator_init_data information for omap4sdp from device tree so the
regulator driver can then use the regulator helper
routine to extract and use them during the driver probe().
Add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
With device tree, the consumer regulator mapping is deferred till
a regulator_get is called from the corresponding device driver,
instead of being done during regulator_register.
This avoids a complete scan of all DT nodes to identify consumers
for all regulators.
Devices can assocaite with one
Device nodes in DT can associate themselves with one or more
regulators by providing a list of phandles (to regulator nodes)
and corresponding supply names.
For Example:
devicenode: node@0x0 {
...
...
regulator = regulator1,regulator2;
On Thu, Sep 15, 2011 at 3:06 PM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Santosh,
On 9/14/2011 7:22 PM, Shilimkar, Santosh wrote:
On Wednesday 14 September 2011 10:48 PM, Tony Lindgren wrote:
* Santoshsantosh.shilim...@ti.com [110914 09:40]:
On Wednesday 14 September 2011 10:38 PM,
Hi,
We're doing some development with the TI8168 EVM and have followed the
instructions on the TI wiki for enabling the /dev framebuffer. When we do this
we end up with a kernel halt during boot (see below for example).
Doing some investigation it looks like the for loop in
Hi Stuart,
On Thu, Sep 15, 2011 at 3:22 PM, Stuart Brown stuart.br...@plexus.com wrote:
Doing some investigation it looks like the for loop in mach-omap2/mailbox.c:
omap_mbox_get() might be wrong:
for(mbox = *mboxes; mbox; mbox++)
...
I'm hesitant to query this as it looks like this
From: Keshava Munegowda keshava_mgo...@ti.com
device name usbhs clocks are changed from
usbhs-omap.0 to usbhs_omap; this is because
in the hwmod registration the device name is set
as usbhs_omap; The redudant clock nodes are removed.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
---
Following 4 hwmod structure are added:
UHH hwmod of usbhs with uhh base address and functional clock,
EHCI hwmod with irq and base address,
OHCI hwmod with irq and base address,
TLL hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
---
From: Keshava Munegowda keshava_mgo...@ti.com
The Hwmod structures and Runtime PM features are implemented
For EHCI and OHCI drivers of OMAP3 and OMAP4.
The global suspend/resume of EHCI and OHCI
is validated on OMAP3430 sdp board with these patches.
these patches are rebased to kevin's pm
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks; These clocks are handled by hwmod and runtime pm,
hence instead of the clock enable/disable, the runtime pm APIS are
used. however,the port clocks are handled by the
The hwmod structure of uhh, ohci, ehci and tll are
retrieved and registered with omap device
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
---
arch/arm/mach-omap2/usb-host.c | 114 +--
1 files changed, 50 insertions(+), 64 deletions(-)
diff --git
From: Benoit Cousson b-cous...@ti.com
Following 4 hwmod structures are added:
UHH hwmod of usbhs with uhh base address and functional clock,
EHCI hwmod with irq and base address,
OHCI hwmod with irq and base address,
TLL hwmod of usbhs with the TLL base address and irq.
Signed-off-by: Benoit
From: Shilimkar, Santosh
Sent: Thursday, September 15, 2011 7:02 AM
You missed my point in the description. Clockdomain inactive
doesn't depend on idle or WFI execution. Under HW supervison
CPU clock domain can get into inactive when CPU is stalled and
waiting for a read response from
On Thu, Sep 15, 2011 at 04:51:57PM +0530, Rajendra Nayak wrote:
The TWL driver seems to set the default .valid_modes_mask to
(REGULATOR_MODE_NORMAL | REGULATOR_MODE_STANDBY) and .valid_ops_mask
to (REGULATOR_CHANGE_VOLTAGE | REGULATOR_CHANGE_MODE |
REGULATOR_CHANGE_STATUS)
for all the
On Thu, Sep 15, 2011 at 04:51:58PM +0530, Rajendra Nayak wrote:
The parameters to set_consumer_device_supply() can be considered
invalid (and hence it could return -EINVAL) if nether consumer_dev nor
consumer_dev_name are passed, not when *both* are passed.
Signed-off-by: Rajendra Nayak
Thanks Ohad,
It looks like this patch is missing from the arago-project linux-omap3 code
base.
We've been using the most recent release - T1816XPSP_04.00.00.12.
What would the procedure be to get this patch applied to the arago-project?
Stuart
-Original Message-
From: Ohad Ben-Cohen
On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
.../devicetree/bindings/regulator/regulator.txt| 37 +
drivers/of/Kconfig |6 ++
drivers/of/Makefile|1 +
drivers/of/of_regulator.c
On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
+Required properties:
+- compatible: Must be regulator,ti,twl-reg;
I'd expect listings for the specific chips too.
+ xyz-regulator: regulator@0 {
+ compatible = regulator,ti,twl-reg;
+ ti,reg-id =
On Thu, Sep 15, 2011 at 4:40 PM, Stuart Brown stuart.br...@plexus.com wrote:
What would the procedure be to get this patch applied to the arago-project?
I have a feeling that asking Sanjeev will help ;)
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a
On Thu, Sep 15, 2011 at 04:52:02PM +0530, Rajendra Nayak wrote:
.../devicetree/bindings/regulator/regulator.txt| 19
drivers/of/of_regulator.c | 31
include/linux/of_regulator.h |7
3 files
On Thu, Sep 15, 2011 at 04:52:03PM +0530, Rajendra Nayak wrote:
Modify the fixed regulator driver to extract fixed_voltage_config from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
The code you added in the previous patch should be part of
On Thu, Sep 15, 2011 at 04:52:05PM +0530, Rajendra Nayak wrote:
regulator = regulator1,regulator2;
regulator-names = supply1,supply2;
};
This syntax is really painful - we're relying on keeping two arrays in
sync which isn't good for legibility or robustness.
On Thu, Sep 15, 2011 at 04:52:06PM +0530, Rajendra Nayak wrote:
+#ifdef CONFIG_OF
+ struct device_node *node;
+ node = of_get_regulator(dev, id);
+ if (!node)
+ goto out;
+ list_for_each_entry(rdev, regulator_list, list)
+ if (node == rdev-node)
+
This provides a series of patches contributed by several people to
do correct charger detection and solve issues that came along with
the charger detection implementation.
USB_EVENT_NONE notification is sent only when a PC cable/CDP cable or
a device connected to MUSB is detached.
USB_EVENT_VBUS
Setting OTG_INTERFSEL to UTMI interferes with charger detection resulting
in incorrect detection of charger type. Hence OTG_INTERFSEL is configured to
ULPI initially and changed to UTMI only after receiving USB_EVENT_ID or
USB_EVENT_VBUS notification.
Signed-off-by: Kishon Vijay Abraham I
omap4430_phy_power is modified to be self contained in that it enables clock
and power up the phy in addition to modifying the USBOTGHS_CONTROL register
during power on. Similarly while powering down, it disables clock and
power down the phy.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
From: Balaji T K balaj...@ti.com
Set the current supplied by dedicated charging port to 1800mV(according to
battery charging specification). Also added a callback function for set_power
to dynamically set the current to be supplied based on the state of the system.
Signed-off-by: Balaji T K
From: Sergii Postulga x0153...@ti.com
Charger detection is given 500ms to complete until which it loops continuously
taking all the processor time. If we plug USB-micro cable to board during
playing video or audio we have a glitches. This patch frees time for doing
other things during waiting
From: Viswanath Puttagunta vi...@ti.com
The charger detection module is getting
disabled during boot up if a DCP (Dedicated charging port)
is connected before device is powered on (Bit 30 of CONTROL_USB2PHYCORE
is set). This patch enables charger type detection each time the charger type
wants to
From: Balaji T K balaj...@ti.com
Charger detection is done in threaded irq and is performed only when OMAP
acts as B-device. Phy is powered on before charger detection and is powered
down once charger detection is completed. The type of charger is sent through
all the registered notifiers.
On Thu, Sep 15, 2011 at 04:52:07PM +0530, Rajendra Nayak wrote:
of_regulator_register_devices() registers all regulators
as platform devices. Use this to register all twl regulators
from the twl driver probe.
Regulators can be devices of any type, not just platform devices.
On Thu, Sep 15, 2011 at 3:12 AM, Rusty Russell ru...@rustcorp.com.au wrote:
7... numbers are cheap :)
7 it is :)
Thanks,
Ohad.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Arnd,
On Fri, Sep 02, 2011 at 04:43:36PM +0200, Arnd Bergmann wrote:
We currently have two symbols to control compilation the MFD subsystem,
MFD_SUPPORT and MFD_CORE. The MFD_SUPPORT is actually not required
at all, it only hides the submenu when not set, with the effect that
Kconfig warns
Hi Hemanth,
On Tue, Aug 30, 2011 at 12:27:17PM +0530, Hemanth V wrote:
From: Hemanth V heman...@ti.com
Date: Fri, 26 Aug 2011 10:49:29 +0530
Subject: [PATCH] Add PWM1 and PWM2 support to twl6030-pwm driver
This patch adds support for PWM1/PWM2. TWL6030 PWM driver also
supports Indicator
Hi THomas,
On Mon, Sep 05, 2011 at 11:26:33AM +0200, Thomas Weber wrote:
The codec for Devkit8000 (TWL4030) was not detected except
when build with CONFIG_SND_SOC_ALL_CODECS.
twl-core.c still uses the CONFIG_TWL4030_CODEC for
twl_has_codec().
In commit
* Mohammed, Afzal af...@ti.com [110915 01:13]:
Hi Tony,
On Thu, Sep 15, 2011 at 11:12:53, DebBarma, Tarun Kanti wrote:
On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren t...@atomide.com wrote:
* Tarun Kanti DebBarma tarun.ka...@ti.com [110908 13:36]:
removed from timer code. New set of
Hi Santosh,
On Tue, Sep 06, 2011 at 09:29:30PM +0530, Santosh Shilimkar wrote:
TWL6030 devices have an interrupt line which is connected to
application processor like OMAP. These devices support multiple features
such as MMC card detect, USB cable detect, RTC interrupt, etc. that must
wake up
* Tony Lindgren t...@atomide.com [110915 09:24]:
* Mohammed, Afzal af...@ti.com [110915 01:13]:
We need clocksource clockevent to be able to work with
timers requiring addition of offsets. Without this AM335X,
TI816X and TI814X SoC's will not boot.
OK. Then how about let's do the
Koyamangalath, Abhilash abhilash...@ti.com writes:
hi Kevin
On Tue, Sep 13, 2011 at 11:54 PM, Hilman, Kevin wrote:
Hi Abhilash,
Koyamangalath, Abhilash abhilash...@ti.com writes:
Hi
On Wed, Aug 31, 2011 at 4:28 AM, Hilman, Kevin wrote:
Abhilash K V abhilash...@ti.com writes:
snip
On Mon, Aug 29, 2011 at 09:41:47PM +0300, Luciano Coelho wrote:
---
@@ -417,7 +417,6 @@ config GPIO_TIMBERDALE
config GPIO_RDC321X
tristate RDC R-321x GPIO support
depends on PCI
- select MFD_SUPPORT
select MFD_CORE
select MFD_RDC321X
help
diff --git
Santosh santosh.shilim...@ti.com writes:
On Wednesday 14 September 2011 01:57 AM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [110904 06:22]:
On OMAP4 SOC intecronnects has many write buffers in the async bridges
and they can be drained only with stongly ordered
On Thu, Sep 15, 2011 at 10:47 PM, Kevin Hilman khil...@ti.com wrote:
Santosh santosh.shilim...@ti.com writes:
On Wednesday 14 September 2011 01:57 AM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [110904 06:22]:
On OMAP4 SOC intecronnects has many write buffers in the
Hello,
There have been ongoing problems for awhile now where ti.com addresses
have been randomly unsubscribed from vger.kernel.org lists (linux-omap,
linux-kernel, etc.)
Luca and myself have been working with TI IT to figure out this problem,
and they claim to have fixed the problem (details on
On Thu, Sep 15, 2011 at 10:32 PM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Santosh,
On Tue, Sep 06, 2011 at 09:29:30PM +0530, Santosh Shilimkar wrote:
TWL6030 devices have an interrupt line which is connected to
application processor like OMAP. These devices support multiple features
* Shilimkar, Santosh santosh.shilim...@ti.com [110915 09:51]:
On Thu, Sep 15, 2011 at 10:47 PM, Kevin Hilman khil...@ti.com wrote:
Santosh santosh.shilim...@ti.com writes:
On Wednesday 14 September 2011 01:57 AM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [110904
On 09/15/2011 08:44 AM, Mark Brown wrote:
On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
.../devicetree/bindings/regulator/regulator.txt| 37 +
drivers/of/Kconfig |6 ++
drivers/of/Makefile|
On Thu, Sep 15, 2011 at 11:23 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [110915 09:51]:
On Thu, Sep 15, 2011 at 10:47 PM, Kevin Hilman khil...@ti.com wrote:
Santosh santosh.shilim...@ti.com writes:
On Wednesday 14 September 2011 01:57 AM, Tony
On 09/15/2011 06:21 AM, Rajendra Nayak wrote:
The helper routine is meant to be used by regulator drivers
to extract the regulator_init_data structure passed from device tree.
'consumer_supplies' which is part of regulator_init_data is not extracted
as the regulator consumer mappings are
Tony,
Please pull the OMAP voltage layer cleanup for v3.2.
This is a combination of the series A..E that have been posted, with
a handful of updates throughout the comments and kerneldoc.
It is based on the powerdomain/clockdomain OMAP_CHIP cleanup from Paul
(his
* Shilimkar, Santosh santosh.shilim...@ti.com [110915 10:49]:
On Thu, Sep 15, 2011 at 11:23 PM, Tony Lindgren t...@atomide.com wrote:
Please also include the errata in the description and set it up with
a Kconfig entry with something like ARM_ERRATA_XX or TI_ERRATA_XX.
Sure.
On Thu, 2011-09-15 at 10:26 -0700, Kevin Hilman wrote:
Hello,
There have been ongoing problems for awhile now where ti.com addresses
have been randomly unsubscribed from vger.kernel.org lists (linux-omap,
linux-kernel, etc.)
Luca and myself have been working with TI IT to figure out this
On Fri, Sep 16, 2011 at 1:13 AM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [110915 10:49]:
On Thu, Sep 15, 2011 at 11:23 PM, Tony Lindgren t...@atomide.com wrote:
Please also include the errata in the description and set it up with
a Kconfig entry
On Tue, Sep 06, 2011 at 09:29:30PM +0530, Santosh Shilimkar wrote:
TWL6030 devices have an interrupt line which is connected to
application processor like OMAP. These devices support multiple features
such as MMC card detect, USB cable detect, RTC interrupt, etc. that must
wake up the
On Thu, Sep 15, 2011 at 04:51:59PM +0530, Rajendra Nayak wrote:
The helper routine is meant to be used by regulator drivers
to extract the regulator_init_data structure passed from device tree.
'consumer_supplies' which is part of regulator_init_data is not extracted
as the regulator consumer
On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
Pass regulator_init_data information for omap4sdp from device tree so the
regulator driver can then use the regulator helper
routine to extract and use them during the driver probe().
Add documentation for TWL regulator specific
On Thu, Sep 15, 2011 at 02:46:18PM +0100, Mark Brown wrote:
On Thu, Sep 15, 2011 at 04:52:00PM +0530, Rajendra Nayak wrote:
+Required properties:
+- compatible: Must be regulator,ti,twl-reg;
I'd expect listings for the specific chips too.
+ xyz-regulator: regulator@0 {
+
On Thu, Sep 15, 2011 at 04:52:01PM +0530, Rajendra Nayak wrote:
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)
Signed-off-by: Rajendra Nayak rna...@ti.com
---
On Thu, Sep 15, 2011 at 04:52:02PM +0530, Rajendra Nayak wrote:
The helper routine defined here (of_get_fixed_voltage_config) can
be used to extract information about fixed regulators (which are not
software controlable) from device tree.
Add documenation about additional bindings for fixed
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
Convert the driver from the outdated omap_pm_set_max_mpu_wakeup_lat
API to the new PM QoS API.
Since the constraint is on the MPU subsystem, use the PM_QOS_CPU_DMA_LATENCY
class of PM QoS. The resulting MPU constraints are used by cpuidle
On Thu, Sep 15, 2011 at 02:54:16PM +0100, Mark Brown wrote:
On Thu, Sep 15, 2011 at 04:52:05PM +0530, Rajendra Nayak wrote:
regulator = regulator1,regulator2;
regulator-names = supply1,supply2;
};
This syntax is really painful - we're relying on keeping two
On Thu, Sep 15, 2011 at 04:50:35PM -0600, Grant Likely wrote:
We've got two competing approaches here. For reg and interrupts, the
proposal on the table that we talked about at LPC is to do reg-names
and interrupts-names so as to preserve the existing semantics of the
reg and interrupts
Hi, Yong
You're right. We figured out something is wrong (is negative) with
vruntime of certain processes.
Below link describes the same issue we observed.
http://lkml.indiana.edu/hypermail/linux/kernel/1101.2/00333.html
And the commite indicated by you is exactly the fix.
Appreciate it!.
On
* Kevin Hilman khil...@ti.com [110915 11:59]:
Tony,
Please pull the OMAP voltage layer cleanup for v3.2.
This is a combination of the series A..E that have been posted, with
a handful of updates throughout the comments and kerneldoc.
It is based on the powerdomain/clockdomain OMAP_CHIP
Tony,
Please pull this omap_device cleanup series for v3.2. This sets the
groundwork for Benoit's DT infrastructure work.
Kevin
The following changes since commit b6fd41e29dea9c6753b1843a77e50433e6123bcb:
Linux 3.1-rc6 (2011-09-12 14:02:02 -0700)
are available in the git repository at:
Jean Pihet jean.pi...@newoldbits.com writes:
Implement the devices wake-up latency constraints using the global
device PM QoS notification handler which applies the constraints to the
underlying layer by calling the corresponding function at hwmod level.
Note: the bus throughput function is
Kevin Hilman khil...@ti.com writes:
Please pull this omap_device cleanup series for v3.2. This sets the
groundwork for Benoit's DT infrastructure work.
Turns out this series has a dependency on a patch[1] in Russell's
for-next branch.
Russell, any chance of picking this patch into your
On 09/15/11 06:22, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks; These clocks are handled by hwmod and runtime pm,
hence instead of the clock enable/disable, the runtime pm APIS are
On Thu, Sep 15, 2011 at 10:35 PM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [110915 09:24]:
* Mohammed, Afzal af...@ti.com [110915 01:13]:
We need clocksource clockevent to be able to work with
timers requiring addition of offsets. Without this AM335X,
On Fri, Sep 16, 2011 at 2:07 AM, Todd Poynor toddpoy...@google.com wrote:
On Tue, Sep 06, 2011 at 09:29:30PM +0530, Santosh Shilimkar wrote:
TWL6030 devices have an interrupt line which is connected to
application processor like OMAP. These devices support multiple features
such as MMC card
On Fri, Sep 16, 2011 at 6:10 AM, Frank Rowand frank.row...@am.sony.com wrote:
On 09/15/11 06:22, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The usbhs core driver does not enable/disable the interface and
functional clocks; These clocks are handled by hwmod and
96 matches
Mail list logo
