From: "Ying-Chun Liu (PaulLiu)" <paul.liu(a)linaro.org>
Change "reg" to "anatop-reg-offset" due to there is a warning of handling no
size field in reg.
This patch also adds the missing device-tree binding documentation.
Signed-off-by: Ying-Chun Liu (PaulLiu) <paul.liu(a)linaro.org>
Cc: Shawn Guo <shawn.guo(a)linaro.org>
Cc: Mark Brown <broonie(a)opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg(a)ti.com>
---
.../bindings/regulator/anatop-regulator.txt | 29 ++++++++++++++++++++
drivers/regulator/anatop-regulator.c | 5 ++-
2 files changed, 32 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.txt
diff --git a/Documentation/devicetree/bindings/regulator/anatop-regulator.txt b/Documentation/devicetree/bindings/regulator/anatop-regulator.txt
new file mode 100644
index 0000000..357758c
--- /dev/null
+++ b/Documentation/devicetree/bindings/regulator/anatop-regulator.txt
@@ -0,0 +1,29 @@
+Anatop Voltage regulators
+
+Required properties:
+- compatible: Must be "fsl,anatop-regulator"
+- anatop-reg-offset: Anatop MFD register offset
+- anatop-vol-bit-shift: Bit shift for the register
+- anatop-vol-bit-width: Number of bits used in the register
+- anatop-min-bit-val: Minimum value of this register
+- anatop-min-voltage: Minimum voltage of this regulator
+- anatop-max-voltage: Maximum voltage of this regulator
+
+Any property defined as part of the core regulator
+binding, defined in regulator.txt, can also be used.
+
+Example:
+
+ regulator-vddpu {
+ compatible = "fsl,anatop-regulator";
+ regulator-name = "vddpu";
+ regulator-min-microvolt = <725000>;
+ regulator-max-microvolt = <1300000>;
+ regulator-always-on;
+ anatop-reg-offset = <0x140>;
+ anatop-vol-bit-shift = <9>;
+ anatop-vol-bit-width = <5>;
+ anatop-min-bit-val = <1>;
+ anatop-min-voltage = <725000>;
+ anatop-max-voltage = <1300000>;
+ };
diff --git a/drivers/regulator/anatop-regulator.c b/drivers/regulator/anatop-regulator.c
index 17499a5..53969af 100644
--- a/drivers/regulator/anatop-regulator.c
+++ b/drivers/regulator/anatop-regulator.c
@@ -138,9 +138,10 @@ static int __devinit anatop_regulator_probe(struct platform_device *pdev)
rdesc->type = REGULATOR_VOLTAGE;
rdesc->owner = THIS_MODULE;
sreg->mfd = anatopmfd;
- ret = of_property_read_u32(np, "reg", &sreg->control_reg);
+ ret = of_property_read_u32(np, "anatop-reg-offset",
+ &sreg->control_reg);
if (ret) {
- dev_err(dev, "no reg property set\n");
+ dev_err(dev, "no anatop-reg-offset property set\n");
goto anatop_probe_end;
}
ret = of_property_read_u32(np, "anatop-vol-bit-width",
--
1.7.9.1
Greetings,
The Linaro Kernel Working Group (KWG) and the Linaro Platform
Group are excited to announce the availability our March 2012
development snapshot:
linux-linaro-3.3-2012.03-2
As the word "snapshot" implies, these are meant as development kernels
and have not been fully validated. You should expect issues and to help
us deliver a better kernel in the future, please file bugs in Launchpad at
https://bugs.launchpad.net/linux-linaro.
The source tarball is available at:
https://launchpad.net/linux-linaro/devtrack/12.03/+download/linux-linaro-3.…
The kernel sources can also be accessed using git at:
git://git.linaro.org/kernel/linux-linaro-tracking.git
tag: linux-linaro-3.3-2012.03-2
This kernel includes the following changes from the 2012.02 kernel:
- Update to 3.3
- Various patches from Linaro
* Versatile Express patches from ARM LT
* Gator module for ARM's Streamline Performance Ananlyzer from ARM LT
* updated irq_domain patch set from Grant L.
* cpuidle core consolidation, cpuidle support for i.MX5/6 and ST-E
u8500 from PM WG
* updated patch set support for common save and restore code to the
Samsung exynos platform from PM WG
* updated thermal_cpu_cooling patch set from the power management WG
* UFS patches from kernel WG
* eMMC4.5 patches from kernel WG
* initial dma-buf patch set and some related components for UMM
- AOSP 3.3 android patch set
A full change log against the 3.3 release is available at:
https://launchpad.net/linux-linaro/devtrack/12.03
High Priority Known Issues:
- ANDROID_RAM_CONSOLE must be disabled for the android kernel to boot.
Dear linus.walleij,
I am sorry to trouble you. Would you mind give a hand?
I got a job that should log the RAM memory access in the QEMU. First, I
should find out the code line in QEMU to trap all RAM memory access. After
some efforts, I have some conclusions:
1. I have found the function dealing with the translation from the virtual
address to physical address in the guest of QEMU, such as
[target-arm/helper.c:get_phys_addr], and the page fault handler function
[target-arm/helper.c:cpu_arm_handle_mmu_fault]. However, we have not found
out the routine of accessing physical address from MMU TLB entry.
2. We have understood the relation of the guest physical address and host
virtual address, and found the function [exec.c:qemu_get_ram_ptr]
translating the guest physical address to host virtual address.
I am pressed for time. Would you mind to help me to check it? If you know
the location of the code lines or related messages, please tell me. Thank
you for your kindness. The QEMU I used getting from [*
http://lists.linaro.org/pipermail/linaro-announce/2012-February/000095.html*
].
Thanks,
Jerry Zhou
Hi,
Does anybody know if google-talkplugin has been ported to ARM? This
package is required to run Google Hangouts and there are proprietary
libraries in the plugin that appear to be compiled for x86 only. I
found some old references that these libraries might eventually be
ported to ARM and was just wondering if anybody had heard of this
work being done.
TIA,
Matt
Hi all!
The submission process for Linaro Connect Q2.12 plenaries is now open!
There will be 30 minutes of plenary talks daily from Tuesday through Friday
at Linaro Connect Q2.12 which is being held from 28 May - 1 June at the
Gold Coast Hotel in Hong Kong.
These plenary sessions will give Linaro Connect attendees an opportunity to
address Linaro, its current and potential Member and Partner
representatives as well as the community as a whole. These sessions are
broken up into two(2)-15 minute sessions for a total of eight (8) Plenary
Slots available for the Linaro Connect Q2.12 event.
Do you have a great idea you would like to present to the Linaro Connect
Q2.12 attendees? Want to share a Linaro success story and motivate,
inspire, excite or educate attendees? Then this is an opportunity for you
to get involved in this Linaro Connect event.
Plenary Submissions and suggested plenary sessions can be added to the
wiki<https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries>;
however, for your submission to be considered it needs to be emailed to David
Rusling, Linaro CTO <david.rusling(a)linaro.org>, and should include the
following information:
** Plenary Title:*
* * 3-5 Sentence abstract about what this talk will be about and how it is
connected to Linaro.*
* * Presenters Name, Company*
*The deadline for plenary submissions is 4 May 2012*. This way presenters
have time to finish their slide decks *prior* to arriving at Linaro Connect
Q2.12 and will allow event planners time for to finalized the schedule
ahead of time.
More information about the plenary sessions and the selection process can
be found on the
wiki<https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries>
[0].
Questions, comments or feedback concerning the plenary session maybe sent
to events(a)linaro.org or to David Rusling <david.rusling(a)linaro.org>.
[0] - https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries
--
Amber Graner
User Experience and Community Specialist
Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM SoCs*
***
Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> |
Twitter<http://twitter.com/#%21/linaroorg>
| Blog <http://www.linaro.org/linaro-blog/>
*+1.828.582.9469* cell
*+1.828.395.1049* office
irc: akgraner
amber.graner(a)linaro.org (email and Google chat)
If the state_count is not initialized for the device use
the driver's state count as the default. That will prevent
to add it manually in the cpuidle driver initialization
routine and will save us from duplicate line of code.
Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org>
---
drivers/cpuidle/cpuidle.c | 2 +-
drivers/cpuidle/driver.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
index 27f77a4..b8a1faf 100644
--- a/drivers/cpuidle/cpuidle.c
+++ b/drivers/cpuidle/cpuidle.c
@@ -268,7 +268,7 @@ int cpuidle_enable_device(struct cpuidle_device *dev)
if (!drv || !cpuidle_curr_governor)
return -EIO;
if (!dev->state_count)
- return -EINVAL;
+ dev->state_count = drv->state_count;
if (dev->registered == 0) {
ret = __cpuidle_register_device(dev);
diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
index 284d7af..40cd3f3 100644
--- a/drivers/cpuidle/driver.c
+++ b/drivers/cpuidle/driver.c
@@ -47,7 +47,7 @@ static void __cpuidle_register_driver(struct cpuidle_driver *drv)
*/
int cpuidle_register_driver(struct cpuidle_driver *drv)
{
- if (!drv)
+ if (!drv || !drv->state_count)
return -EINVAL;
if (cpuidle_disabled())
--
1.7.5.4
Hi,
I'm doing a project using OpenCV 2.3.1 and I want to embedded this on a
pandaboard. So I'm looking for someone who can help me to instal opencv on
Pandabord using Linaro Android 11.11 . If you have some link or if you can
advise me I would appreciate.
Thanks in advance.
Best Regards