112527034193_579960007066Gadiyar Anand

 
161021404435_543060007795Felipe Balbi

 
185327304050_594560007389Gadiyar Anand

 
123020974284_518460007745Gadiyar Anand

 
114126914035_551360007902Shilimkar Santosh
Felipe Balbi wrote: Hi, On Fri, Aug 20, 2010 at 07:47:07AM +0200, ext Gadiyar, Anand wrote: The differences between OMAP3 and OMAP4 are: - The OMAP4 has a different set of clocks which d

 
165720254605_585160007697Shubhrajyoti D

 
191724354837_535260007817Kevin Hilman
Datta, Shubhrajyoti wrote: Subject: [RFC PATCH] Board support for the the GPIO keys Please tag $SUBJECT with something like "omap: 4430sdp: " Board support for the GPIO keys. The

 
114627184546_519660007924Varadarajan Charulat
Thanks for the review -----Original Message----- From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ] Sent: Thursday, August 26, 2010

 
158628924021_587060007212Murphy Dan
Hi Charu, Agree to your comments. Will fix them. -----Original Message----- From: Varadarajan, Charulatha Sent: Friday, August 20, 2010 12:13 PM To: Datta, Shubhrajyoti; linux-omap@xxxxxxxxx

 
161422164903_564960007804Marc Chalain

 
155123864830_515560007654Robert Nelson

 
185221534088_568960007954Robert Nelson
system_rev comes from u-boot and is a constant 0x20, so Bx boards also fall in this if and will get setup with the wrong gpio_wp pin. Switch to using the Beagle revision routine to correcly set pi

 
150526524671_505160007333Robert Nelson
On Wed, 18 Aug 2010 10:56:51 -0500 Robert Nelson <robertcnelson@xxxxxxxxx wrote: + ret = gpio_request(171, "rev_id_0"); + if (ret < 0) + goto fail0; + + ret = gpio_reques

 
197624344224_599760007299Keshava Munegowda
Make TLL channel count a parameter instead of a hardcoded value. This allows us to be flexible with future OMAP revisions which could have a different number of channels. Signed-off-by: Keshava Mune

 
120829184516_511160007245Keshava Munegowda
Rename usbhost2_120m_fck to usbhost_hs_fck and usbhost1_48m_fck to usbhost_fs_fck, so that we can reuse the names across OMAP3 and OMAP4. OMAP3 and OMAP4 have similar clocks, with different frequenc

 
191521184632_574560007869Keshava Munegowda
The PHY reset code is moved at the begining and end of the function omap_start_ehc. This simplfies the writing clocks enabling code for OMAP4 later. Signed-off-by: Keshava Munegowda <keshava_mg

 
139821254021_548760007528Munegowda Keshava
Make TLL channel count a parameter instead of a hardcoded value. This allows us to be flexible with future OMAP revisions which could have a different number of channels. Signed-off-by: Keshava Mune

 
144123204179_511160007028Munegowda Keshava

 
144423464463_566960007767Munegowda Keshava

 
196925524684_548460007251Gadiyar Anand

 
173025784369_536160007643Greg KH
-----Original Message----- From: Munegowda, Keshava Sent: Wednesday, August 18, 2010 8:26 AM To: linux-usb@xxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx Cc: Munegowda, Keshava Subject: [PAT

 
122927214769_525160007584Hema HK
-----Original Message----- From: Greg KH [ rel="nofollow" mailto:greg@xxxxxxxxx mailto:greg@xxxxxxxxx ] Sent: Wednesday, September 08, 2010 2:26 PM To: Munegowda, Keshava Cc: linux-usb-o

 
177926494904_595960007275Kalliguddi Hema
Hema HK <hemahk@xxxxxx writes: Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync() for enabling/disabling the clocks,sysconfig settings. used omap_hwmod_enable_wakeup

 
198722044621_545060007965Kalliguddi Hema
"Kalliguddi, Hema" <hemahk@xxxxxx writes: static int musb_platform_resume(struct musb *musb) { u32 l; + struct device *dev = musb- controller; + struct

 
121628424516_590160007179Kevin Hilman
OMAP USBOTG modules has a requirement to set the auto idle bit only after setting smart idle bit. Modified the _sys_enable api to set the smart idle first and then the autoidle bit. Setting this will

 
115120554757_552160007079Hema HK
Hi, -----Original Message----- From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ] Sent: Thursday, August 26, 2010 5:12 AM To: Kallig

 
116326464800_593360007008Kalliguddi Hema
Hema HK <hemahk@xxxxxx writes: With OMAP core-off support musb was not functional as context was getting lost after wakeup from core-off. And also musb was blocking the core-off after load

 
151626764657_541960007417Kalliguddi Hema
"Kalliguddi, Hema" <hemahk@xxxxxx writes: -----Original Message----- From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ]

 
169426214622_531560007495Hema HK
Using omap_device_build api instead of platform_device_register for musb device registration.The device specific resources defined in centralized database will be used. So removed the resource defini

 
127922864336_579660007663Hema HK
OMAP3 hwmod data stuctures are populated with base address, L3 and L4 interface clocks, IRQs,and sysconfig register details. Signed-off-by: Hema HK <hemahk@xxxxxx Cc: Felipe Balbi <felipe.bal

 
197523384718_573160007134Hema HK
Modified the Omap,Blackfin and Davinci board files to add the name of the IRQs in the resource structures and musb driver to use the get_irq_byname() api to get the mc and dma irq numbers instead of

 
181120224781_561160007678Kalliguddi Hema
Hema HK <hemahk@xxxxxx writes: Cc: Felipe Balbi <felipe.balbi@xxxxxxxxx Cc: Tony Lindgren <tony@xxxxxxxxxxx Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx Cc: Cousson, Benoit

 
161924714354_527660007988Krogerus Heikki EXTT
-----Original Message----- From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ] Sent: Thursday, August 26, 2010 5:29 AM To: Kalligudd

 
169325844609_531460007680Heikki Krogerus
On Wed, Aug 18, 2010 at 04:01:05PM +0300, Krogerus Heikki (EXT-Teleca/Helsinki) wrote: From: Heikki Krogerus <ext-heikki.krogerus@xxxxxxxxx NXP ISP1704 is Battery Charging Specification 1.

 
181021794966_514560007152Heikki Krogerus

 
180929494491_552660007350Thara Gopinath
+static void isp1704_charger_work(struct work_struct *data) +{ + struct isp1704_charger *isp = + container_of(data, struct isp1704_charger, work); + + /* FIXME Only supporting dedicated

 
166124914373_544260007327Kevin Hilman
This patch introduces a user list of devices associated with each voltage domain instance. The user list is implemented using plist structure with priority node populated with the voltage values. Thi

 
112027214799_547460007689Kevin Hilman
Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx writes: + if (!found) { + user = kzalloc(sizeof(struct omap_vdd_user_list), GFP_KERNEL); + if (!user) { + pr_err("%s: Unable to cre

 
146226894273_507060007172Nishanth Menon
Hello, On Wed, 01 Sep 2010 15:51:40 -0700 Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx wrote: Looking closer at this, keeping track of a list of devices and constraints is what the regulator f

 
175028134352_571660007326Nishanth Menon
On Thu, 2 Sep 2010 03:17:56 -0500, Nishanth Menon <nm@xxxxxx wrote: Just brainstorming - if we use the regulator framework - there are potential benefits - agreed. BUT, consider the cpuidle

 
186927674275_536060007956Nishanth Menon
Hi, On Thu, 2 Sep 2010 05:17:01 -0500, Nishanth Menon <nm@xxxxxx wrote: note - if we allow unlock of irqs at this point, we cannot predictably progress down the logic. spin_unlock() would

 
171029554446_508260007547Kevin Hilman
Hi, On Thu, 2 Sep 2010 05:40:56 -0500, Nishanth Menon <nm@xxxxxx wrote: Felipe Balbi had written, on 09/02/2010 05:28 AM, the following: Hi, On Thu, 2 Sep 2010 05:17:01 -0500, Nishan

 
141025164267_520960007263Kevin Hilman

 
189824514953_517060007956Kevin Hilman
-----Original Message----- From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ] Sent: Thursday, September 02, 2010 4:22 AM To: Gopi

 
134322724769_569560007727Kevin Hilman
On Fri, Sep 03, 2010 at 09:41:11AM -0700, Kevin Hilman wrote: Like you, Im no expert on the regulator framework internals, but it appears to have a pretty thorough system of constraints manageme

 
102128574494_529660007787Eduardo Valentin
On Fri, Sep 03, 2010 at 11:00:31AM -0700, Kevin Hilman wrote: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx writes: The only thing I can think you might need to do if this is just straig

 
125129274741_569760007136Mark Brown
On Mon, 2010-09-06 at 22:59 +0300, Eduardo Valentin wrote: Hello, On Fri, Sep 03, 2010 at 08:20:52PM +0200, Mark Brown wrote: On Fri, Sep 03, 2010 at 11:00:31AM -0700, Kevin Hilman wrote:

 
124424204653_551160007642Mark Brown
"Gopinath, Thara" <thara@xxxxxx writes: [...] I agree probably regulator framework would be the best place for this but then IMO regulator framework needs a lot of changes to s

 
177525264093_572760007616Thara Gopinath
This patch extends the device hwmod structure to contain info about the voltage domain to which the device belongs to. This is needed to support a device based DVFS where the device knows which volta

 
168220394888_545060007876Kevin Hilman
Thara Gopinath <thara@xxxxxx writes: This patch adds an API in the opp layer that can be used by the voltage layer to get a list of all the scalable devices belonging to a particular volta