Same deal. New hardware, working on bringup. It's currently running a slightly
ancient android.
>From
>http://linux-sunxi.org/Retrieving_device_information#Retrieving_data_over_USB_in_FEL_mode
> ./fel read 0x4300 0x2 script.bin
works fine.
> ./bin2fex script.bin script.fex
segfaults.
Hi,
On 01/06/2014 08:16 AM, Arnd Bergmann wrote:
On Monday 06 January 2014, Hans de Goede wrote:
+Required properties:
+ - compatible: Should be "platform-ohci"
+ - reg: Address range of the ohci registers.
+ - interrupts: Should contain the ohci interrupt.
+
+Optional properties:
+ - clocks: a
On Monday 06 January 2014, Hans de Goede wrote:
> +Required properties:
> + - compatible: Should be "platform-ohci"
> + - reg: Address range of the ohci registers.
> + - interrupts: Should contain the ohci interrupt.
> +
> +Optional properties:
> + - clocks: array of clocks
> + - clock-names: clock
Hi
For i2cdetect i,e is not an error.
just find that line in kernel by grep, and comment it.
you will see only i2c bus address.
Regards
Punith
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving
Some factor clocks, such as the parent clock of pll5 and pll6, have
multiple output names. Use the last name as the name for the clock
itself.
Signed-off-by: Chen-Yu Tsai
---
drivers/clk/sunxi/clk-sunxi.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/driv
Device tree naming conventions state that node names should match
node function. Change fully functioning clock nodes to match.
Also add the output name for pll5 to use as the clock name.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun4i-a10.dtsi | 26 +++---
1 file ch
Device tree naming conventions state that node names should match
node function. Change fully functioning clock nodes to match.
Also add the output name for pll5 to use as the clock name.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun5i-a10s.dtsi | 26 +++---
arch/arm
sunxi clock drivers use dt node name as clock name, but clock
nodes should be named clk@X, so the names would be the same.
Let the drivers read clock names from dt clock-output-names
property.
Signed-off-by: Chen-Yu Tsai
---
drivers/clk/sunxi/clk-sunxi.c | 6 ++
1 file changed, 6 insertions(
This is v2 of the clock node renaming patch series, which renames
the clock nodes in sunxi dts to conform to device tree naming
conventions, i.e. clk@N. Dummy clocks that will be renamed/removed
later, or clocks sharing registers are not renamed.
Renamed clock nodes have clock-output-names propert
Divs clocks consist of a parent factor clock with multiple outputs,
and seperate clocks for each output. Get the name of the parent
clock from the parent factor clock, instead of the DT node name.
Signed-off-by: Chen-Yu Tsai
---
drivers/clk/sunxi/clk-sunxi.c | 3 ++-
1 file changed, 2 insertions
The Cubietruck makes use of the first three i2c controllers found on the
Allwinner A20; i2c-0 is used internally for the PMIC, i2c-1 is exposed on
the board headers, and i2c-2 is used for DDC on the VGA connector. This
patch enables them in the device tree.
Signed-off-by: Chen-Yu Tsai
---
arch/a
Device tree naming conventions state that node names should match
node function. Change fully functioning clock nodes to match.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun6i-a31.dtsi | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/sun6
Device tree naming conventions state that node names should match
node function. Change fully functioning clock nodes to match.
Also add the output name for pll5 to use as the clock name.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun7i-a20.dtsi | 21 -
1 file changed
Hi
i am using A20 eval board.
i need to know what are configuration need to done for Ethernet in script
as well as in android file system,
so that i will make it work.
what about MAC address?
Kindly tell me.
Regards
Punith
--
You received this message because you are subscribed to the Goo
An on a different note, not to make things more difficult: the cpufrequtils
package from ubuntu (at least this version: cpufrequtils_008-1_armhf.deb)
installs an init.d startup file called cpufrequtils that sets the default
governor to... you guessed it -- ondemand. This is easily overridden by
On Mon, 6 Jan 2014 06:39:38 +0600
Roman Mamedov wrote:
> On Mon, 6 Jan 2014 00:00:00 +0200
> Siarhei Siamashka wrote:
>
> > A better solution is to really ramp up the CPU to the maximum clock
> > speed if we have some external power source connected (ACIN or VBUS).
> > Adhering to the "principl
On Mon, 6 Jan 2014 00:07:02 +0100
Carlo Caione wrote:
> On Mon, Jan 6, 2014 at 12:04 AM, Olliver Schinagl wrote:
> > On 01/05/14 23:00, Siarhei Siamashka wrote:
> >>
> >> # cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20_regs
> >> only power adapter : REG[0x0]=0xc1,REG[0x1]=0x
On Sun, 5 Jan 2014 23:25:29 +0100
Michal Suchanek wrote:
> On 5 January 2014 23:00, Siarhei Siamashka
> wrote:
> > === cubietruck ===
> >
> > # echo 1 > /sys/devices/platform/disp/graphics/fb0/blank
> >
> > # cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20_regs
> > only power adapter
On Sunday, January 5, 2014 7:13:06 PM UTC-5, Roman Mamedov wrote:
>
> On Sun, 5 Jan 2014 16:01:20 -0800 (PST)
> Patrick Wood > wrote:
>
> > Also, my experience with performance on the A10 devices over the last
> two
> > years has shown me that ondemand is a really terrible governor, as it
>
On Mon, 6 Jan 2014 00:00:00 +0200
Siarhei Siamashka wrote:
> A better solution is to really ramp up the CPU to the maximum clock
> speed if we have some external power source connected (ACIN or VBUS).
> Adhering to the "principle of least surprise", it makes sense to fork
> the "ondemand" governo
On Sun, 5 Jan 2014 16:01:20 -0800 (PST)
Patrick Wood wrote:
> Also, my experience with performance on the A10 devices over the last two
> years has shown me that ondemand is a really terrible governor, as it
> doesn't boost the CPU frequency unless utilization has been high over an
> extended
On Sunday, January 5, 2014 5:00:00 PM UTC-5, Siarhei Siamashka wrote:
>
> On Wed, 1 Jan 2014 20:03:35 -0800 (PST)
> Patrick Wood > wrote:
>
> > On Wednesday, January 1, 2014 5:54:20 PM UTC-5, Siarhei Siamashka wrote:
> > > I myself still see no good reason for using any governor other than
>
Hi,
On 01/05/2014 12:48 AM, Hans de Goede wrote:
Hi Arokux et al,
So I've been working on cleaning up the sunxi-ehci support by
writing a separate phy driver for the usbphy part of the SoC.
This is turning out quite nicely, for those interested you
can find my wip here:
Note only tested on su
On Sun, Jan 5, 2014 at 1:12 PM, wrote:
> 3 Ekim 2013 Perşembe 17:56:24 UTC+3 tarihinde Jon Smirl yazdı:
> > I have one of these A20 based EU3000 web cams.
> >
> >
> http://www.aliexpress.com/store/product/EU3000-HD2-Android4-2-TV-Box-Allwinner-A20-Cortex-Dual-Core-A7-5-0MP-Camera-MIC/507965_12137
Printing an error on probe-deferral clearly is not the right thing to do.
While at it I've also silenced the error in case of -ENODATA, so that
devm_phy_get can be used to get an optional phy without causing errors to
be printed. Alternatively a new devm_phy_get_optional method could be
added for t
On Mon, Jan 6, 2014 at 12:04 AM, Olliver Schinagl wrote:
> On 01/05/14 23:00, Siarhei Siamashka wrote:
>>
>> # cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20_regs
>> only power adapter : REG[0x0]=0xc1,REG[0x1]=0x10
>> power adapter + miniusb : REG[0x0]=0xf9,REG[0x1]=0x10
>
The phy-core allows phy_init and phy_power_on to be called multiple times,
but before this patch -ENOSUPP from phy_pm_runtime_get_sync would be
propagated to the caller for the 2nd and later calls.
Signed-off-by: Hans de Goede
---
drivers/phy/phy-core.c | 6 --
1 file changed, 4 insertions(+
Add support for ohci-platform instantiation from devicetree, including
optionally getting clks and a phy from devicetree, and enabling / disabling
those on power_on / off.
This should allow using ohci-platform from devicetree in various cases.
Specifically after this commit it can be used for the
Currently ehci-platform is only used in combination with devicetree when used
with some via socs. By extending it to (optionally) get clks and a phy from
devicetree, and enabling / disabling those on power_on / off, it can be used
more generically. Specifically after this commit it can be used for
On 01/05/14 23:00, Siarhei Siamashka wrote:
# cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20_regs
only power adapter : REG[0x0]=0xc1,REG[0x1]=0x10
power adapter + miniusb : REG[0x0]=0xf9,REG[0x1]=0x10
only miniusb : REG[0x0]=0x3d,REG[0x1]=0x70
miniusb + li
On 5 January 2014 23:00, Siarhei Siamashka wrote:
> On Wed, 1 Jan 2014 20:03:35 -0800 (PST)
> Patrick Wood wrote:
>
>> On Wednesday, January 1, 2014 5:54:20 PM UTC-5, Siarhei Siamashka wrote:
>> > I myself still see no good reason for using any governor other than
>> > "performance" when running
On Wed, 1 Jan 2014 20:03:35 -0800 (PST)
Patrick Wood wrote:
> On Wednesday, January 1, 2014 5:54:20 PM UTC-5, Siarhei Siamashka wrote:
> > I myself still see no good reason for using any governor other than
> > "performance" when running with a wall connected power plug. Poor
> > default cpufre
3 Ekim 2013 Perşembe 17:56:24 UTC+3 tarihinde Jon Smirl yazdı:
> I have one of these A20 based EU3000 web cams.
>
> http://www.aliexpress.com/store/product/EU3000-HD2-Android4-2-TV-Box-Allwinner-A20-Cortex-Dual-Core-A7-5-0MP-Camera-MIC/507965_1213723041.html
>
>
>
> Nice case and tiny package.
The unit has a Chinese Android build on it which is slowing me down.
I haven't figure out how to start adb Ethernet daemon on target device.
On Sun, Jan 5, 2014 at 12:01 PM, jonsm...@gmail.com wrote:
>
>
>
> On Sun, Jan 5, 2014 at 11:55 AM, Michal Suchanek wrote:
>
>> On 5 January 2014 17:48, j
On 12/21/2013 12:55 PM, Peter Chen wrote:
Thanks for you reply.The link should helps me a lot.Here is the CAN
controller document, hope it help those CAN driver deps.
Thanks for your documentation!
AFAIK, there is Flexcan implement in android framework,
https://github.com/zhangjie201412/Flex
On Sun, Jan 5, 2014 at 11:55 AM, Michal Suchanek wrote:
> On 5 January 2014 17:48, jonsm...@gmail.com wrote:
> >
> >
> >
> > On Sun, Jan 5, 2014 at 11:43 AM, Michal Suchanek
> wrote:
> >>
> >>
> >>
> >>
> >> On 5 January 2014 16:50, jonsm...@gmail.com wrote:
> >>
> >>>
> >>>
> >>>
> >>> On Sun
On 5 January 2014 17:48, jonsm...@gmail.com wrote:
>
>
>
> On Sun, Jan 5, 2014 at 11:43 AM, Michal Suchanek wrote:
>>
>>
>>
>>
>> On 5 January 2014 16:50, jonsm...@gmail.com wrote:
>>
>>>
>>>
>>>
>>> On Sun, Jan 5, 2014 at 5:38 AM, Michal Suchanek
>>> wrote:
AFAIK the camera board is
On Sun, Jan 5, 2014 at 11:43 AM, Michal Suchanek wrote:
>
>
>
> On 5 January 2014 16:50, jonsm...@gmail.com wrote:
>
>
>>
>>
>> On Sun, Jan 5, 2014 at 5:38 AM, Michal Suchanek wrote:
>>
>>> AFAIK the camera board is connected digitally so the noise is something
>>> that is internal to the camera
On 5 January 2014 16:50, jonsm...@gmail.com wrote:
>
>
> On Sun, Jan 5, 2014 at 5:38 AM, Michal Suchanek wrote:
>
>> AFAIK the camera board is connected digitally so the noise is something
>> that is internal to the camera board.
>>
>> It is normal that under low light condition the image is noi
On Sun, Jan 05, 2014 at 08:29:37AM -0800, Alexis Jeandet wrote:
> Ok thank, I didn't find this page,
It is at the very bottom of the front page, under the "Devices" section.
Here it reads:
If your device is not listed, you might need to work through the
new device howto.
> I wil
Ok thank, I didn't find this page, I will try to do as much as I can, I'm
actually trying to find a good kernel config, to get as much
devices working as I can, in parallel I will try to fill a new Wiki entry
for this device.
best regards,
Alexis.
--
You received this message because you ar
This gives some of our device drivers (realtek usb wifi for instance)
the ability to dynamically turn on/off USBCs. These config options match
sun4i and sun5i.
Signed-off-by: Luc Verhaegen
---
arch/arm/configs/sun7i_defconfig |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --g
On Sun, Jan 05, 2014 at 06:27:29AM -0800, Alexis Jeandet wrote:
> Hello everybody,
>
> I bought an A20 tablet which doesn't seems to be listed in the wiki device
> list, I would be happy to contribute in any way to provide all the
> information about it, I took some PCB pictures, I started to li
On Sun, Jan 5, 2014 at 5:38 AM, Michal Suchanek wrote:
> AFAIK the camera board is connected digitally so the noise is something
> that is internal to the camera board.
>
> It is normal that under low light condition the image is noisy. Did you
> try taking pictures in full daylight or using some
Allwinner A20 SoCs have a special interrupt controller for managing NMI.
Three register are present to (un)mask, control and acknowledge NMI.
These two patches add a new irqchip driver in cascade with GIC.
Carlo Caione (2):
ARM: sun7i: Add irqchip driver for NMI controller
ARM: sun7i: dts: Add
Allwinner A20 SoCs have special registers to control / (un)mask /
acknowledge NMI. This NMI controller is separated and independent from GIC.
This patch adds a new irqchip to manage NMI.
Signed-off-by: Carlo Caione
---
drivers/irqchip/Makefile| 1 +
drivers/irqchip/irq-sun7i-nmi.c | 19
This patch adds DTS entry for NMI controller as child of GIC.
Signed-off-by: Carlo Caione
---
arch/arm/boot/dts/sun7i-a20.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi b/arch/arm/boot/dts/sun7i-a20.dtsi
index 4c25f81..89e93da 100644
--- a/arch
On 12/31/2013 08:20 AM, Hans de Goede wrote:
The sun4i resisitive touchscreen controller also comes with a built-in
temperature sensor. This commit adds support for it.
This commit also introduces a new "ts-attached" device-tree property,
when this is not set, the input part of the driver won't
Hello everybody,
I bought an A20 tablet which doesn't seems to be listed in the wiki device
list, I would be happy to contribute in any way to provide all the
information about it, I took some PCB pictures, I started to list all the
chip inside.
At this point I can boot linux on it thank to Ol
On 01/05/14 14:32, Hans de Goede wrote:
Hi,
On 01/05/2014 01:42 PM, Olliver Schinagl wrote:
On 01/04/14 22:47, Arnd Bergmann wrote:
On Saturday 04 January 2014 22:39:50 Arnd Bergmann wrote:
+Required properties:
+- compatible : compatible list, contains "allwinner,sun4i-a10-ahci"
+- reg
Hi,
On 01/05/2014 01:42 PM, Olliver Schinagl wrote:
On 01/04/14 22:47, Arnd Bergmann wrote:
On Saturday 04 January 2014 22:39:50 Arnd Bergmann wrote:
+Required properties:
+- compatible : compatible list, contains "allwinner,sun4i-a10-ahci"
+- reg:
+- interrupts :
+- clocks
Hi,
On 01/05/2014 12:35 PM, Arnd Bergmann wrote:
On Sunday 05 January 2014, Hans de Goede wrote:
+static int sunxi_ahci_phy_init(struct device *dev, void __iomem *reg_base)
+{
+ u32 reg_val;
+ int timeout;
+
+ /* This magic is from the original code */
+ writel(0, re
Hi,
On 01/05/2014 01:42 PM, Olliver Schinagl wrote:
On 01/04/14 22:47, Arnd Bergmann wrote:
On Saturday 04 January 2014 22:39:50 Arnd Bergmann wrote:
+Required properties:
+- compatible : compatible list, contains "allwinner,sun4i-a10-ahci"
+- reg:
+- interrupts :
+- clocks
On 01/04/14 22:47, Arnd Bergmann wrote:
On Saturday 04 January 2014 22:39:50 Arnd Bergmann wrote:
+Required properties:
+- compatible : compatible list, contains "allwinner,sun4i-a10-ahci"
+- reg:
+- interrupts :
+- clocks : clocks for ACHI
+- clock-names: clock nam
Hi,
On 01/05/2014 11:56 AM, Arokux X wrote:
Hello Hans,
On Sun, Jan 5, 2014 at 12:48 AM, Hans de Goede wrote:
Hi Arokux et al,
So I've been working on cleaning up the sunxi-ehci support by
writing a separate phy driver for the usbphy part of the SoC.
This is turning out quite nicely, for th
On Sunday 05 January 2014, Hans de Goede wrote:
> >
> > Also, please send the binding as a separate patch with Cc to
> > the devicetree-discuss mailing list.
>
> Hmm, this contradicts what others are saying who have requested for
> the binding docs to be part of the same commit as the driver (with
Hello Hans,
On Sun, Jan 5, 2014 at 12:48 AM, Hans de Goede wrote:
> Hi Arokux et al,
>
> So I've been working on cleaning up the sunxi-ehci support by
> writing a separate phy driver for the usbphy part of the SoC.
>
> This is turning out quite nicely, for those interested you
> can find my wip h
AFAIK the camera board is connected digitally so the noise is something
that is internal to the camera board.
It is normal that under low light condition the image is noisy. Did you try
taking pictures in full daylight or using some photography lighting?
The noise can be removed in software and t
58 matches
Mail list logo
