(2012年03月08日 22:18), Jean-Christophe PLAGNIOL-VILLARD wrote:
>> +static int __devexit anatop_regulator_remove(struct platform_device *pdev)
>> +{
>> +struct regulator_dev *rdev = platform_get_drvdata(pdev);
>> +struct anatop_regulator *sreg = rdev_get_drvdata(rdev);
>> +kfree(sreg->name
Hi Dmitry,
On Fri, Feb 24, 2012 at 4:23 PM, Dmitry Antipov
wrote:
> On 02/23/2012 04:57 AM, Ming Lei wrote:
>
>> No, it doesn't work with upstream kernel now. You need to apply the
>> patches[1][2]
>> against upstream kernel to route CTIs IRQ so that OMAP4 PMU/perf can work
>> well.
>>
>> [1], ht
Hi Richard,
On Fri, Mar 09, 2012 at 10:34:19AM +0800, Richard Zhao wrote:
> Hello Mike,
>
> The main interface for clk implementer is to register clocks dynamically.
> I think it highly depends on clk DT bindings. From the patch Grant sent
> out, it looks like he doesn't like one node per clk. So
Hi Grant,
On Friday 09 March 2012 11:12 AM, Grant Likely wrote:
On Thu, 23 Feb 2012 17:31:27 +0530, Rajendra Nayak wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree.
Signed-off-by: Rajendra Nayak
Good job Rob. Now you need to make sure that the branch you provided
is up to date with Linus's latest -rc (aka rebase your branch every
rc).
-- Forwarded message --
From: Stephen Rothwell
Date: Fri, Mar 9, 2012 at 8:40 AM
Subject: Re: [git pull] Consolidate cpuidle functionality
On Friday 09 March 2012 11:16 AM, Grant Likely wrote:
On Fri, 24 Feb 2012 10:49:00 -0800, Tony Lindgren wrote:
* Rajendra Nayak [120223 19:29]:
On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -113,5 +113,31 @@
On Wed, Mar 7, 2012 at 10:07 PM, Andrey Konovalov
wrote:
> Greetings,
>
> I've pushed the baseline for the 12.03 linux-linaro kernel tree to
> git://git.linaro.org/kernel/linux-linaro-tracking.git , linux-linaro branch.
>
> Currently this is v3.3-rc6 plus:
> - 4 topics from the ARM LT
> - few comm
Hi Paul,
On Friday 09 March 2012 12:21 PM, Paul Walmsley wrote:
On Thu, 8 Mar 2012, Grant Likely wrote:
Yes, absolutely use separate compatible values. It is always important
to be specific as to the silicon implementing the IP.
In that case, it is probably best to use the full chip name in
On Thu, 8 Mar 2012, Grant Likely wrote:
> Yes, absolutely use separate compatible values. It is always important
> to be specific as to the silicon implementing the IP.
In that case, it is probably best to use the full chip name in the
compatible string, e.g., omap2420 or omap2430 rather than j
On Wed, 7 Mar 2012, Turquette, Mike wrote:
> Assuming that some day OMAP code can be refactored to allow for lazy
> (or at least initcall-based) registration of clocks then perhaps your
> suggestion can take root. Which leads me to this question: are there
> any other platforms out there that requ
> + if (anatop_reg->control_reg) {
> + sel = (uv - anatop_reg->min_voltage) / 25000;
sel = DIV_ROUND_UP(uv - anatop_reg->min_voltage, 25000);
Use DIV_ROUND_UP to avoid the possible truncate of integer division.
This ensures the selected volatge falls within the specified range
Hello,
Once again Linaro will be having the the ARM Porting Jam, which will
happen during this friday. We had quite a good feedback and quite many
folks working on FTBFS related issues last Friday, but we still have a
long list to fix before the release.
If you're interested on helping fixing FTB
On 16:00 Fri 09 Mar , Ying-Chun Liu (PaulLiu) wrote:
> (2012年03月08日 22:18), Jean-Christophe PLAGNIOL-VILLARD wrote:
> >> +static int __devexit anatop_regulator_remove(struct platform_device *pdev)
> >> +{
> >> + struct regulator_dev *rdev = platform_get_drvdata(pdev);
> >> + struct anatop_reg
> --- a/drivers/regulator/Kconfig
> +++ b/drivers/regulator/Kconfig
> @@ -213,6 +213,14 @@ config REGULATOR_PCAP
> This driver provides support for the voltage regulators of the
> PCAP2 PMIC.
>
> +config REGULATOR_ANATOP
> + tristate "Freescale i.MX on-chip ANATOP LDO regulato
2012/3/9 Ying-Chun Liu (PaulLiu) :
> 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
> I'd say use the nonstatic ones. I think using the static initializers
> will cause us much pain in the future. I've been through several rebases
> on the i.MX clock rework and everytime I wish my sed foo would be
> better. Now imagine what happens when it turns out that the internal
> struct clk
Hi Rob,
On Thu, 8 Mar 2012 19:58:23 -0600 Rob Lee wrote:
>
> git://git.linaro.org/people/rob_lee/linux.git cpuidle_consol_pull
>
> These changes move various functionality duplicated in platform
> cpuidle drivers to the core cpuidle driver and common arch arm code. Also,
> the irq disabling in
Hello Stephen,
The following changes since commit 192cfd58774b4d17b2fe8bdc77d89c2ef4e0591d:
Linux 3.3-rc6 (2012-03-03 17:08:09 -0800)
are available in the git repository at:
git://git.linaro.org/people/rob_lee/linux.git cpuidle_consol_pull
Robert Lee (8):
cpuidle: Add common time keep
On Fri, Mar 09, 2012 at 10:58:34AM +0100, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> > I've modify the patch based on your review. However, the last one cannot
> > be made because regulator_unregister is void return.
> so we have a issue here regulator_unregister MUST return an error conde
The e
On Fri, Mar 09, 2012 at 03:57:09PM +0800, Ying-Chun Liu (PaulLiu) wrote:
> 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).
Hi
Today morning I've noticed that my beagle C4 is not working well.
This is the output a seen on serial:
(Also here: https://pastebin.linaro.org/424/)
40W
U-Boot SPL 2011.12 (Feb 16 2012 - 21:43:13)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
mmc_send_cmd: ti
W dniu 09.03.2012 13:41, Zygmunt Krynicki pisze:
Hi
Today morning I've noticed that my beagle C4 is not working well.
Update: it seems that SD card is working somewhat as without it U-Boot
does not load and none of the output is there. I'll try re-flashing that
card (brand new, used _once_)
Hi,
I am doing this on A9, echo mem >/sys/power/state is right, will trigger
kernel to sleep.
-jack
On 7 March 2012 23:05, yang gqyang wrote:
> dear all:
> I am working on arm cortex a8 now, trying to implement "suspend to ram"
> based on linux 3.0.8.
> Before i start my work, the soc already
On Wed, Mar 7, 2012 at 12:05 PM, yang gqyang wrote:
> dear all:
> I am working on arm cortex a8 now, trying to implement "suspend to ram"
> based on linux 3.0.8.
Which CPU exactly are you using?
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
h
On Thu, Jan 26, 2012 at 04:29:40PM +0800, Hui Zhang wrote:
> Thank you, Ricardo!
> By your experience,do you think xbmc can perform well on boards without
> hardware OpenGL ES acceleration?
I don't know if Ricardo answered, but unless XBMC has a non-composited
2D mode, I think it's unlikely. You'r
On Fri, 24 Feb 2012 15:56:52 +0530, Rajendra Nayak wrote:
> On Friday 24 February 2012 03:46 PM, T Krishnamoorthy, Balaji wrote:
> >> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> >> index 29f4589..9204f60 100644
> >> --- a/arch/arm/boot/dts/omap4.dtsi
> >> +++ b/arch/
On Thu, Mar 8, 2012 at 6:47 PM, Richard Earnshaw
wrote:
> On 08/03/12 17:21, Nicolas Pitre wrote:
>> On Thu, 8 Mar 2012, Richard Earnshaw wrote:
>>
>>> On 02/03/12 21:15, Nicolas Pitre wrote:
So, to me, the gcc documentation is perfectly clear on this topic.
there really _is_ a guarantee
On 02/29/12 21:15, Kukjin Kim wrote:
Tushar Behera wrote:
[...]
Acked-by: Jingoo Han
OK, I will apply this with Sylwester's 'reviewed-by' I looked at
before.
Thanks. Do you want me rebase this patch on your latest for-next and
resend?
Thanks but I can do it.
BTW, Tushar, what's the
On Fri, 9 Mar 2012, Dave Martin wrote:
> Register variables feel like a red herring though. We're only using
> those because we can't do the needful thing and actually desscribe
> these constraints in the asm constraints (which would seem to be the
> right place). We specifically don't care wher
On 09/03/12 16:20, Nicolas Pitre wrote:
> On Fri, 9 Mar 2012, Dave Martin wrote:
>
>> Register variables feel like a red herring though. We're only using
>> those because we can't do the needful thing and actually desscribe
>> these constraints in the asm constraints (which would seem to be the
>>
On Wed, Mar 7, 2012 at 10:27 PM, Andrew Lunn wrote:
>> Assuming that some day OMAP code can be refactored to allow for lazy
>> (or at least initcall-based) registration of clocks then perhaps your
>> suggestion can take root. Which leads me to this question: are there
>> any other platforms out t
On Thu, Mar 8, 2012 at 11:57 PM, Andrew Lunn wrote:
>> I'd say use the nonstatic ones. I think using the static initializers
>> will cause us much pain in the future. I've been through several rebases
>> on the i.MX clock rework and everytime I wish my sed foo would be
>> better. Now imagine what
On Thu, Mar 8, 2012 at 6:34 PM, Richard Zhao wrote:
> Hello Mike,
>
> The main interface for clk implementer is to register clocks dynamically.
> I think it highly depends on clk DT bindings. From the patch Grant sent
> out, it looks like he doesn't like one node per clk. So how do we
> register c
On Wed, Mar 7, 2012 at 1:20 PM, Sascha Hauer wrote:
> On Sat, Mar 03, 2012 at 12:29:01AM -0800, Mike Turquette wrote:
>> +struct clk *clk_register_divider(struct device *dev, const char *name,
>> + const char *parent_name, unsigned long flags,
>> + void __iomem *reg, u8 shi
On Mon, Mar 5, 2012 at 2:17 AM, Andrew Lunn wrote:
>> > I think i can wrap your simple gate clock, to make my "complex" gate
>> > clock. What would help is if you would EXPORT_SYMBOL_GPL
>> > clk_gate_enable() and clk_gate_disable(), since they do exactly what i
>> > want. I can then build my own
Signed-off-by: Mircea Gherzan
---
arch/arm/kernel/smp_twd.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
index 4464b87..b93e3ad 100644
--- a/arch/arm/kernel/smp_twd.c
+++ b/arch/arm/kernel/smp_twd.c
@@ -216,6 +2
Signed-off-by: Mircea Gherzan
---
drivers/thermal/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
index cea6ad0..55f057d 100644
--- a/drivers/thermal/Kconfig
+++ b/drivers/thermal/Kconfig
@@ -18,6 +18,7 @@ config T
Signed-off-by: Mircea Gherzan
---
arch/arm/mach-omap2/Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 0b7014d..e9991c9 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
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
The common clock framework defines a common struct clk as well as an
implementation of the clk api that unifies clock operations on various
platforms and devices.
The net result is consolidation of many different struct clk definitions
and platform-specific clock framework implementations.
Thanks
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
Signed-off-by: Mike Turquette
Cc: Russell King
Cc: Jeremy Kerr
Cc: Thomas Gleixner
Cc: Arnd Bergman
Cc: Paul Walmsley
Cc: Shawn Guo
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 clk definitions
and platform-specific clock framework implementa
Many platforms support simple gateable clocks, fixed-rate clocks,
adjustable divider clocks and multi-parent multiplexer clocks.
This patch introduces basic clock types for the above-mentioned hardware
which share some common characteristics.
Based on original work by Jeremy Kerr and contribution
43 matches
Mail list logo