Exynos based SoC's have two different naming conventions.
One is S5PC_ and other is EXXX_. This patch adds
generic code to handle EXXX_ connvention.
Signed-off-by: Chander Kashyap
---
arch/arm/include/asm/arch-exynos/cpu.h |5 -
1 files changed, 4 insertions(+), 1 deletions(-
From: "Ying-Chun Liu (PaulLiu)"
Anatop is an integrated regulator inside i.MX6 SoC.
There are 3 digital regulators which controls PU, CORE (ARM), and SOC.
And 3 analog regulators which controls 1P1, 2P5, 3P0 (USB).
This patch adds the Anatop regulator driver.
Signed-off-by: Nancy Chen
Signed-of
On Mon, Mar 5, 2012 at 1:22 AM, Richard Zhao wrote:
> Hi Mike,
Hi Richard,
Sorry for missing this earlier. I've taken in most of your
suggestions and commented on some of them below. Any of your feedback
that I cut from this mail was taken in as a fix in v7 :-)
> On Sat, Mar 03, 2012 at 12:29
On Tue, Mar 13, 2012 at 4:24 AM, Sascha Hauer wrote:
> On Sat, Mar 03, 2012 at 12:29:00AM -0800, Mike Turquette wrote:
>> The common clock framework defines a common struct clk useful across
>> most platforms as well as an implementation of the clk api that drivers
>> can use safely for managing c
On Tue, Mar 13, 2012 at 2:48 PM, Rob Herring wrote:
> Mike,
>
> On 03/10/2012 01:54 AM, Mike Turquette wrote:
>> The common clock framework defines a common struct clk useful across
>> most platforms as well as an implementation of the clk api that drivers
>> can use safely for managing clocks.
>>
Mike,
On 03/10/2012 01:54 AM, Mike Turquette wrote:
> The common clock framework defines a common struct clk useful across
> most platforms as well as an implementation of the clk api that drivers
> can use safely for managing clocks.
>
> The net result is consolidation of many different struct c
On Mon, Mar 12, 2012 at 8:32 PM, Rajendra Nayak wrote:
> The series adds device tree support for OMAP hsmmc
> driver.
>
> Changes in V2:
> -1- Minor fixes based on comments from Grant.
> -2- Added a seperate compatible for omap3.
> -3- Added a new binding "ti,needs-special-reset"
> to handle some
hi yang,
在 2012年3月10日 下午10:37，yang gqyang 写道：
> Thanks for your comment.
> Finally, i find out that i made a mistake. The uart(8250) have not been
> restore after resume, instead, it use the configuration got from boot. The
> uart have not been restored correctly, so that "ls" can not output
Any update on below patch?
On Mon, 2012-02-06 at 18:16 +0530, Ashish Jangam wrote:
> DA9052/53 PMIC has capability to supply power for upto 3 banks of 6
> white serial LEDS. It can also control intensity of independent banks
> and to drive these banks boost converter will provide up to 24V and
> fo
Any update on below patch?
On Mon, 2012-02-06 at 18:18 +0530, Ashish Jangam wrote:
> This driver adds support for the watchdog functionality provided by the
> Dialog Semiconductor DA9052/53 PMIC chip.
>
> This patch is functionally tested on Samsung SMDKV6410.
>
> Signed-off-by: David Dajun Chen
Any update on the below patch
On Mon, 2012-02-06 at 18:21 +0530, Ashish Jangam wrote:
> This driver adds support for DA9052/53 4-wire resistive ADC interfaced
> touchscreen controller.
>
> DA9052/53 is a MFD therefore this driver depends on DA9052/53 core
> driver for core functionalities.
>
> Th
Hi Mike,
On Mon, Mar 12, 2012 at 08:16:36PM -0700, Turquette, Mike wrote:
> On Mon, Mar 12, 2012 at 4:51 AM, Sascha Hauer wrote:
> > On Sun, Mar 11, 2012 at 02:24:46PM -0700, Turquette, Mike wrote:
> >> On Sun, Mar 11, 2012 at 4:34 AM, Sascha Hauer
> >> wrote:
> >> > Hi Mike,
> >> >
> >> > I wa
On Tue, Mar 13, 2012 at 4:22 PM, Amit Kachhap wrote:
> Yes that should be helpful. Even the things your are suggesting are
> somewhat same with some patches submitted which sets cpufreq min/max
> constraint.
Hmm..let me see how soon can I code up a rough implementation!
Cheers!
--
-
Th
On Sat, Mar 03, 2012 at 12:29:00AM -0800, Mike Turquette wrote:
> The common clock framework defines a common struct clk useful across
> most platforms as well as an implementation of the clk api that drivers
> can use safely for managing clocks.
>
> The net result is consolidation of many differe
On 13 March 2012 15:44, Sundar wrote:
> On Tue, Mar 13, 2012 at 3:30 PM, Amit Kucheria
> wrote:
>> Sundar,
>
> Hi Amit,
>
>> At the moment it doesn't. But there was some discussion around
>> creating something that will work with devfreq. This would allow
>> peripheral drivers to be plugged in a
On Mon, Mar 12, 2012 at 10:50:09PM -0500, Matt Sealey wrote:
> Hi Mike,
>
> Can I suggest/we discuss that we support fractional (i.e. represented
> by fixed point value with integer and fractional part) dividers in the
> common divider clock case, simplistically just adding a divider
> fractional
On Tue, Mar 13, 2012 at 3:30 PM, Amit Kucheria wrote:
> Sundar,
Hi Amit,
> At the moment it doesn't. But there was some discussion around
> creating something that will work with devfreq. This would allow
> peripheral drivers to be plugged in as well. Amit is investigating
> that at present.
Wh
Hi Amit,
[snip.]
> >> +
> >> + kobject_uevent(&th_zone->therm_dev->device.kobj, KOBJ_CHANGE);
> >
> > Wouldn't it make more sense to pass the trip point id also as an 'env'
> > parameter ? This way, the user space can easily figure out which trip
> > point has been crossed.
> Its a good sugge
Sundar,
On Tue, Mar 13, 2012 at 11:45 AM, Sundar wrote:
> Hi Amit,
>
> Thanks for the replies. One more query
>
> On Tue, Mar 13, 2012 at 10:37 AM, Amit Kachhap
> wrote:
>
>>> "Different cpu related cooling devices": Do you mean cooling devices
>>> for different CPUs (num_cpus) or are you refer
Hi Amit,
Thanks for the replies. One more query
On Tue, Mar 13, 2012 at 10:37 AM, Amit Kachhap wrote:
>> "Different cpu related cooling devices": Do you mean cooling devices
>> for different CPUs (num_cpus) or are you referring to different
>> customers aka consumer drivers who could use this f
20 matches
Mail list logo
