[linux-sunxi] Raise DCDC1 Voltage on sun6i?
Hi Hans, Thanks for completing SPL support on the A31. I've managed to boot mainline U-boot on my Hummingbird A31. One issue I ran into is that with DCDC1 set at 3.0V, mmc0 is very unstable in the kernel. All operations timeout and the kernel panics because the rootfs isn't available. Raising the voltage to 3.3V gets rid of the problem, but I'm not sure that is the correct solution. Did you encounter something like this? I remember you sending a patch for u-boot-sunxi some time ago for something like this. Regards, ChenYu Tsai -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: Raise DCDC1 Voltage on sun6i?
Hi ChenYu, On 11/28/2014 10:20 AM, wens Tsai wrote: Hi Hans, Thanks for completing SPL support on the A31. I've managed to boot mainline U-boot on my Hummingbird A31. One issue I ran into is that with DCDC1 set at 3.0V, mmc0 is very unstable in the kernel. All operations timeout and the kernel panics because the rootfs isn't available. Raising the voltage to 3.3V gets rid of the problem, but I'm not sure that is the correct solution. The fex file for the mele boards says dcdc1 should be 3.3V not 3.0V and that makes sense really, since 3.3V is a standard voltage, while 3.0V is not. However the fex file for the Hummingbird says 3.0V and my Mele M9 works fine with the current u-boot setting of 3.0V. I've just booted my M9 into the original firmware and that is actually using 3.3V so changing things to 3.3V does seem to be the right thing. Maxime, I seem to remember you telling me that the Colombus is really using 3.0V. Maxime can you confirm this? Is that routed to the mmc power ? It could be that 3.0V is enough for the A31 itself, but that on boards which do not have a separate power-supply for the mmc 3.3V is used ? I'm fine with moving to 3.3V, I'm wondering if we should make it configurable like the DLDO# and ALDO# voltages, see drivers/power/Kconfig, with a 3.3V voltage and an override in the Colombus defconfig ? ChenYu, can you check which voltage the original firmware is actually using ? You should see boot1 printing the voltage, and you can check it from a root shell by doing: cat /sys/class/regulator/regulator.13/name cat /sys/class/regulator/regulator.13/microvolts (The first one is just to check your regulators are numbered the same). Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: [PATCH 0/5] sun6i: Add A31s (pinctrl) support
On Sun, Nov 23, 2014 at 1:54 PM, Hans de Goede hdego...@redhat.com wrote: I'm not sure if sunxi pinctrl patches go through Maxime's tree or Linus' tree, so I'll leave figuring out who takes what patches to you two. The changes in drivers/pinctrl and arch/* are usually orthogonal (just Kconfig symbols and DTS changes, no cross calls or header files that break compilation etc) and then they can be applied orthogonally. I just put the pinctrl patch in my tree and the rest in the platform tree. Yours, Linus Walleij -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: [PATCH 0/5] sun6i: Add A31s (pinctrl) support
Hi, On 11/28/2014 01:01 PM, Linus Walleij wrote: On Sun, Nov 23, 2014 at 1:54 PM, Hans de Goede hdego...@redhat.com wrote: I'm not sure if sunxi pinctrl patches go through Maxime's tree or Linus' tree, so I'll leave figuring out who takes what patches to you two. The changes in drivers/pinctrl and arch/* are usually orthogonal (just Kconfig symbols and DTS changes, no cross calls or header files that break compilation etc) and then they can be applied orthogonally. I just put the pinctrl patch in my tree and the rest in the platform tree. Ok, note in case it was not clear there will be a v2, so please do not merge v1. Thanks, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: [PATCH 3/9] clk: sunxi: Add prcm mod0 clock driver
Hi,
On 11/27/2014 08:05 PM, Maxime Ripard wrote:
Hi,
On Thu, Nov 27, 2014 at 11:10:51AM +0100, Hans de Goede wrote:
Hi,
On 11/27/2014 10:28 AM, Chen-Yu Tsai wrote:
Hi,
On Thu, Nov 27, 2014 at 4:41 PM, Hans de Goede hdego...@redhat.com wrote:
snip
I notice that you've not responded to my proposal to simple make the clock
node a child node of the clocks node in the dt, that should work nicely, and
avoid the need for any kernel level changes to support it, I'm beginning to
think that that is probably the best solution.
Would that not cause an overlap of the io regions, and cause one of them
to fail? AFAIK the OF subsystem doesn't like overlapping resources.
No the overlap check is done by the platform dev resource code, and
of_clk_declare
does not use that. So the overlap would be there, but not an issue (in theory
I did not test this).
An overlap is always an issue.
Thinking more about this, I believe that using the MFD framework for the prcm
seems
like a mistake to me. It gains us nothing, since we have no irq to de-multiplex
or
some such. We're not using MFD for the CMU, why use it for CMU2 (which the prcm
effectively is) ?
Because the PRCM is much more than that. It also handles the power
domains for example.
Ok, so thinking more about this, I'm still convinced that the MFD framework is
only
getting in the way here. But I can see having things represented in devicetree
properly, with the clocks, etc. as child nodes of the prcm being something which
we want.
So since all we are using the MFD for is to instantiate platform devices under
the prcm
nodes, and assign an io resource for the regs to them, why not simply make the
prcm node
itself a simple-bus.
This does everything the MFD prcm driver currently does, without actually
needing a specific
kernel driver, and as added bonus this will move the definition of the mfd
function reg offsets
out of the kernel and into the devicetree where they belong in the first place.
Please see the attached patches, I've tested this on sun6i, if we go this route
we should
make the same change on sun8i (I can make the change, but not test it).
Regards,
Hans
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
From 6756574293a1f291a8dcc29427b27f32f83acb2d Mon Sep 17 00:00:00 2001
From: Hans de Goede hdego...@redhat.com
Date: Fri, 28 Nov 2014 13:48:58 +0100
Subject: [PATCH v2 1/2] ARM: dts: sun6i: Change prcm node into a simple-bus
The prcm node's purpose is to group the various prcm sub-devices together,
it does not need any special handling beyond that, there is no need to
handle shared resources like a shared (multiplexed) interrupt or a shared
i2c bus.
As such there really is no need to have a separate compatible for it, using
simple-bus for it works fine. This also allows us to specify the register
offsets of the various child-devices directly into the dts, rather then having
to specify them in the OS implementation, putting the register offsets where
the belong.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun6i-a31.dtsi | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi
index 29e6438..4b8541f 100644
--- a/arch/arm/boot/dts/sun6i-a31.dtsi
+++ b/arch/arm/boot/dts/sun6i-a31.dtsi
@@ -846,11 +846,15 @@
};
prcm@01f01400 {
- compatible = allwinner,sun6i-a31-prcm;
+ compatible = simple-bus;
reg = 0x01f01400 0x200;
+ #address-cells = 1;
+ #size-cells = 1;
+ ranges;
ar100: ar100_clk {
compatible = allwinner,sun6i-a31-ar100-clk;
+reg = 0x01f01400 0x4;
#clock-cells = 0;
clocks = osc32k, osc24M, pll6, pll6;
clock-output-names = ar100;
@@ -867,6 +871,7 @@
apb0: apb0_clk {
compatible = allwinner,sun6i-a31-apb0-clk;
+reg = 0x01f0140c 0x4;
#clock-cells = 0;
clocks = ahb0;
clock-output-names = apb0;
@@ -874,6 +879,7 @@
apb0_gates: apb0_gates_clk {
compatible = allwinner,sun6i-a31-apb0-gates-clk;
+reg = 0x01f01428 0x4;
#clock-cells = 1;
clocks = apb0;
clock-output-names = apb0_pio, apb0_ir,
@@ -884,6 +890,7 @@
apb0_rst: apb0_rst {
compatible = allwinner,sun6i-a31-clock-reset;
+reg = 0x01f014b0 0x4;
#reset-cells = 1;
};
};
--
2.1.0
From a152b0405d446c748fef146915736e4a8fc548b1 Mon Sep 17 00:00:00 2001
From: Hans de Goede hdego...@redhat.com
Date: Fri, 28 Nov 2014 13:54:14 +0100
Subject: [PATCH v2 2/2] ARM: dts: sun6i: Add ir_clk node
Add an ir_clk sub-node to the prcm node.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun6i-a31.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi
[linux-sunxi] upgarde to kitkat allwinner a31s Q7S
Hi alls we have purchased 1000 tablets from china market the tablet is Allwinner A31s with Q7s board pls follow below link for more info http://eskychina.en.alibaba.com/product/1247008184-210516202/Cheap_Q7S_7_inch_Tablet_PC_Android_4_2_CPU_Allwinner_A31S_ARM_Cortex_A7_Quad_Core_Support_Wifi_3G.html the tablets has many problems such as battery drop, hang and crash many times, etc .. we think the current firmware has major problems so we have decided to upgrade to kitkat but the distributer does not support us we have only have a stock firmware with phoneixsuit tool so how we can port a kitkat version to current firmware ? pls help us BR -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
