| 119325254921_501460007952 | Gadiyar Anand |
|
|
|
|   |
| 157228924792_533660007467 | Felipe Balbi |
|
|
|
|   |
| 125522214630_580860007542 | Gadiyar Anand |
|
|
|
|   |
| 193721464511_592560007863 | Gadiyar Anand |
|
|
|
|   |
| 117824324306_592160007334 | Shilimkar 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 |
|
|   |
| 105528474859_597660007652 | Shubhrajyoti D |
|
|
|
|   |
| 192724334544_571960007991 | Kevin 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 |
|
|   |
| 118520244212_581560007063 | Varadarajan Charulat |
|
Thanks for the review
-----Original Message-----
From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ]
Sent: Thursday, August 26, 2010 |
|
|   |
| 135727694210_586860007946 | Murphy 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 |
|
|   |
| 173128724378_503660007031 | Marc Chalain |
|
|
|
|   |
| 137028484879_522960007740 | Robert Nelson |
|
|
|
|   |
| 188127504173_542560007943 | Robert 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 |
|
|   |
| 141526544968_562860007800 | Robert 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 |
|
|   |
| 169228264568_590260007261 | Keshava 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 |
|
|   |
| 184824234132_522560007925 | Keshava 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 |
|
|   |
| 125728314772_513660007594 | Keshava 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 |
|
|   |
| 187629424344_504860007813 | Munegowda 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 |
|
|   |
| 199227824466_595960007936 | Munegowda Keshava |
|
|
|
|   |
| 175921014761_532760007454 | Munegowda Keshava |
|
|
|
|   |
| 158828514878_572160007338 | Gadiyar Anand |
|
|
|
|   |
| 164623344169_541760007229 | Greg 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 |
|
|   |
| 101123454170_535560007536 | Hema 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 |
|
|   |
| 116823854317_563560007727 | Kalliguddi 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 |
|
|   |
| 157021034829_533160007833 | Kalliguddi Hema |
|
"Kalliguddi, Hema" <hemahk@xxxxxx writes:
static int musb_platform_resume(struct musb *musb)
{
u32 l;
+ struct device *dev = musb- controller;
+ struct |
|
|   |
| 178620184683_566360007760 | Kevin 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 |
|
|   |
| 100023854093_517060007564 | Hema 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 |
|
|   |
| 139928134910_556960007303 | Kalliguddi 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 |
|
|   |
| 110523374689_542360007033 | Kalliguddi Hema |
|
"Kalliguddi, Hema" <hemahk@xxxxxx writes:
-----Original Message-----
From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ] |
|
|   |
| 115025414136_598060007566 | Hema 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 |
|
|   |
| 181226584584_549460007323 | Hema 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 |
|
|   |
| 125423214708_534860007510 | Hema 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 |
|
|   |
| 191228914322_582160007491 | Kalliguddi 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 |
|
|   |
| 112425654828_581360007799 | Krogerus 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 |
|
|   |
| 184621384340_598260007213 | Heikki 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. |
|
|   |
| 154829294871_513260007191 | Heikki Krogerus |
|
|
|
|   |
| 145626784513_516360007004 | Thara 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 |
|
|   |
| 167329384896_599660007355 | Kevin 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 |
|
|   |
| 148728834921_531560007909 | Kevin 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 |
|
|   |
| 111425424047_545560007164 | Nishanth 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 |
|
|   |
| 166820714093_553960007517 | Nishanth 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 |
|
|   |
| 173126594194_524460007220 | Nishanth 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 |
|
|   |
| 124824964158_514360007917 | Kevin 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 |
|
|   |
| 149829804800_541960007495 | Kevin Hilman |
|
|
|
|   |
| 132724084036_537460007560 | Kevin Hilman |
|
-----Original Message-----
From: Kevin Hilman [ rel="nofollow" mailto:khilman@xxxxxxxxxxxxxxxxxxx mailto:khilman@xxxxxxxxxxxxxxxxxxx ]
Sent: Thursday, September 02, 2010 4:22 AM
To: Gopi |
|
|   |
| 153925314632_563260007836 | Kevin 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 |
|
|   |
| 114928004494_534460007317 | Eduardo 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 |
|
|   |
| 156522924814_572360007305 | Mark 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:
|
|
|   |
| 164029354284_543960007579 | Mark 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 |
|
|   |
| 193426804987_597160007850 | Thara 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 |
|
|   |
| 153125934380_516260007450 | Kevin 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 |
|
|   |