Re: [linux-sunxi] Latest kernel does not find SD card

2017-11-23 Thread Chris Obbard 
hi guys,

had a bit of time to debug this tonight. here's my environment:

u-boot v2017.09 with lower-default-cpufreq-H5.path applied.

linux mainline, modules built-in, no ramdisk

it's like it doesn't find the SD card, for whatever reason.




[8.928343] VFS: Cannot open root device "mmcblk0p1" or
> unknown-block(0,0): error -6
> [8.936096] Please append a correct "root=" boot option; here are the
> available partitions:
> [8.944461] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> [8.952717] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.0-g5a787756b
> #1
> [8.959579] Hardware name: Xunlong Orange Pi PC 2 (DT)
> [8.964707] Call trace:
> [8.967161]  dump_backtrace+0x0/0x190
> [8.970820]  show_stack+0x14/0x20
> [8.974134]  dump_stack+0x9c/0xbc
> [8.977448]  panic+0x11c/0x290
> [8.980501]  mount_block_root+0x190/0x264
> [8.984505]  mount_root+0x11c/0x134
> [8.987989]  prepare_namespace+0x12c/0x174
> [8.992080]  kernel_init_freeable+0x200/0x224
> [8.996433]  kernel_init+0x10/0x100
> [8.19]  ret_from_fork+0x10/0x18
> [9.003493] SMP: stopping secondary CPUs
> [9.007411] Kernel Offset: disabled
> [9.010896] CPU features: 0x002004
> [9.014290] Memory Limit: none
> [9.017346] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(0,0)





On 21 November 2017 at 08:44, Chris Obbard  wrote:

> It is most likely the switch of the mmc regulators from a fixed one
>> to the AXP regulators.
>>
>> Please ensure you have the AXP mfd and regulator drivers built-in.
>> AFAIK the RSB variant of the AXP mfd driver does not support auto
>> loading of the module.
>
>
> I should have been more specific, I am using the Orange Pi PC2 which has
> a SY8106A regulator.  This is set to 1.1V by default without any comms from
> kernel.
>
> I am unsure as to why a regulator driver change would cause my SD card to
> not be found by the Kernel? On the Orange Pi PC2 the SD card is permanently
> wired to 3v3.
>
>
> Chris
>

-- 
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] [PATCH] arm64: allwinner: a64: Enable AXP803 for Orangepi Win

2017-11-23 Thread Jagan Teki 
Enable AXP803 PMIC and regulators for Orangepi Win.

Signed-off-by: Jagan Teki 
---
 .../boot/dts/allwinner/sun50i-a64-orangepi-win.dts | 125 +++--
 1 file changed, 117 insertions(+), 8 deletions(-)

diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts 
b/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts
index 5f8ff40..240d357 100644
--- a/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts
+++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts
@@ -57,13 +57,6 @@
chosen {
stdout-path = "serial0:115200n8";
};
-
-   reg_vcc3v3: vcc3v3 {
-   compatible = "regulator-fixed";
-   regulator-name = "vcc3v3";
-   regulator-min-microvolt = <330>;
-   regulator-max-microvolt = <330>;
-   };
 };
 
  {
@@ -73,7 +66,7 @@
  {
pinctrl-names = "default";
pinctrl-0 = <_pins>;
-   vmmc-supply = <_vcc3v3>;
+   vmmc-supply = <_dcdc1>;
cd-gpios = < 5 6 GPIO_ACTIVE_HIGH>;
cd-inverted;
status = "okay";
@@ -83,6 +76,122 @@
status = "okay";
 };
 
+_rsb {
+   status = "okay";
+
+   axp803: pmic@3a3 {
+   compatible = "x-powers,axp803";
+   reg = <0x3a3>;
+   interrupt-parent = <_intc>;
+   interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
+   };
+};
+
+#include "axp803.dtsi"
+
+_aldo1 {
+   regulator-always-on;
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "afvcc-csi";
+};
+
+_aldo2 {
+   regulator-always-on;
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "vcc-pl";
+};
+
+_aldo3 {
+   regulator-always-on;
+   regulator-min-microvolt = <300>;
+   regulator-max-microvolt = <300>;
+   regulator-name = "vcc-pll-avcc";
+};
+
+_dcdc1 {
+   regulator-always-on;
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "vcc-3v3";
+};
+
+_dcdc2 {
+   regulator-always-on;
+   regulator-min-microvolt = <104>;
+   regulator-max-microvolt = <130>;
+   regulator-name = "vdd-cpux";
+};
+
+/* DCDC3 is polyphased with DCDC2 */
+
+_dcdc5 {
+   regulator-always-on;
+   regulator-min-microvolt = <150>;
+   regulator-max-microvolt = <150>;
+   regulator-name = "vcc-dram";
+};
+
+_dcdc6 {
+   regulator-always-on;
+   regulator-min-microvolt = <110>;
+   regulator-max-microvolt = <110>;
+   regulator-name = "vdd-sys";
+};
+
+_dldo1 {
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "vcc-hdmi-dsi";
+};
+
+_dldo2 {
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "vcc-wifi";
+};
+
+_dldo3 {
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "avdd-csi";
+};
+
+_dldo4 {
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   regulator-name = "vcc-wifi-io";
+};
+
+_eldo1 {
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <180>;
+   regulator-name = "cpvdd";
+};
+
+_fldo1 {
+   regulator-min-microvolt = <120>;
+   regulator-max-microvolt = <120>;
+   regulator-name = "vcc-1v2-hsic";
+};
+
+/*
+ * The A64 chip cannot work without this regulator off, although
+ * it seems to be only driving the AR100 core.
+ * Maybe we don't still know well about CPUs domain.
+ */
+_fldo2 {
+   regulator-always-on;
+   regulator-min-microvolt = <110>;
+   regulator-max-microvolt = <110>;
+   regulator-name = "vdd-cpus";
+};
+
+_rtc_ldo {
+   regulator-name = "vcc-rtc";
+};
+
  {
pinctrl-names = "default";
pinctrl-0 = <_pins_a>;
-- 
2.7.4

-- 
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.