[linux-sunxi] Re: [PATCH] ARM: sun7i: dt: Add new MK808C device
On 4 March 2015 at 21:34, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
On Tue, Mar 03, 2015 at 09:22:32PM +0100, Code Kipper wrote:
+
+/ {
+ model = mk808c;
+ compatible = mk808c, allwinner,sun7i-a20;
the compatible must be of the format vendor,device. Please add the
vendor name.
AhhhI've searched high and low for a vendors name. I listed it as
unknown on the wiki page,
would 'odm' be considered valid?
Not really. Another mk808c device might very well be made by some
other odm.
Hi Maxime,
I documented the device here at http://linux-sunxi.org/MK808C.
Don't your device has any brand on the case or the PCB?
There is nothing on the PCB to reference a manufacturer, the actual packaging
and case are from the earlier MK808B and mention A9. There was only a
small sticker on the side to show that the contents was a MK808C.
I guess 'unknown' isn't a valid vendor name,
Maxime
BR,
CK
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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: backporting A20-OLinuXino-LIME2 support to 3.16 kernel
Jens Thiele ka...@karme.de writes: just got: [12041.992438] usb 4-1: SerialNumber: [...] [12042.115080] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 18, RD RTO !! [12042.263156] sunxi-mmc 1c0f000.mmc: data error, sending stop command [12042.419970] sunxi-mmc 1c0f000.mmc: send stop command failed [12042.561641] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12042.703576] mmcblk0: error -110 sending status command, retrying [12042.853876] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12042.995393] mmcblk0: error -110 sending status command, retrying [12043.145709] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.287337] mmcblk0: error -110 sending status command, aborting [12043.437671] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.579375] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.721055] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.862702] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12044.004662] mmc0: card removed aeh - shame on me card removed yes, so it was - i accidently removed the card without noticing sorry, for the noise :( $ translate extrem peinlich extrem peinlich :: cringe-making -- 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: [U-Boot] Basic A33 support including dram init available in my personal repo
Hi, On 02-03-15 11:25, Hans de Goede wrote: Hi, On 01-03-15 19:42, Vishnu Patekar wrote: Allwinner A33 tablets comes with the libdram binary, fortunately I've found the libdram code at https://github.com/realthunder/a33_bootloader/tree/master/basic_loader/bsp/bsp_for_a67. Ah, that is both good and bad... I've integrated it with mainline u-boot, still lot to do to post it to upstream Integrated sounds as if you've copied pieces of code from the bsp code you've found into mainline u-boot. That is a big no no (this the bad part). AFAIK the bsp code does not come with a GPL license header, and Allwinner does not want to release these bits under the GPL for whatever reasons, a lot can be said about this, but in the end currently the bsp code is not GPL licensed, so we cannot use it / copy from it. There can be no discussion on this, when you're submitting this upstream you must not have any literal copied code in the patch you're sending upstream. You can use non copyrightable information from the bsp sources like register names and the initialization algorithm (IANAL), but you must 100% write your own code! Ok, so something (to me) quite unexpected has happened and Allwinner has just released what seems to be ALL there boot0 code under the GPL, it can found here: https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/boot0 https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/bsp Specifically interesting for the discussion at hand is: https://github.com/allwinner-zh/bootloader/blob/master/basic_loader/bsp/bsp_for_a33/init_dram/mctl_hal.c Which caries a GPL header now. This completely changes my story above, whatever you have (or had, sorry) was fine. It should still be cleaned up a bit, but all my worries about copy and pasting non GPL code are gone now. 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] [PATCH 2/7] ARM: dts: sun5i: Stop using different compatibles for ehci/ohci on a13 vs a10s
The A13 and the A10s use the same die (this has been confirmed by Allwinner),
as such there is no need to differentiate between the ehci/ohci parts of both,
the only reasons there were different allwinner,sun5i-a*-foo compatible
between these 2 parts is costemetically and because we could when we still
had 2 completely different dtsi files.
The allwinner,sun5i-a*-foo compatible strings are not used for binding at all,
the actual driver binds to the generic-?hci compatible, so we can safely remove
this cosmetical difference and simplify the dtsi files.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun5i-a10s.dtsi | 8
arch/arm/boot/dts/sun5i-a13.dtsi | 8
arch/arm/boot/dts/sun5i.dtsi | 2 ++
3 files changed, 2 insertions(+), 16 deletions(-)
diff --git a/arch/arm/boot/dts/sun5i-a10s.dtsi
b/arch/arm/boot/dts/sun5i-a10s.dtsi
index ef516db..a78c95d 100644
--- a/arch/arm/boot/dts/sun5i-a10s.dtsi
+++ b/arch/arm/boot/dts/sun5i-a10s.dtsi
@@ -157,14 +157,6 @@
};
};
-ehci0 {
- compatible = allwinner,sun5i-a10s-ehci, generic-ehci;
-};
-
-ohci0 {
- compatible = allwinner,sun5i-a10s-ohci, generic-ohci;
-};
-
pio {
compatible = allwinner,sun5i-a10s-pinctrl;
diff --git a/arch/arm/boot/dts/sun5i-a13.dtsi b/arch/arm/boot/dts/sun5i-a13.dtsi
index 5d9ce84..136158f 100644
--- a/arch/arm/boot/dts/sun5i-a13.dtsi
+++ b/arch/arm/boot/dts/sun5i-a13.dtsi
@@ -153,14 +153,6 @@
cooling-max-level = 6;
};
-ehci0 {
- compatible = allwinner,sun5i-a13-ehci, generic-ehci;
-};
-
-ohci0 {
- compatible = allwinner,sun5i-a13-ohci, generic-ohci;
-};
-
pio {
compatible = allwinner,sun5i-a13-pinctrl;
diff --git a/arch/arm/boot/dts/sun5i.dtsi b/arch/arm/boot/dts/sun5i.dtsi
index 610ea18..416c4de 100644
--- a/arch/arm/boot/dts/sun5i.dtsi
+++ b/arch/arm/boot/dts/sun5i.dtsi
@@ -392,6 +392,7 @@
};
ehci0: usb@01c14000 {
+ compatible = allwinner,sun5i-a13-ehci, generic-ehci;
reg = 0x01c14000 0x100;
interrupts = 39;
clocks = ahb_gates 1;
@@ -401,6 +402,7 @@
};
ohci0: usb@01c14400 {
+ compatible = allwinner,sun5i-a13-ohci, generic-ohci;
reg = 0x01c14400 0x100;
interrupts = 40;
clocks = usb_clk 6, ahb_gates 2;
--
2.3.1
--
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 4/7] ARM: dts: sun5i: Add new Auxtek-t004 board
The auxtek-t004:
http://www.fasttech.com/products/1110/10004200/1318603-auxtek-t004-allwinner-a10s-single-core-android-ics
Is an Allwinner A10s based hdmi tv stick with with 512M RAM, 4G nand flash,
toc9002 (bcm43362) sdio wifi, 1 USB host ports using an USB-A receptacle and
a 2 micro-usb receptacles, one for power and one for USB OTG.
The sdio wifi appears to not have an oob irq hooked up, so we rely on sdio-irq
support for it.
Signed-off-by: Hans de Goede hdego...@redhat.com
foo
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts | 151 +++
2 files changed, 152 insertions(+)
create mode 100644 arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index beac15f..d824336 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -525,6 +525,7 @@ dtb-$(CONFIG_MACH_SUN4I) += \
sun4i-a10-olinuxino-lime.dtb \
sun4i-a10-pcduino.dtb
dtb-$(CONFIG_MACH_SUN5I) += \
+ sun5i-a10s-auxtek-t004.dtb \
sun5i-a10s-mk802.dtb \
sun5i-a10s-olinuxino-micro.dtb \
sun5i-a10s-r7-tv-dongle.dtb \
diff --git a/arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts
b/arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts
new file mode 100644
index 000..6c6fef7
--- /dev/null
+++ b/arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts
@@ -0,0 +1,151 @@
+/*
+ * Copyright 2015 Hans de Goede hdego...@redhat.com
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
+ * a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This file is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public
+ * License along with this file; if not, write to the Free
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ *
+ * Or, alternatively,
+ *
+ * b) Permission is hereby granted, free of charge, to any person
+ * obtaining a copy of this software and associated documentation
+ * files (the Software), to deal in the Software without
+ * restriction, including without limitation the rights to use,
+ * copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following
+ * conditions:
+ *
+ * The above copyright notice and this permission notice shall be
+ * included in all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ */
+
+/dts-v1/;
+#include sun5i-a10s.dtsi
+#include sunxi-common-regulators.dtsi
+#include dt-bindings/gpio/gpio.h
+#include dt-bindings/pinctrl/sun4i-a10.h
+
+/ {
+ model = Auxtek t004 A10s hdmi tv-stick;
+ compatible = allwinner,auxtek-t004, allwinner,sun5i-a10s;
+
+ leds {
+ compatible = gpio-leds;
+ pinctrl-names = default;
+ pinctrl-0 = led_pins_t004;
+
+ red {
+ label = t004-tv-dongle:red:usr;
+ gpios = pio 1 2 GPIO_ACTIVE_HIGH; /* PB2 */
+ default-state = on;
+ };
+ };
+
+ reg_vmmc1: vmmc1 {
+ compatible = regulator-fixed;
+ pinctrl-names = default;
+ pinctrl-0 = mmc1_vcc_en_pin_t004;
+ regulator-name = vmmc1;
+ regulator-min-microvolt = 330;
+ regulator-max-microvolt = 330;
+ enable-active-high;
+ gpio = pio 1 18 GPIO_ACTIVE_HIGH; /* PB18 */
+ };
+};
+
+ehci0 {
+ status = okay;
+};
+
+mmc0 {
+ pinctrl-names = default;
+ pinctrl-0 = mmc0_pins_a, mmc0_cd_pin_t004;
+ vmmc-supply = reg_vcc3v3;
+ bus-width = 4;
+ cd-gpios = pio 6 1 GPIO_ACTIVE_HIGH; /* PG1 */
+
[linux-sunxi] [PATCH 5/7] ARM: dts: sun5i: Add new Utoo P66 board
The UTOO P66 is a 6 A13 tablet / lcd ereader. It features a 6 480x800 ips
lcd screen, 512MB RAM 4GB emmc.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/sun5i-a13-utoo-p66.dts | 203 +++
2 files changed, 205 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/sun5i-a13-utoo-p66.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index d824336..f97c5d3 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -531,7 +531,8 @@ dtb-$(CONFIG_MACH_SUN5I) += \
sun5i-a10s-r7-tv-dongle.dtb \
sun5i-a13-hsg-h702.dtb \
sun5i-a13-olinuxino.dtb \
- sun5i-a13-olinuxino-micro.dtb
+ sun5i-a13-olinuxino-micro.dtb \
+ sun5i-a13-utoo-p66.dtb
dtb-$(CONFIG_MACH_SUN6I) += \
sun6i-a31-app4-evb1.dtb \
sun6i-a31-colombus.dtb \
diff --git a/arch/arm/boot/dts/sun5i-a13-utoo-p66.dts
b/arch/arm/boot/dts/sun5i-a13-utoo-p66.dts
new file mode 100644
index 000..0f0a411
--- /dev/null
+++ b/arch/arm/boot/dts/sun5i-a13-utoo-p66.dts
@@ -0,0 +1,203 @@
+/*
+ * Copyright 2015 Hans de Goede hdego...@redhat.com
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
+ * a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This file is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public
+ * License along with this file; if not, write to the Free
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ *
+ * Or, alternatively,
+ *
+ * b) Permission is hereby granted, free of charge, to any person
+ * obtaining a copy of this software and associated documentation
+ * files (the Software), to deal in the Software without
+ * restriction, including without limitation the rights to use,
+ * copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following
+ * conditions:
+ *
+ * The above copyright notice and this permission notice shall be
+ * included in all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ */
+
+/dts-v1/;
+#include sun5i-a13.dtsi
+#include sunxi-common-regulators.dtsi
+#include dt-bindings/gpio/gpio.h
+#include dt-bindings/input/input.h
+#include dt-bindings/pinctrl/sun4i-a10.h
+
+/ {
+ model = Utoo P66;
+ compatible = utoo,p66, allwinner,sun5i-a13;
+
+ i2c_lcd: i2c@0 {
+ /* The lcd panel i2c interface is hooked up via gpios */
+ compatible = i2c-gpio;
+ pinctrl-names = default;
+ pinctrl-0 = i2c_lcd_pins;
+ gpios = pio 6 12 GPIO_ACTIVE_HIGH, /* PG12, sda */
+ pio 6 10 GPIO_ACTIVE_HIGH; /* PG10, scl */
+ i2c-gpio,delay-us = 5;
+ };
+};
+
+cpu0 {
+ cpu-supply = reg_dcdc2;
+};
+
+ehci0 {
+ status = okay;
+};
+
+i2c0 {
+ pinctrl-names = default;
+ pinctrl-0 = i2c0_pins_a;
+ status = okay;
+
+ axp209: pmic@34 {
+ reg = 0x34;
+ interrupts = 0;
+ };
+};
+
+#include axp209.dtsi
+
+i2c1 {
+ pinctrl-names = default;
+ pinctrl-0 = i2c1_pins_a;
+ status = okay;
+
+ pcf8563: rtc@51 {
+ compatible = nxp,pcf8563;
+ reg = 0x51;
+ };
+};
+
+lradc {
+ vref-supply = reg_ldo2;
+ status = okay;
+
+ button@200 {
+ label = Volume Up;
+ linux,code = KEY_VOLUMEUP;
+ channel = 0;
+ voltage = 20;
+ };
+
+ button@400 {
+ label = Volume Down;
+ linux,code = KEY_VOLUMEDOWN;
+ channel = 0;
+
[linux-sunxi] [PATCH 6/7] ARM: dts: sun7i: Add OOB irq support to boards with broadcom sdio wifi
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun7i-a20-cubietruck.dts | 11 +++
arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts | 11 +++
2 files changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
index 0c219a4..8111b0c 100644
--- a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
+++ b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
@@ -167,12 +167,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
+ interrupt-names = host-wake;
+ };
};
mmc3_pins_a {
diff --git a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
index baee563..4a8defd 100644
--- a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
+++ b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
@@ -164,12 +164,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
+ interrupt-names = host-wake;
+ };
};
mmc3_pins_a {
--
2.3.1
--
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 3/7] ARM: dts: sun5i: Add mmc2 pinmux settings
Add A13 mmc2 pinmux settings, note these are for a 8bit bus.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun5i.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i.dtsi b/arch/arm/boot/dts/sun5i.dtsi
index 416c4de..244d896 100644
--- a/arch/arm/boot/dts/sun5i.dtsi
+++ b/arch/arm/boot/dts/sun5i.dtsi
@@ -469,6 +469,15 @@
allwinner,drive = SUN4I_PINCTRL_30_MA;
allwinner,pull = SUN4I_PINCTRL_NO_PULL;
};
+
+ mmc2_pins_a: mmc2@0 {
+ allwinner,pins = PC6, PC7, PC8, PC9,
+ PC10, PC11, PC12, PC13,
+ PC14, PC15;
+ allwinner,function = mmc2;
+ allwinner,drive = SUN4I_PINCTRL_30_MA;
+ allwinner,pull = SUN4I_PINCTRL_PULL_UP;
+ };
};
timer@01c20c00 {
--
2.3.1
--
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 1/7] ARM: dts: sun4i: Enable tablet keys on Chuwi V7 CW0825
Enable the lradc controlled tablet keys on the Chuwi V7 CW0825 tablet.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts | 27 +
1 file changed, 27 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts
b/arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts
index 58214f2..97fca89 100644
--- a/arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts
+++ b/arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts
@@ -49,6 +49,7 @@
#include sun4i-a10.dtsi
#include sunxi-common-regulators.dtsi
#include dt-bindings/gpio/gpio.h
+#include dt-bindings/input/input.h
/ {
model = Chuwi V7 CW0825;
@@ -74,6 +75,32 @@
};
};
+lradc {
+ vref-supply = reg_vcc3v0;
+ status = okay;
+
+ button@800 {
+ label = Volume Up;
+ linux,code = KEY_VOLUMEUP;
+ channel = 0;
+ voltage = 80;
+ };
+
+ button@1000 {
+ label = Volume Down;
+ linux,code = KEY_VOLUMEDOWN;
+ channel = 0;
+ voltage = 100;
+ };
+
+ button@1200 {
+ label = Back;
+ linux,code = KEY_BACK;
+ channel = 0;
+ voltage = 120;
+ };
+};
+
mmc0 {
pinctrl-names = default;
pinctrl-0 = mmc0_pins_a, mmc0_cd_pin_reference_design;
--
2.3.1
--
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 7/7] ARM: dts: sun7i: Enable cap-sdio-irq for bananapro sdio wifi
The sdio wifi on the Banana Pro does not appear to have an oob irq hooked up, so enable sdio-irq support to avoid unnecessary polling. Signed-off-by: Hans de Goede hdego...@redhat.com --- arch/arm/boot/dts/sun7i-a20-bananapro.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/sun7i-a20-bananapro.dts b/arch/arm/boot/dts/sun7i-a20-bananapro.dts index fb89fe7..d0cd78f 100644 --- a/arch/arm/boot/dts/sun7i-a20-bananapro.dts +++ b/arch/arm/boot/dts/sun7i-a20-bananapro.dts @@ -164,6 +164,7 @@ vmmc-supply = reg_vmmc3; bus-width = 4; non-removable; + cap-sdio-irq; status = okay; }; -- 2.3.1 -- 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.
Re: [linux-sunxi] Backporting simplefb support to 3.16 kernel
Hi, On 06-03-15 17:02, Karsten Merker wrote: On Fri, Mar 06, 2015 at 04:40:52PM +0100, Jens Thiele wrote: just tested on A20‑OLinuXino‑LIME2 + LCD‑OLinuXino‑10TS prisirah@prisirah:~$ uname -a Linux prisirah 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) armv7l GNU/Linux and it works™ :-) [...] PS: it somehow feels a bit slower? (maybe just caused by different kernel config?!) do the DRAM clocks differ bettween 3.16 and 3.19? don't think so as u-boot sets them up? AFAIK the mainline kernel does not change the DRAM timing that is set up by u-boot, so changing the kernel version should not influence the DRAM timing in any way. Correct. 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: eGalax Driver for A20 (Banana/Orange Pi)
Ok, the driver named usbtouchscreen.ko works as well.
Need to be patched https://lkml.org/lkml/2007/3/24/54 to accept X-Y swap
and X invert, Y invert.
In this case, the ismod line must be called with arguments, for example
insmod /system/vendor/modules/usbtouchscreen.ko swap_xy invert_y
For the calibration
https://a20androidincar.wordpress.com/configuring-the-touchscreen/, same
thing: work into usbtouchscreen.c
static struct usbtouch_device_info usbtouch_dev_info[] = {
#ifdef CONFIG_TOUCHSCREEN_USB_EGALAX
[DEVTYPE_EGALAX] = {
.min_xc = 0x003e,
.max_xc = 0x079d,
.min_yc = 0x0069,
.max_yc = 0x0735,
.rept_size = 16,
.process_pkt = usbtouch_process_multi,
.get_pkt_len = egalax_get_pkt_len,
.read_data = egalax_read_data,
},
#endif
with the values x_min, x_max, y_min, y_max, found with this command in root:
getevent -l
and touching the 4 corners - Top Left, Top Right, Bottom Right, Bottom Left
The final step consit to create a file named Vendor__Product_.idc with
= your usb device Vendor
= your usb device Product
- cat /proc/bus/input/devices to find Vendor and Product
This .idc file must be in /system/usr/idc folder,
- or placed before build in
/ANDROID/android/out/target/product/sugar-lemaker/system/etc , with an
order to copy it in the file sugar_lemaker.mk file:
PRODUCT_COPY_FILES += \
[...]
device/softwinner/sugar-lemaker/Vendor_0eef_Product_0001.idc:
system/usr/idc/Vendor_0eef_Product_0001.idc
For multi touch, I work on this but I have found a link here
http://www.chalk-elec.com/?p=2028.
That's all !
--
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.
backporting A20-OLinuXino-LIME2 support to 3.16 kernel (Was: Re: [linux-sunxi] Backporting simplefb support to 3.16 kernel)
Jens Thiele ka...@karme.de writes: just tested on A20‑OLinuXino‑LIME2 + LCD‑OLinuXino‑10TS prisirah@prisirah:~$ uname -a Linux prisirah 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) armv7l GNU/Linux and it works™ :-) just got: [12041.992438] usb 4-1: SerialNumber: [...] [12042.115080] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 18, RD RTO !! [12042.263156] sunxi-mmc 1c0f000.mmc: data error, sending stop command [12042.419970] sunxi-mmc 1c0f000.mmc: send stop command failed [12042.561641] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12042.703576] mmcblk0: error -110 sending status command, retrying [12042.853876] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12042.995393] mmcblk0: error -110 sending status command, retrying [12043.145709] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.287337] mmcblk0: error -110 sending status command, aborting [12043.437671] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.579375] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.721055] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12043.862702] sunxi-mmc 1c0f000.mmc: smc 0 err, cmd 13, RTO !! [12044.004662] mmc0: card removed maybe sunxi-mmc needs some backporting, too? -- Prisirah - Building digital photo frames for family and friends using open-source hardware. http://karme.de/prisirah/ -- 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.
Re: [linux-sunxi] Re: [U-Boot] Basic A33 support including dram init available in my personal repo
On Sat, 07 Mar 2015 20:06:27 +0100 Hans de Goede hdego...@redhat.com wrote: Hi, On 02-03-15 11:25, Hans de Goede wrote: Hi, On 01-03-15 19:42, Vishnu Patekar wrote: Allwinner A33 tablets comes with the libdram binary, fortunately I've found the libdram code at https://github.com/realthunder/a33_bootloader/tree/master/basic_loader/bsp/bsp_for_a67. Ah, that is both good and bad... I've integrated it with mainline u-boot, still lot to do to post it to upstream Integrated sounds as if you've copied pieces of code from the bsp code you've found into mainline u-boot. That is a big no no (this the bad part). AFAIK the bsp code does not come with a GPL license header, and Allwinner does not want to release these bits under the GPL for whatever reasons, a lot can be said about this, but in the end currently the bsp code is not GPL licensed, so we cannot use it / copy from it. There can be no discussion on this, when you're submitting this upstream you must not have any literal copied code in the patch you're sending upstream. You can use non copyrightable information from the bsp sources like register names and the initialization algorithm (IANAL), but you must 100% write your own code! Ok, so something (to me) quite unexpected has happened and Allwinner has just released what seems to be ALL there boot0 code under the GPL, it can found here: https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/boot0 https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/bsp Specifically interesting for the discussion at hand is: https://github.com/allwinner-zh/bootloader/blob/master/basic_loader/bsp/bsp_for_a33/init_dram/mctl_hal.c Which caries a GPL header now. This completely changes my story above, whatever you have (or had, sorry) was fine. It should still be cleaned up a bit, but all my worries about copy and pasting non GPL code are gone now. It is strange that this has caught you by surprise, because you had been informed about what is going on: http://lists.denx.de/pipermail/u-boot/2015-March/207174.html Basically, we need to thank David and Vishnu for negotiating this with Allwinner (and this communication has been going on for some time already), which resulted in a reasonable solution in the end. You have also played your role well. My intervention was only needed to ensure that Vishnu does not get discouraged by your response, which originally sounded like only a single less than perfect solution was possible :-) Yes, we are kinda lucky to have discovered this apparently leaked A33 dram code. I don't approve the actions of whoever is responsible for this leak. But we ended up in a situation where the bad guys (competitors?) have already got access to the code to learn all the secrets, while the good guys (us) could not use the code because of the missing license notices. And Allwinner just made a rational decision how to deal with it (in the same way as this happened with the previous code leaks). Having also the A23, A83T and A80 dram code open sourced under the GPL license is very much appreciated. It means that U-Boot can get full support for A83T and A80 too. Special thanks to Vishu for not trying to hide the origin of the A33 dram code. I particularly like full transparency and honesty in handling this case. I'm still not completely happy about the presence of magic numbers all over the place (for example, Rockchip sources for very similar dram controllers have proper named identifiers for the hardware register bitfields) and other code quality problems. In a prefect world, we would also get full documentation for the dram controllers and the errata lists. But even the current source code is enough to move from the dead point. -- Best regards, Siarhei Siamashka -- 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.
Re: [linux-sunxi] Open source CedarX driver
On Sun, Mar 8, 2015 at 12:32 AM, Henrik Nordström hen...@henriknordstrom.net wrote: fre 2015-03-06 klockan 18:28 +0800 skrev Quink: cedarx2.0 is a refactoring of cedarx1.0. The job is finished about just three month ago and not used by most vendors yet. Some work is still needed to port cedarx2.0 to linux. The directory of cedarx2.0 in Android SDK is frameworks/av/media/liballwinner. The directory of cedarx1.0 in Android SDK is frameworks/av/media/CedarX-Projects. Most part of cedarx2.0 is open source. It's not the same situation compared with cedarx1.0. Maybe it is not a big step and not enough, it is a right direction. The latest cedarx code released by Allwinner is still non-GPL in the important parts, and no indications that this will change any time soon. Yes they have released much of the glue layers with GPL license, but the actual video encoding/decoding parts is till in a binary library which is incompatible with the GPL license terms. As an interim solution for the repo at https://github.com/allwinner-zh/media-codec (with the aim to keep the glue code as LGPL while the .so libraries as closed-source), would it make sense to split the repository into two parts? That is, have a https://github.com/allwinner-zh/media-codec-lib repository that will contain the two .so closed-source libraries. Then, the https://github.com/allwinner-zh/media-codec repository will include the media-codec-lib as a 'git submodule'. Simos -- 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.
Re: [linux-sunxi] Re: [U-Boot] Basic A33 support including dram init available in my personal repo
lör 2015-03-07 klockan 20:06 +0100 skrev Hans de Goede: Ok, so something (to me) quite unexpected has happened and Allwinner has just released what seems to be ALL there boot0 code under the GPL, it can found here: https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/boot0 https://github.com/allwinner-zh/bootloader/tree/master/basic_loader/bsp Excellent! Something good is clearly happening at Allwinner finally. Regards Henrik -- 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.
Re: [linux-sunxi] Open source CedarX driver
fre 2015-03-06 klockan 18:28 +0800 skrev Quink: cedarx2.0 is a refactoring of cedarx1.0. The job is finished about just three month ago and not used by most vendors yet. Some work is still needed to port cedarx2.0 to linux. The directory of cedarx2.0 in Android SDK is frameworks/av/media/liballwinner. The directory of cedarx1.0 in Android SDK is frameworks/av/media/CedarX-Projects. Most part of cedarx2.0 is open source. It's not the same situation compared with cedarx1.0. Maybe it is not a big step and not enough, it is a right direction. The latest cedarx code released by Allwinner is still non-GPL in the important parts, and no indications that this will change any time soon. Yes they have released much of the glue layers with GPL license, but the actual video encoding/decoding parts is till in a binary library which is incompatible with the GPL license terms. For open and Linux desktop portable drivers then please take a close look at the Cedrus open driver developed outside of Allwinner: http://linux-sunxi.org/Cedrus Please note that the security concerns mentioned in this project also applies to Allwinners code as it stems from the Allwinner kernel API and hardware capabilities, not the Cedrus code. Regards Henrik -- 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.
Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
fre 2015-03-06 klockan 19:44 + skrev Manuel Braga: The video engine is the least priority item in the wish list, but is dependent of all the others. I understand that, and also don't see a point of wasting time in a 100% open source driver and software for it, if the only way to use it requires hardware that is limited by binaries blobs (for example; dram initialization). This is not me going for a full 100% or nothing, just a question of priorities. A10, A13, A20 have full open source system code for a long long time, and these days even integrated in mainline u-boot kernel, including initialization from bare metal. Full DRAM setup etc. And now DRAM setup code and more for the whole range of SoCs have suddently been released as open source by Allwinner which removes a large part of the burden of getting the other SoCs supported at system level. The SoC user guides have also improved by far compared to the early A10 user guides we got access to years ago, plus are now officially published and not just randomly leaked. If you look at the openness then VPU and GPU is the most sore parts in the Allwinner SoCs at the moment. Not so much because they depend on everything else but because everything about them is closed down tightly by Allwinner. There is also some issues in display interfacing where there is relations to third party interest organisations and content protection. Please ignore what is in the Allwinner SDK releases and focus on what is available in open versions or documented. The silly fact that some later SDK releases have closed down some things which was open before do not make the already openly published versions closed, or that support for those have been dropped by linux-sunxi community kernel. Regards Henrik -- 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.
Re: [linux-sunxi] Open source CedarX driver
On Sat, 07 Mar 2015 23:32:51 +0100 Henrik Nordström hen...@henriknordstrom.net wrote: fre 2015-03-06 klockan 18:28 +0800 skrev Quink: cedarx2.0 is a refactoring of cedarx1.0. The job is finished about just three month ago and not used by most vendors yet. Some work is still needed to port cedarx2.0 to linux. The directory of cedarx2.0 in Android SDK is frameworks/av/media/liballwinner. The directory of cedarx1.0 in Android SDK is frameworks/av/media/CedarX-Projects. Most part of cedarx2.0 is open source. It's not the same situation compared with cedarx1.0. Maybe it is not a big step and not enough, it is a right direction. The latest cedarx code released by Allwinner is still non-GPL in the important parts, and no indications that this will change any time soon. Yes they have released much of the glue layers with GPL license, but the actual video encoding/decoding parts is till in a binary library which is incompatible with the GPL license terms. For open and Linux desktop portable drivers then please take a close look at the Cedrus open driver developed outside of Allwinner: http://linux-sunxi.org/Cedrus Please note that the security concerns mentioned in this project also applies to Allwinners code as it stems from the Allwinner kernel API and hardware capabilities, not the Cedrus code. Just to make it clear, we are talking about the LGPL license here, not GPL. This makes a rather major difference regarding the compliance requirements. -- Best regards, Siarhei Siamashka -- 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.
Re: [linux-sunxi] [PATCH 6/7] ARM: dts: sun7i: Add OOB irq support to boards with broadcom sdio wifi
Hi,
On Sun, Mar 8, 2015 at 3:01 AM, Hans de Goede hdego...@redhat.com wrote:
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun7i-a20-cubietruck.dts | 11 +++
arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts | 11 +++
2 files changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
index 0c219a4..8111b0c 100644
--- a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
+++ b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
@@ -167,12 +167,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
^ IRQ_TYPE_LEVEL_LOW?
+ interrupt-names = host-wake;
+ };
};
mmc3_pins_a {
diff --git a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
index baee563..4a8defd 100644
--- a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
+++ b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
@@ -164,12 +164,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
Same here.
ChenYu
+ interrupt-names = host-wake;
+ };
};
mmc3_pins_a {
--
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.
Re: [linux-sunxi] [UBOOT] Both Linux-Sunxi and Mainline Uboot have issues
Hi Tsvetan, On Thu, 19 Feb 2015 14:38:58 +0200 Siarhei Siamashka siarhei.siamas...@gmail.com wrote: On Wed, 18 Feb 2015 22:29:07 -0800 (PST) TsvetanUsunov tsvetanusu...@gmail.com wrote: Hi For A13-OLinuxino till now we conservatively used the Linux-Sunxi uboot, but we recently got new lot of Samsung memories and we decided to tweak some parameters for this DDR in Linux-Sunxi uboot and found problems. As this uboot is with status not maintained anymore I will not discuss the problems, as probably no one will spend time on it, This is actually very much interesting. What kind of problems you got after the change of DDR3 chips? My (probably somewhat limited) understanding is that all DDR3 chips have to support standard timings according to the JEDEC specs. There are several standard speed bins, so the faster chips just are tested for compatibility with a faster speed bin and labelled as such. BUT The magic Allwinner settings in u-boot make the DDR3 chips configuration violate the spec: http://lists.denx.de/pipermail/u-boot/2015-January/201787.html So I would not be very surprised if some of the chips can tolerate these settings and the others can't. If you can confirm that this is indeed the problem, then we might try to drop the problematic magic settings sooner. You can find a collection of DDR3 timing parameters for different clock speeds and JEDEC speed bins at: http://git.denx.de/?p=u-boot.git;a=blob;f=board/sunxi/dram_timings_sun4i.h;h=29b934da639c86b1830d1e26b7a751b6b227a21a;hb=HEAD The hardware documentation about the timing parameters is in the linux-sunxi wiki (no official documentation exists, but we took some efforts to collect the information about similar DRAM controllers used in Rockchip/TI SoCs from the Internet and verify that they actually apply to our hardware, mostly using the trial and error method of black box testing): http://linux-sunxi.org/A10_DRAM_Controller_Register_Guide#SDR_TPR0 http://linux-sunxi.org/A10_DRAM_Controller_Register_Guide#SDR_TPR1 http://linux-sunxi.org/A10_DRAM_Controller_Register_Guide#SDR_TPR2 Additionally, by tweaking the impedance matching configuration (using a brute force search and some heuristics), we can reach much higher DRAM clock speeds on various hardware. Some information about this is here: http://linux-sunxi.org/A10_DRAM_Controller_Calibration I know that Olimex has opted to just change the RZQ resistors nominal away from the standard 240 Ohm in different board revisions instead of tweaking the impedance via software. This introduces a practical problem for us on Olimex boards, which employ these tricks. It would be great if we could have a better cooperation with Olimex and maybe improve the DRAM configuration on Olimex boards to get better reliability and performance. Basically, we need to run certain tests on a statistically significant number of boards, preferably from different batches. I can help and answer questions. But most of the information is already available in the linux-sunxi wiki. so we wisely decided to move to mainline uboot :) but it seems there are other issues to address. That's a good choice :) BTW, the blog post https://olimex.wordpress.com/2014/10/27/a20-olinuxino-lime2-review-and-updates/ says that Much better routing of DDR3 memory. We increased the number of layers to 8 vs the 6 layers in LIME, we put the DDR3 memory closer to the A20, we layout the tracks shorter, as result now LIME2 runs with DDR3 on 532Mhz on LIME there were problems to run DDR3 at more than 400Mhz I'm very happy about the improved DRAM clock speed in LIME2. But if I understand this correctly, the old LIME is not expected to be reliable with the DRAM clocked higher than 400MHz? Are you now going to contribute updates for http://git.denx.de/?p=u-boot.git;a=blob;f=configs/A10-OLinuXino-Lime_defconfig;h=8fa1a330cd34e1a8202892595c549971b3275169;hb=HEAD http://git.denx.de/?p=u-boot.git;a=blob;f=configs/A20-OLinuXino-Lime_defconfig;h=5442f645f87165c34bbed8ba3e6cde3d8a8b87e8;hb=HEAD to pick a more reasonable DRAM clock speed? Or do you see no problems having it configured as 480MHz in the mainline u-boot for A10-OLinuXino-Lime and A20-OLinuXino-Lime? This is just a reminder to say that I'm still very much interested to get a reply. You seem to be assuming that nobody here (and in the upstream U-Boot) is interested in the DRAM settings used on Olimex boards, but this is not quite true. The wiki page at https://www.olimex.com/wiki/A13-OLinuXino now says: Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. Previously we used HYNIX H5TQ2G83CFR, now we use SAMSUNG K4B2G0846Q. Newest official Debian release (recommended):
Re: [linux-sunxi] [PATCH 6/7] ARM: dts: sun7i: Add OOB irq support to boards with broadcom sdio wifi
On Sun, Mar 8, 2015 at 3:01 AM, Hans de Goede hdego...@redhat.com wrote:
Signed-off-by: Hans de Goede hdego...@redhat.com
---
arch/arm/boot/dts/sun7i-a20-cubietruck.dts | 11 +++
arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts | 11 +++
2 files changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
index 0c219a4..8111b0c 100644
--- a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
+++ b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
@@ -167,12 +167,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
+ interrupt-names = host-wake;
+ };
I gave this a spin on my Cubietruck. (I was running cap-sdio-irq before.)
Ran a few ping tests with a simple
sudo ping -i 0.1 -I wlan0 -s 65500 192.168.1.1
After a few runs I got
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD SBE !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110
brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x0a040, err: -5
brcmfmac: brcmf_sdio_hdparse: seq 226: sequence number error, expect 227
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD DTO !!
sunxi-mmc 1c12000.mmc: data error, sending stop command
The chip is pretty much dead afterwards.
With cap-sdio-irq it doesn't happen so soon, but it does.
Without either, the response time is bad with packet losses,
but at least it doesn't die.
Is this the problem Arend (CC-ed) was looking into?
Regards
ChenYu
};
mmc3_pins_a {
diff --git a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
index baee563..4a8defd 100644
--- a/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
+++ b/arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts
@@ -164,12 +164,23 @@
};
mmc3 {
+ #address-cells = 1;
+ #size-cells = 0;
+
pinctrl-names = default;
pinctrl-0 = mmc3_pins_a;
vmmc-supply = reg_vmmc3;
bus-width = 4;
non-removable;
status = okay;
+
+ brcmf: bcrmf@1 {
+ reg = 1;
+ compatible = brcm,bcm4329-fmac;
+ interrupt-parent = pio;
+ interrupts = 10 8; /* PH10 / EINT10 */
+ interrupt-names = host-wake;
+ };
};
mmc3_pins_a {
--
2.3.1
--
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.
--
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.
Re: [linux-sunxi] [PATCH 7/7] ARM: dts: sun7i: Enable cap-sdio-irq for bananapro sdio wifi
On Sun, Mar 8, 2015 at 3:01 AM, Hans de Goede hdego...@redhat.com wrote: The sdio wifi on the Banana Pro does not appear to have an oob irq hooked up, so enable sdio-irq support to avoid unnecessary polling. I wonder if this is stable enough to put back into the mmc driver, i.e. declare the capability in the driver itself? IIRC at one point it did. ChenYu Signed-off-by: Hans de Goede hdego...@redhat.com --- arch/arm/boot/dts/sun7i-a20-bananapro.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/sun7i-a20-bananapro.dts b/arch/arm/boot/dts/sun7i-a20-bananapro.dts index fb89fe7..d0cd78f 100644 --- a/arch/arm/boot/dts/sun7i-a20-bananapro.dts +++ b/arch/arm/boot/dts/sun7i-a20-bananapro.dts @@ -164,6 +164,7 @@ vmmc-supply = reg_vmmc3; bus-width = 4; non-removable; + cap-sdio-irq; status = okay; }; -- 2.3.1 -- 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.
