[linux-sunxi] Bare metal example for cubietruck

2016-10-12 Thread dlbp
Hello!
I'm using a cubietruck and because i Need to port an operating system from x86 
to ARM architecture, i need an example of bare metal software for a Cubietruck 
(with Cortex A-7). It's good also a simple hello world bare metal.

It is very important!

Thanks in advance

-- 
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 3/5] Input: add driver for Ilitek ili2139 touch IC

2016-10-12 Thread Hans de Goede

Hi,

On 10/11/2016 12:21 PM, Icenowy Zheng wrote:


2016年10月11日 下午5:37于 Hans de Goede 写道:


Hi,


I have a request: could you please test this driver on your E708 Q1? (According 
to the info you published on github, your E708 has also ili)


I'm afraid the touchscreen on my E708 Q1 is broken (does not even work in 
android),
so I cannot test this.





On 10/11/2016 02:33 AM, Icenowy Zheng wrote:

This driver adds support for Ilitek ili2139 touch IC, which is used in
several Colorfly tablets (for example, Colorfly E708 Q1, which is an
Allwinner A31s tablet with mainline kernel support).

Theortically it may support more Ilitek touch ICs, however, only ili2139
is used in any mainlined device.

It supports device tree enumeration, with screen resolution and axis
quirks configurable.

Signed-off-by: Icenowy Zheng 
---
  drivers/input/touchscreen/Kconfig   |  14 ++
  drivers/input/touchscreen/Makefile  |   1 +
  drivers/input/touchscreen/ili2139.c | 320 
  3 files changed, 335 insertions(+)
  create mode 100644 drivers/input/touchscreen/ili2139.c

diff --git a/drivers/input/touchscreen/Kconfig 
b/drivers/input/touchscreen/Kconfig
index 5079813..bb4d9d2 100644
--- a/drivers/input/touchscreen/Kconfig
+++ b/drivers/input/touchscreen/Kconfig
@@ -348,6 +348,20 @@ config TOUCHSCREEN_ILI210X
To compile this driver as a module, choose M here: the
module will be called ili210x.

+config TOUCHSCREEN_ILI2139
+ tristate "Ilitek ILI2139 based touchscreen"
+ depends on I2C
+ depends on OF
+ help
+   Say Y here if you have a ILI2139 based touchscreen
+   controller. Such kind of chipsets can be found in several
+   Colorfly tablets.
+
+   If unsure, say N.
+
+   To compile this driver as a module, choose M here; the
+   module will be called ili2139.
+
  config TOUCHSCREEN_IPROC
  tristate "IPROC touch panel driver support"
  depends on ARCH_BCM_IPROC || COMPILE_TEST
diff --git a/drivers/input/touchscreen/Makefile 
b/drivers/input/touchscreen/Makefile
index 81b8645..930b5e2 100644
--- a/drivers/input/touchscreen/Makefile
+++ b/drivers/input/touchscreen/Makefile
@@ -40,6 +40,7 @@ obj-$(CONFIG_TOUCHSCREEN_EGALAX_SERIAL) += egalax_ts_serial.o
  obj-$(CONFIG_TOUCHSCREEN_FUJITSU) += fujitsu_ts.o
  obj-$(CONFIG_TOUCHSCREEN_GOODIX) += goodix.o
  obj-$(CONFIG_TOUCHSCREEN_ILI210X) += ili210x.o
+obj-$(CONFIG_TOUCHSCREEN_ILI2139) += ili2139.o
  obj-$(CONFIG_TOUCHSCREEN_IMX6UL_TSC) += imx6ul_tsc.o
  obj-$(CONFIG_TOUCHSCREEN_INEXIO) += inexio.o
  obj-$(CONFIG_TOUCHSCREEN_INTEL_MID) += intel-mid-touch.o
diff --git a/drivers/input/touchscreen/ili2139.c 
b/drivers/input/touchscreen/ili2139.c
new file mode 100644
index 000..65c2dea
--- /dev/null
+++ b/drivers/input/touchscreen/ili2139.c
@@ -0,0 +1,320 @@
+/* -
+ * Copyright (C) 2016, Icenowy Zheng 
+ *
+ * Derived from:
+ *  ili210x.c
+ *  Copyright (C) Olivier Sobrie 
+ *
+ *  This program 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 program 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.
+ * -
+ */
+
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+
+#define DEFAULT_POLL_PERIOD 20
+
+#define MAX_TOUCHES 10
+#define COMPATIBLE_TOUCHES 2
+
+/* Touchscreen commands */
+#define REG_TOUCHDATA 0x10
+#define REG_TOUCHSUBDATA 0x11
+#define REG_PANEL_INFO 0x20
+#define REG_FIRMWARE_VERSION 0x40
+#define REG_PROTO_VERSION 0x42
+
+#define SUBDATA_STATUS_TOUCH_POINT 0x80
+#define SUBDATA_STATUS_RELEASE_POINT 0x00
+
+struct finger {
+ u8 x_low;
+ u8 x_high;
+ u8 y_low;
+ u8 y_high;
+} __packed;
+
+struct touchdata {
+ u8 length;
+ struct finger finger[COMPATIBLE_TOUCHES];
+} __packed;
+
+struct touch_subdata {
+ u8 status;
+ struct finger finger;
+} __packed;
+
+struct panel_info {
+ struct finger finger_max;
+ u8 xchannel_num;
+ u8 ychannel_num;
+} __packed;
+
+struct firmware_version {
+ u8 id;
+ u8 major;
+ u8 minor;
+} __packed;
+
+struct ili2139 {
+ struct i2c_client *client;
+ struct input_dev *input;
+ unsigned int poll_period;
+ struct delayed_work dwork;
+ struct touchscreen_properties prop;
+ int slots[MAX_TOUCHES];
+ int ids[MAX_TOUCHES];
+ struct input_mt_pos pos[MAX_TOUCHES];
+};
+
+static int ili2139_read_reg(struct i2c_client *client, u8 reg, void *buf,
+ size_t len)
+{
+ struct i2c_msg msg[2] = {
+ {
+ .addr = client->addr,
+ .flags = 0,
+ .len = 1,
+ .buf = ,
+ },
+ {
+ .addr 

Re: [linux-sunxi] Root file system for Linux-sunxi 3.4 on Cubietruck

2016-10-12 Thread dlbp
Thank you for the answer!!

So...should i modify file .fex to enable VGA??

Thank you

Il giorno mercoledì 12 ottobre 2016 13:59:09 UTC+2, Bastiaan van den Berg 
ha scritto:
>
> Enabling VGA is required before it will work.
>
> Check out https://linux-sunxi.org/Fex_Guide and 
> https://linux-sunxi.org/Display and https://linux-sunxi.org/Script.bin 
>
> And well, all the other pages on the wiki ;)
>
> As for root filesystem, you can use any with a proper ACL , so -not- Fat32 
> or NTFS , but most others are ok. Depends on which medium you are setting 
> it up really
>
>
> On Wed, Oct 12, 2016 at 1:50 PM, dlbp  > wrote:
>
>> Hello to everybody
>>
>> First of all, i'm using a micro SD and a Cubietruck.
>>
>> I have installed U-boot-2015.04 and linux-sunxi (from 
>> https://github.com/linux-sunxi/linux-sunxi )
>>
>> I have followed the guide available online and it boots.
>>
>> But when starting kernel, if i connect Cubietruck via VGA, i can't see 
>> anything. Otherwise, if i connect via UART, it works!!!
>>
>> What can be the solution??
>>
>> Another request: i need a target root file system as indicated in 
>> http://linux-sunxi.org/Linux_Kernel#Install
>> What root filesystem can i use?? 
>>
>> Thanks to 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...@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] Root file system for Linux-sunxi 3.4 on Cubietruck

2016-10-12 Thread Bastiaan van den Berg
Enabling VGA is required before it will work.

Check out https://linux-sunxi.org/Fex_Guide and
https://linux-sunxi.org/Display and https://linux-sunxi.org/Script.bin

And well, all the other pages on the wiki ;)

As for root filesystem, you can use any with a proper ACL , so -not- Fat32
or NTFS , but most others are ok. Depends on which medium you are setting
it up really


On Wed, Oct 12, 2016 at 1:50 PM, dlbp  wrote:

> Hello to everybody
>
> First of all, i'm using a micro SD and a Cubietruck.
>
> I have installed U-boot-2015.04 and linux-sunxi (from https://github.com/
> linux-sunxi/linux-sunxi )
>
> I have followed the guide available online and it boots.
>
> But when starting kernel, if i connect Cubietruck via VGA, i can't see
> anything. Otherwise, if i connect via UART, it works!!!
>
> What can be the solution??
>
> Another request: i need a target root file system as indicated in
> http://linux-sunxi.org/Linux_Kernel#Install
> What root filesystem can i use??
>
> Thanks to 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.
>

-- 
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] Root file system for Linux-sunxi 3.4 on Cubietruck

2016-10-12 Thread dlbp
Hello to everybody

First of all, i'm using a micro SD and a Cubietruck.

I have installed U-boot-2015.04 and linux-sunxi 
(from https://github.com/linux-sunxi/linux-sunxi )

I have followed the guide available online and it boots.

But when starting kernel, if i connect Cubietruck via VGA, i can't see 
anything. Otherwise, if i connect via UART, it works!!!

What can be the solution??

Another request: i need a target root file system as indicated 
in http://linux-sunxi.org/Linux_Kernel#Install
What root filesystem can i use?? 

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


[linux-sunxi] Re: [RFC 0/1] misc: Add Allwinner Q8 tablet hardware manager

2016-10-12 Thread Mark Rutland
Hi,

On Fri, Sep 09, 2016 at 04:32:06PM -0500, Rob Herring wrote:
> On Thu, Sep 1, 2016 at 2:08 PM, Hans de Goede  wrote:
> > Hi All,
> >
> > Here is a first RFC for the q8 tablet hw-manager I've been talking
> > about for a while now.
> >
> > The touchscreen part is finished, I'll start working on the
> > accelerometer bits next.
> 
> This at least partially overlaps with the "overlay manager" just
> posted. A dev board having different devices attached and a production
> device have 2nd source components are not really different problems.
> We need a common solution and can't have each platform making up their
> own scheme.

To follow up discussions at ELC-E, I agree that we need a common solution (if
this has to happen in the kernel rather than in an earlier stage of the boot
process).

Otherwise, we're creating pseudo-board-files, and a whole new set of problems
for ourselves.

Thanks
Mark.

-- 
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 2/5] pwm: sun4i: Add support for PWM controller on sun6i SoCs

2016-10-12 Thread Icenowy Zheng
Hi,

- 原件 -
> Hi,
> 
> On Wed, Oct 12, 2016 at 12:20 PM, Icenowy Zheng  wrote:
> > The PWM controller in A31 is different with other Allwinner SoCs, with
> > a control register per channel (in other SoCs the control register is
> > shared), and each channel are allocated 16 bytes of address (but only 8
> > bytes are used.). The register map in one channel is just like a
> > single-channel A10 PWM controller, however, A31 have a different
> > prescaler table than other SoCs.
> > 
> > In order to use the driver for all 4 channels, device nodes should be
> > created per channel.
> 
> I think Maxime wants you to support the different register offsets
> in this driver, and have all 4 channels in the same device (node).

I think that will make the code much more complex...
And in hardware there may also be 4 controllers... as the register is aligned 
at 0x10.

The error I made in my previous patch set is making
a dedicatded pwm-sun6i driver. So I reworked this.
(This also why I do not call the current patchset PATCH v2 -- it's a new 
patchset)

Icenowy Zheng

> 
> ChenYu
> 
> 
> > Signed-off-by: Icenowy Zheng 
> > ---
> > drivers/pwm/pwm-sun4i.c | 37 -
> > 1 file changed, 36 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
> > index 03a99a5..3e93bdf 100644
> > --- a/drivers/pwm/pwm-sun4i.c
> > +++ b/drivers/pwm/pwm-sun4i.c
> > @@ -46,7 +46,7 @@
> > 
> > #define BIT_CH(bit, chan)           ((bit) << ((chan) * PWMCH_OFFSET))
> > 
> > -static const u32 prescaler_table[] = {
> > +static const u32 prescaler_table_a10[] = {
> > 120,
> > 180,
> > 240,
> > @@ -65,10 +65,30 @@ static const u32 prescaler_table[] = {
> > 0, /* Actually 1 but tested separately */
> > };
> > 
> > +static const u32 prescaler_table_a31[] = {
> > +             1,
> > +             2,
> > +             4,
> > +             8,
> > +             16,
> > +             32,
> > +             64,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +             0,
> > +};
> > +
> > struct sun4i_pwm_data {
> > bool has_prescaler_bypass;
> > bool has_rdy;
> > unsigned int npwm;
> > +             const u32 *prescaler_table;
> > };
> > 
> > struct sun4i_pwm_chip {
> > @@ -100,6 +120,7 @@ static int sun4i_pwm_config(struct pwm_chip *chip,
> > struct pwm_device *pwm, int duty_ns, int period_ns)
> > {
> > struct sun4i_pwm_chip *sun4i_pwm = to_sun4i_pwm_chip(chip);
> > +             const u32 *prescaler_table = sun4i_pwm->data->prescaler_table;
> > u32 prd, dty, val, clk_gate;
> > u64 clk_rate, div = 0;
> > unsigned int prescaler = 0;
> > @@ -264,24 +285,35 @@ static const struct sun4i_pwm_data
> > sun4i_pwm_data_a10 = { .has_prescaler_bypass = false,
> > .has_rdy = false,
> > .npwm = 2,
> > +             .prescaler_table = prescaler_table_a10,
> > };
> > 
> > static const struct sun4i_pwm_data sun4i_pwm_data_a10s = {
> > .has_prescaler_bypass = true,
> > .has_rdy = true,
> > .npwm = 2,
> > +             .prescaler_table = prescaler_table_a10,
> > };
> > 
> > static const struct sun4i_pwm_data sun4i_pwm_data_a13 = {
> > .has_prescaler_bypass = true,
> > .has_rdy = true,
> > .npwm = 1,
> > +             .prescaler_table = prescaler_table_a10,
> > };
> > 
> > static const struct sun4i_pwm_data sun4i_pwm_data_a20 = {
> > .has_prescaler_bypass = true,
> > .has_rdy = true,
> > .npwm = 2,
> > +             .prescaler_table = prescaler_table_a10,
> > +};
> > +
> > +static const struct sun4i_pwm_data sun4i_pwm_data_a31 = {
> > +             .has_prescaler_bypass = false,
> > +             .has_rdy = true,
> > +             .npwm = 1,
> > +             .prescaler_table = prescaler_table_a31,
> > };
> > 
> > static const struct of_device_id sun4i_pwm_dt_ids[] = {
> > @@ -298,6 +330,9 @@ static const struct of_device_id
> > sun4i_pwm_dt_ids[] = { .compatible = "allwinner,sun7i-a20-pwm",
> > .data = _pwm_data_a20,
> > }, {
> > +                             .compatible = "allwinner,sun6i-a31-pwm",
> > +                             .data = _pwm_data_a31
> > +             }, {
> > /* sentinel */
> > },
> > };
> > --
> > 2.10.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.

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.

Re: [linux-sunxi] [PATCH 2/5] pwm: sun4i: Add support for PWM controller on sun6i SoCs

2016-10-12 Thread Chen-Yu Tsai
Hi,

On Wed, Oct 12, 2016 at 12:20 PM, Icenowy Zheng  wrote:
> The PWM controller in A31 is different with other Allwinner SoCs, with a
> control register per channel (in other SoCs the control register is
> shared), and each channel are allocated 16 bytes of address (but only 8
> bytes are used.). The register map in one channel is just like a
> single-channel A10 PWM controller, however, A31 have a different
> prescaler table than other SoCs.
>
> In order to use the driver for all 4 channels, device nodes should be
> created per channel.

I think Maxime wants you to support the different register offsets
in this driver, and have all 4 channels in the same device (node).

ChenYu


> Signed-off-by: Icenowy Zheng 
> ---
>  drivers/pwm/pwm-sun4i.c | 37 -
>  1 file changed, 36 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
> index 03a99a5..3e93bdf 100644
> --- a/drivers/pwm/pwm-sun4i.c
> +++ b/drivers/pwm/pwm-sun4i.c
> @@ -46,7 +46,7 @@
>
>  #define BIT_CH(bit, chan)  ((bit) << ((chan) * PWMCH_OFFSET))
>
> -static const u32 prescaler_table[] = {
> +static const u32 prescaler_table_a10[] = {
> 120,
> 180,
> 240,
> @@ -65,10 +65,30 @@ static const u32 prescaler_table[] = {
> 0, /* Actually 1 but tested separately */
>  };
>
> +static const u32 prescaler_table_a31[] = {
> +   1,
> +   2,
> +   4,
> +   8,
> +   16,
> +   32,
> +   64,
> +   0,
> +   0,
> +   0,
> +   0,
> +   0,
> +   0,
> +   0,
> +   0,
> +   0,
> +};
> +
>  struct sun4i_pwm_data {
> bool has_prescaler_bypass;
> bool has_rdy;
> unsigned int npwm;
> +   const u32 *prescaler_table;
>  };
>
>  struct sun4i_pwm_chip {
> @@ -100,6 +120,7 @@ static int sun4i_pwm_config(struct pwm_chip *chip, struct 
> pwm_device *pwm,
> int duty_ns, int period_ns)
>  {
> struct sun4i_pwm_chip *sun4i_pwm = to_sun4i_pwm_chip(chip);
> +   const u32 *prescaler_table = sun4i_pwm->data->prescaler_table;
> u32 prd, dty, val, clk_gate;
> u64 clk_rate, div = 0;
> unsigned int prescaler = 0;
> @@ -264,24 +285,35 @@ static const struct sun4i_pwm_data sun4i_pwm_data_a10 = 
> {
> .has_prescaler_bypass = false,
> .has_rdy = false,
> .npwm = 2,
> +   .prescaler_table = prescaler_table_a10,
>  };
>
>  static const struct sun4i_pwm_data sun4i_pwm_data_a10s = {
> .has_prescaler_bypass = true,
> .has_rdy = true,
> .npwm = 2,
> +   .prescaler_table = prescaler_table_a10,
>  };
>
>  static const struct sun4i_pwm_data sun4i_pwm_data_a13 = {
> .has_prescaler_bypass = true,
> .has_rdy = true,
> .npwm = 1,
> +   .prescaler_table = prescaler_table_a10,
>  };
>
>  static const struct sun4i_pwm_data sun4i_pwm_data_a20 = {
> .has_prescaler_bypass = true,
> .has_rdy = true,
> .npwm = 2,
> +   .prescaler_table = prescaler_table_a10,
> +};
> +
> +static const struct sun4i_pwm_data sun4i_pwm_data_a31 = {
> +   .has_prescaler_bypass = false,
> +   .has_rdy = true,
> +   .npwm = 1,
> +   .prescaler_table = prescaler_table_a31,
>  };
>
>  static const struct of_device_id sun4i_pwm_dt_ids[] = {
> @@ -298,6 +330,9 @@ static const struct of_device_id sun4i_pwm_dt_ids[] = {
> .compatible = "allwinner,sun7i-a20-pwm",
> .data = _pwm_data_a20,
> }, {
> +   .compatible = "allwinner,sun6i-a31-pwm",
> +   .data = _pwm_data_a31
> +   }, {
> /* sentinel */
> },
>  };
> --
> 2.10.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 4/5] ARM: dts: sun6i: add pinmux for PWM0

2016-10-12 Thread Chen-Yu Tsai
On Wed, Oct 12, 2016 at 12:20 PM, Icenowy Zheng  wrote:
> PWM0 is used by sun6i tablets as the backlight PWM.
>
> Add pinmux for it.
>
> Signed-off-by: Icenowy Zheng 
> ---
>  arch/arm/boot/dts/sun6i-a31.dtsi | 7 +++
>  1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi 
> b/arch/arm/boot/dts/sun6i-a31.dtsi
> index 97626ce..76f5a06 100644
> --- a/arch/arm/boot/dts/sun6i-a31.dtsi
> +++ b/arch/arm/boot/dts/sun6i-a31.dtsi
> @@ -494,6 +494,13 @@
> allwinner,pull = ;
> };
>
> +   pwm0_pins: pwm0@0 {
> +   allwinner,pins = "PH13";
> +   allwinner,function = "pwm0";
> +   allwinner,drive = ;
> +   allwinner,pull = ;

Maxime is updating the pinctrl bindings to use generic pinconf,
but otherwise this patch looks good.

ChenYu

> +   };
> +
> mmc0_pins_a: mmc0@0 {
> allwinner,pins = "PF0", "PF1", "PF2",
>  "PF3", "PF4", "PF5";
> --
> 2.10.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.