[linux-sunxi] Re: [PATCH v1] ARM:sunxi:sid: Make use of the of_match_ptr

2015-01-07 Thread Olliver Schinagl

Hey Arnd,
On 07-01-15 10:00, Arnd Bergmann wrote:

On Wednesday 07 January 2015 08:41:08 Olliver Schinagl wrote:

From: Olliver Schinagl oli...@schinagl.nl

I probably have forgotten to use this macro for the of_match pointer, so
this patch adds the of_match_ptr macro.

Signed-off-by: Olliver Schinagl oli...@schinagl.nl
---
  drivers/misc/eeprom/sunxi_sid.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/misc/eeprom/sunxi_sid.c b/drivers/misc/eeprom/sunxi_sid.c
index 8385177..5a330d9 100644
--- a/drivers/misc/eeprom/sunxi_sid.c
+++ b/drivers/misc/eeprom/sunxi_sid.c
@@ -25,6 +25,7 @@
  #include linux/kernel.h
  #include linux/kobject.h
  #include linux/module.h
+#include linux/of.h
  #include linux/of_device.h
  #include linux/platform_device.h
  #include linux/random.h
@@ -146,7 +147,7 @@ static struct platform_driver sunxi_sid_driver = {
 .remove = sunxi_sid_remove,
 .driver = {
 .name = DRV_NAME,
-   .of_match_table = sunxi_sid_of_match,
+   .of_match_table = of_match_ptr(sunxi_sid_of_match),
 },
  };
  module_platform_driver(sunxi_sid_driver);

This looks wrong: sunxi_sid_of_match is defined unconditionally, so
now you get a compiler warning if CONFIG_OF is disabled.

The existing code is good, we only add the of_match_ptr() for drivers
that are useful without CONFIG_OF and that want to save a few bytes
in .data size.
Ah, I missunderstood its use then!It looked like the of_match_ptr() got 
defined away otherwise. Sorry for the noise!


Olliver


Arnd


--
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 v1] ARM:sunxi:sid: Make use of the of_match_ptr

2015-01-07 Thread Maxime Ripard
Hi,

On Wed, Jan 07, 2015 at 08:41:08AM +0100, Olliver Schinagl wrote:
 From: Olliver Schinagl oli...@schinagl.nl
 
 I probably have forgotten to use this macro for the of_match pointer, so
 this patch adds the of_match_ptr macro.
 
 Signed-off-by: Olliver Schinagl oli...@schinagl.nl
 ---
  drivers/misc/eeprom/sunxi_sid.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)
 
 diff --git a/drivers/misc/eeprom/sunxi_sid.c b/drivers/misc/eeprom/sunxi_sid.c
 index 8385177..5a330d9 100644
 --- a/drivers/misc/eeprom/sunxi_sid.c
 +++ b/drivers/misc/eeprom/sunxi_sid.c
 @@ -25,6 +25,7 @@
  #include linux/kernel.h
  #include linux/kobject.h
  #include linux/module.h
 +#include linux/of.h
  #include linux/of_device.h
  #include linux/platform_device.h
  #include linux/random.h
 @@ -146,7 +147,7 @@ static struct platform_driver sunxi_sid_driver = {
   .remove = sunxi_sid_remove,
   .driver = {
   .name = DRV_NAME,
 - .of_match_table = sunxi_sid_of_match,
 + .of_match_table = of_match_ptr(sunxi_sid_of_match),

Why do you need this ? The sunxi_sid_of_match array is always defined.

Maxime

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


signature.asc
Description: Digital signature


Re: [linux-sunxi] Mainline work status

2015-01-07 Thread wens Tsai
Hi,

On Thu, Jan 8, 2015 at 6:21 AM, Iain Paton ipat...@gmail.com wrote:
 On 24/12/14 15:29, wens Tsai wrote:

 - AXP20x (PEK and docs) series, originally by Carlo, posted v8
 - AXP20x regulator driver cleanup, finished and tested
 - AXP221 support, originally by Boris, finished and tested
   * Also enables WiFi on the Hummingbird A31
 - sunxi (sun[457]i) cpufreq support, finished and testing (CB/CB2 tested)
   * Only added support for the boards I own. It's just a matter of adding
 the regulator nodes with the proper constraints

 Hi,

 I've been testing your patches with a20 olinuxino lime2  a10 lime

 I notice your cpu opp data reduces the voltage down to 0.9v for the lowest
 frequency, but all of the regulator nodes you added for cubieboard cubietruck
 etc, have the lower limit set to 1v.  Did you test 0.9v on anything?

Not before. The assumption was that we provide a generic set of OPPs.
Board files then decide which ones are actually usable via regulator
constraints.

 The lime2 dts currently has 0.7v as the lower limit for dcdc2 and when it's
 dropped to an opp with cpu core voltage set to 0.9v the board starts crashing
 randomly very soon after.

I just tested my cubieboard2, and it crashes as soon as the voltage
is lowered to 0.9v by cpufrequtils.

0.9v is below the recommended voltage range for VDD-CPU, according to
the datasheet. Running my board at 144 MHz / 1.0v seems fine though.

 I'll post a patch shortly to raise the lime2 dcdc2 lower limit to 1v, but
 I think it's probably worth collecting some more data on how many boards
 will really be able to use that 0.9v setting.

I can increase the voltage setting for 144 MHz to 1.0v in the dtsi.

This brings out additional problems though. The clock driver doesn't
support re-calculating the dividers ATM. So when the cpu clock is
at 144 MHz, the ahb clocks run at 24 MHz, which IIRC is too slow for
USB.

Maybe I just remove it from the OPP set for the time being.

 With the exception of altering the dcdc2 limits, I've not encountered any
 other problems.

Thanks for the feedback!

ChenYu

-- 
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: ARM: dts: sunxi: A20-OlinuXino-Lime2 raise dcdc2 lower voltage limit

2015-01-07 Thread wens Tsai
On Thu, Jan 8, 2015 at 6:21 AM, Iain Paton ipat...@gmail.com wrote:
 The Lime2 is not stable if the cpu core voltage is reduced below 1v. To
 prevent any problems when operating points are enabled, raise the pmic dcdc2
 lower voltage limit to 1v.

 Signed-off-by: Iain Paton ipat...@gmail.com
 ---

 Maxime, I realise the axp209 nodes will probably end up abstracted somewhat
 differently once all of the patches Chen-Yu posted are reviewed and picked
 up and I can redo the lime2 dts to fit once that's done.
 For now, the lime2 dts defines the full axp209 node itself including all of
 the regulators, so if the lowest opp with the 0.9v setting is enabled this
 will cause problems.

 Up to you if you want to take this patch now or we wait until the axp209.dtsi
 lands and refactor the lime2 dts appropriately then.

  arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

 diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts 
 b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
 index ed364d5..910318a 100644
 --- a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
 +++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
 @@ -159,7 +159,7 @@
 };

 vdd_cpu: dcdc2 {
 -   regulator-min-microvolt = 
 70;
 +   regulator-min-microvolt = 
 100;
 regulator-max-microvolt = 
 2275000;

You should lower the maximum voltage as well, either in this patch
or when you redo all the regulators. AFAIK the SoC certainly cannot
take up to 2.275V. The regulator nodes are supposed to say what
the board can handle.

ChenYu

 regulator-always-on;
 };
 --
 2.1.3


-- 
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/3] ARM: dts: sun8i: Add dts file for Ippo Q8H v1.2 tablets

2015-01-07 Thread Hans de Goede
The Ippo Q8H v1.2 is almost identical to the v5, still it needs a separate
dtb file since some gpio-s surrounding the wlan/bluetooth are different,
it uses different camera sensors, and different DRAM timings.

Note that atm neither the wlan/bluetooth nor the camera are supported, so
atm their is no difference between the dts files, but because of the different
DRAM timings there are already separate u-boot configs for the 2 different
versions, and the 1.2 config refers to sun8i-a23-ippo-q8h-v1.2.dtb to be
future proof, so we need to provide a sun8i-a23-ippo-q8h-v1.2.dtb file.

Signed-off-by: Hans de Goede hdego...@redhat.com
---
 arch/arm/boot/dts/Makefile|  3 +-
 arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts | 58 +++
 2 files changed, 60 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts

diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 4142831..7f66bab 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -478,7 +478,8 @@ dtb-$(CONFIG_MACH_SUN7I) += \
sun7i-a20-olinuxino-micro.dtb \
sun7i-a20-pcduino3.dtb
 dtb-$(CONFIG_MACH_SUN8I) += \
-   sun8i-a23-ippo-q8h-v5.dtb
+   sun8i-a23-ippo-q8h-v5.dtb \
+   sun8i-a23-ippo-q8h-v1.2.dtb
 dtb-$(CONFIG_MACH_SUN9I) += \
sun9i-a80-optimus.dtb
 dtb-$(CONFIG_ARCH_TEGRA) += tegra20-harmony.dtb \
diff --git a/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts 
b/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts
new file mode 100644
index 000..7056fc2
--- /dev/null
+++ b/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts
@@ -0,0 +1,58 @@
+/*
+ * 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.
+ */
+
+/*
+ * The Ippo Q8H v1.2 is almost identical to the v5, still it needs a separate
+ * dtb file since some gpio-s surrounding the wlan/bluetooth are different,
+ * and it uses different camera sensors.
+ */
+
+#include sun8i-a23-ippo-q8h-v5.dts
+
+/ {
+   model = Ippo Q8H Dual Core Tablet (v1.2);
+};
-- 
2.1.0

-- 
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/3] ARM: dts: sun7i: Add dts file for Bananapro board

2015-01-07 Thread Hans de Goede
Add support for the new Bananapro A20 development board from lemaker.org.
This board features 1G RAM, 2 USB A receptacles, 1 micro USB receptacle for
OTG, 1 micro USB receptacle for power, HDMI, sata, Gbit ethernet, ir receiver,
3.5 mm jack for a/v out, on board microphone, 40 gpio pins and sdio wifi.

Signed-off-by: Hans de Goede hdego...@redhat.com
---
 arch/arm/boot/dts/Makefile|   1 +
 arch/arm/boot/dts/sun7i-a20-bananapro.dts | 261 ++
 2 files changed, 262 insertions(+)
 create mode 100644 arch/arm/boot/dts/sun7i-a20-bananapro.dts

diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 548520f..4142831 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -467,6 +467,7 @@ dtb-$(CONFIG_MACH_SUN6I) += \
sun6i-a31s-cs908.dtb
 dtb-$(CONFIG_MACH_SUN7I) += \
sun7i-a20-bananapi.dtb \
+   sun7i-a20-bananapro.dtb \
sun7i-a20-cubieboard2.dtb \
sun7i-a20-cubietruck.dtb \
sun7i-a20-hummingbird.dtb \
diff --git a/arch/arm/boot/dts/sun7i-a20-bananapro.dts 
b/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new file mode 100644
index 000..3b4764d
--- /dev/null
+++ b/arch/arm/boot/dts/sun7i-a20-bananapro.dts
@@ -0,0 +1,261 @@
+/*
+ * 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/ sun7i-a20.dtsi
+/include/ sunxi-common-regulators.dtsi
+
+/ {
+   model = LeMaker Banana Pro;
+   compatible = lemaker,bananapro, allwinner,sun7i-a20;
+
+   soc@01c0 {
+   spi0: spi@01c05000 {
+   pinctrl-names = default;
+   pinctrl-0 = spi0_pins_a;
+   status = okay;
+   };
+
+   mmc0: mmc@01c0f000 {
+   pinctrl-names = default;
+   pinctrl-0 = mmc0_pins_a, mmc0_cd_pin_bananapi;
+   vmmc-supply = reg_vcc3v3;
+   bus-width = 4;
+   cd-gpios = pio 7 10 0; /* PH10 */
+   cd-inverted;
+   status = okay;
+   };
+
+   mmc3: mmc@01c12000 {
+   pinctrl-names = default;
+   pinctrl-0 = mmc3_pins_a;
+   vmmc-supply = reg_vmmc3;
+   bus-width = 4;
+   non-removable;
+   status = okay;
+   };
+
+   usbphy: phy@01c13400 {
+   usb1_vbus-supply = reg_usb1_vbus;
+   usb2_vbus-supply = reg_usb2_vbus;
+   status = okay;
+   };
+
+   ehci0: usb@01c14000 {
+   status = okay;
+   };
+
+   ohci0: usb@01c14400 {
+

[linux-sunxi] Re: [PATCH 1/1] ARM: sun4i: pcduino: Enable user LED and button support for pcDuino

2015-01-07 Thread Hans de Goede

Hi,

Looks good:

Acked-by: Hans de Goede hdego...@redhat.com

But you've send this to the wrong address, can you please resend this to
Maxime, with the arm and dts lists in Cc ?

Thanks,

Hans


On 07-01-15 13:16, Zoltan HERPAI wrote:

The pcDuino board has LEDs connected to PH15/PH16, and back/home/menu
buttons to PH17/18/19 respectively. Enable these via gpio-leds and
gpio-keys. This is shared across the v1 and v2 versions of the board.

Tested on a v2 and verified against the schematics of a v1.

Signed-off-by: Zoltan HERPAI wigy...@uid0.hu
---
  arch/arm/boot/dts/sun4i-a10-pcduino.dts |   57 +++
  1 file changed, 57 insertions(+)

diff --git a/arch/arm/boot/dts/sun4i-a10-pcduino.dts 
b/arch/arm/boot/dts/sun4i-a10-pcduino.dts
index 48161ad..c26a6bb 100644
--- a/arch/arm/boot/dts/sun4i-a10-pcduino.dts
+++ b/arch/arm/boot/dts/sun4i-a10-pcduino.dts
@@ -51,6 +51,8 @@
  #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 = LinkSprite pcDuino;
@@ -64,6 +66,22 @@
status = okay;
};

+   pinctrl@01c20800 {
+   led_pins_pcduino: led_pins@0 {
+   allwinner,pins = PH15, PH16;
+   allwinner,function = gpio_out;
+   allwinner,drive = SUN4I_PINCTRL_10_MA;
+   allwinner,pull = SUN4I_PINCTRL_NO_PULL;
+   };
+
+   key_pins_pcduino: key_pins@0 {
+   allwinner,pins = PH17, PH18, PH19;
+   allwinner,function = gpio_in;
+   allwinner,drive = SUN4I_PINCTRL_10_MA;
+   allwinner,pull = SUN4I_PINCTRL_NO_PULL;
+   };
+   };
+
mdio@01c0b080 {
status = okay;

@@ -126,6 +144,45 @@
};
};

+   leds {
+   compatible = gpio-leds;
+   pinctrl-names = default;
+   pinctrl-0 = led_pins_pcduino;
+
+   tx {
+   label = pcduino:green:tx;
+   gpios = pio 7 15 GPIO_ACTIVE_LOW;
+   };
+
+   rx {
+   label = pcduino:green:rx;
+   gpios = pio 7 16 GPIO_ACTIVE_LOW;
+   };
+   };
+
+   gpio_keys {
+   compatible = gpio-keys;
+   pinctrl-names = default;
+   pinctrl-0 = key_pins_pcduino;
+   #address-cells = 1;
+   #size-cells = 0;
+   button@0 {
+   label = Key Back;
+   linux,code = KEY_BACK;
+   gpios = pio 7 17 GPIO_ACTIVE_LOW;
+   };
+   button@1 {
+   label = Key Home;
+   linux,code = KEY_HOME;
+   gpios = pio 7 18 GPIO_ACTIVE_LOW;
+   };
+   button@2 {
+   label = Key Menu;
+   linux,code = KEY_MENU;
+   gpios = pio 7 19 GPIO_ACTIVE_LOW;
+   };
+   };
+
reg_usb1_vbus: usb1-vbus {
status = okay;
};



--
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 NAND] [PATCH 0/4] Add nand reading support to u-boot

2015-01-07 Thread Hans de Goede

Hi,

On 07-01-15 08:15, Daniel Kochmański wrote:

Hi,

Hans de Goede writes:


Hi,

On 06-01-15 12:57, Yassin Jaffer wrote:


Hi Hans

I was working on utilizing the DM framework for the nand driver, but this
is going to take sometime , anyway I will try to submit the driver based on
bbrezillon work.


Ok, thanks. I'm looking forward to the posting of the next version of your
series.


I'm quite happy if Daniel wants to pickup my work,


It looks to me like Daniel may have more time to work on this atm then you,
so that might be a good idea. Either way please coordinate with each other
to avoid double work. You can use private mail to Daniel for the coordination
stuff if you prefer, it would be nice if you could send a short summary of
who plans to do what once that is clear.


I'd be glad to, but I have limited time to devote for this project, and
I might me not be as that helpful as you expect me to.


   besides Daniel patches are for the SPL nand driver.

We should be able to use your adaption of Boris' work in the SPL too, for
mmc we are also using the same driver in both SPL and regular u-boot, and I
assume that Daniel's patches are also capable of loading say a kernel from
nand, right Daniel ?


I'm not sure if I remember correctly, but I had problems with adaptation
of lichee driver for nand, because it was too big to fit in SPL (BROM
expects boot0 to fit at first 8K).

Yes, these patches are capable of this. I haven't included patch which
added MBOOT functionality, since it seems unrelated to nand
support. Putting it short, it was downloading multiimage from mtd2
(which had 16M in my config), and extracted from it kernel, devicetree,
ramdisk and u-boot script which was performing boot.


Regards,

Hans




Regards

On Tuesday, January 6, 2015 12:08:48 AM UTC+11, Hans de Goede wrote:


Hi,

On 02-01-15 09:53, Daniel Kochmański wrote:

This is a series of patches to enable nand read functionality on sunxi
devices. It uses DMA and is able to read from syndrome partitions and
normal ones. Additionaly mksunxiboot tool is patched to be able to
format resulting binary to be able to read from BROM, so NAND SPL builds
are now possible. a20_nandread command is added for conveniance.

Afaik DMA controller doesn't vary between a10 and a20, so this should
work on a10 devices, but due to no a10 hardware it wasn't tested.


First of all many thanks for working on this!

I see that this is against linux-sunxi/u-boot-sunxi.git, that is not
(really) being actively developed anymore, see:


https://www.marshut.net/kuispp/linux-sunxi-u-boot-sunxi-is-no-longer-supported-time-to-switch-to-upstream-u-boot.html

Can you please rebase on top of upstream u-boot, on top of the next
branch:
http://git.denx.de/?p=u-boot/u-boot-sunxi.git;a=shortlog;h=refs/heads/next
?


I'll certainly do. In fact, it's done, but not tested yet.


Your patches all seem to only have a subject and not a proper commit
message,
please add a commit message to all of them describing the changes in
somewhat
more detail then you do in the subject, you could e.g. re-use bits of your
coverletter. Also for upstream u-boot we require a Signed-off-by as part
of the
commit message, so please add a line like this one to all your commit
messages:

Signed-off-by: Daniel Kochmański dkoch...@antmicro.com javascript:

You can make git do this automatically by specifying the -s option when
committing,
also please send further versions of this patch-set to the upstream u-boot
list.


Ok, thanks for the tip.


Besides all the above, which is easily fixed, unfortunately we also have
the problem
(or luxury) that Yassin Jaffer (added to the CC) has also been working on
nand support,
re-using the upstream kernel code Boris Brezillon has been working on,
see:

https://github.com/yassinjaffer/u-boot/commits/sunxi-nand


I wasn't aware of his work untill now. I'll give a closer look to it.


Great, I'm looking forward to seeing a new patchs-series from you, adding nand
support to u-boot would be great.

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] ARM: dts: sunxi: A20-OlinuXino-Lime2 raise dcdc2 lower voltage limit

2015-01-07 Thread Iain Paton
The Lime2 is not stable if the cpu core voltage is reduced below 1v. To
prevent any problems when operating points are enabled, raise the pmic dcdc2
lower voltage limit to 1v.

Signed-off-by: Iain Paton ipat...@gmail.com
---

Maxime, I realise the axp209 nodes will probably end up abstracted somewhat 
differently once all of the patches Chen-Yu posted are reviewed and picked
up and I can redo the lime2 dts to fit once that's done.
For now, the lime2 dts defines the full axp209 node itself including all of
the regulators, so if the lowest opp with the 0.9v setting is enabled this 
will cause problems.

Up to you if you want to take this patch now or we wait until the axp209.dtsi
lands and refactor the lime2 dts appropriately then.

 arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts 
b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
index ed364d5..910318a 100644
--- a/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
+++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts
@@ -159,7 +159,7 @@
};
 
vdd_cpu: dcdc2 {
-   regulator-min-microvolt = 
70;
+   regulator-min-microvolt = 
100;
regulator-max-microvolt = 
2275000;
regulator-always-on;
};
-- 
2.1.3

-- 
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: A10: How to power off LCD backlight without CONFIG_SUN4I_GPIO_UGLY?

2015-01-07 Thread Piotr Kopeć
Nie wiem czy to ci pomoże dopiero testuje :
sprawdz 4 punkt  Code lcd off and touchscreen
Link http://klanjin.cba.pl/?p=36

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