Re: [linux-sunxi] Problem with Allwinner H3 clocks

2016-01-28 Thread Jean-Francois Moine 
On Thu, 28 Jan 2016 20:29:31 +0100
Maxime Ripard  wrote:

> > You are right, I had these lines in my DT. Thanks.
> 
> And even though you had these lines, it was still not working? Or is
> it working now? I'm confused.

It was not working with these lines because I was using the real pll8,
and, so, Jens' old patch was needed.

> > The A23/A33/H3 (and surely some other SoCs) documentations about
> > the peripheral/periph/periph0/periph1 PLLs say:
> > 
> > Note: The PLL Output should be fixed to 600MHz, it is not
> > recommended to vary this value arbitrarily.
> 
> I don't know if it's worth it at this point. The pll6 seems to work
> fine at other rates. Have you experienced any breakage when running at
> another frequency?

Each times I started my machine, the clocks (periph0 and 1) were 600MHz.
I think that this value should be OK for all subdevices (with the
kernel 3.4, I have 200MHz for AHB1 and underneath, 600MHz for
deinterlace and CSI, 300MHz and 50MHz for MMC).

-- 
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef |   http://moinejf.free.fr/

-- 
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] Ditter V21 HDMI Android TV stick - FEL mode?

2016-01-28 Thread Luc Verhaegen 
On Thu, Jan 28, 2016 at 07:04:28AM -0800, ffum...@googlemail.com wrote:
> Hi all,
> 
> I've got a Ditter V21 HDMI Android TV stick, based upon Allwinner A31s SoC:
> 
> http://freaktab.com/forum/tv-player-support/allwinner-tv-players/10567-ditter-v21-a31s-1gb-ram
> 
> Mine gets with the two buttons on the main board (v1.3).

http://linux-sunxi.org/New_Device_howto

Luc Verhaegen.

-- 
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] Problem with Allwinner H3 clocks

2016-01-28 Thread Jean-Francois Moine 
On Thu, 28 Jan 2016 09:15:57 +0100
Hans de Goede  wrote:

> p.s.
> 
> Did I understand correctly that you are working on a kms (or fbdev) driver
> for the H3? A fellow Dutch hacker (Jelle van der Waa, added to the Cc) is
> looking into adding H3 video console support to upstream u-boot. If you
> already have a lit-up display with an upstream kernel it would be great
> if you could share that, even if it is still wip.

Hi Hans and Jelle,

I submitted a (second) patch mid-january:

http://www.spinics.net/lists/dri-devel/msg98558.html

It has changed a bit since this time (towards simplification).
I was to submit a new patch, but the hardware cursor refuses to have
transparent pixels!
Otherwise, the TCON1 and DE2 are simple enough for the primary plane.
The problem is the HDMI driver...

-- 
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef |   http://moinejf.free.fr/

-- 
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] Problem with Allwinner H3 clocks

2016-01-28 Thread Jean-Francois Moine 
On Thu, 28 Jan 2016 14:16:26 +0100
Jens Kuske  wrote:

> after figuring out how to boot a devicetree kernel with allwinner's
> u-boot I only had to add the mandatory
>   
>   clock-frequency = <2400>;
>   arm,cpu-registers-not-fw-configured;
> 
> to the timer node and v4.5-rc1 booted successfully. They are
> intentionally left out in the official dt, because documentation says
> one should prefer to fix the firmware -> mainline u-boot
> No problems with clocks or uart here.

You are right, I had these lines in my DT. Thanks.

But, now, what about the PLL8 (periph1) which should be used by the MMCs?

The A23/A33/H3 (and surely some other SoCs) documentations about
the peripheral/periph/periph0/periph1 PLLs say:

Note: The PLL Output should be fixed to 600MHz, it is not
recommended to vary this value arbitrarily.

(the value is 1.2GHz for the A64)

Could it be safer or simpler to define the frequency of these clocks in
the DT (with their x2/d2)?

-- 
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef |   http://moinejf.free.fr/

-- 
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] Problem with Allwinner H3 clocks

2016-01-28 Thread Hans de Goede 

Hi,

On 01/28/2016 08:29 PM, Maxime Ripard wrote:

On Thu, Jan 28, 2016 at 05:59:18PM +0100, Jean-Francois Moine wrote:





The A23/A33/H3 (and surely some other SoCs) documentations about
the peripheral/periph/periph0/periph1 PLLs say:

Note: The PLL Output should be fixed to 600MHz, it is not
recommended to vary this value arbitrarily.


I don't know if it's worth it at this point. The pll6 seems to work
fine at other rates. Have you experienced any breakage when running at
another frequency?


Hmm, are we actually changing the freq of pll6 on any SoCs? I know we've
the code to it, but given that it is shared between many pheripherals,
I assume we end up never changing it. I assume / hope that the clock
framework protects against reclocking a clock with multiple users ...

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.

Re: [linux-sunxi] Problem with Allwinner H3 clocks

2016-01-28 Thread Maxime Ripard 
On Thu, Jan 28, 2016 at 05:59:18PM +0100, Jean-Francois Moine wrote:
> On Thu, 28 Jan 2016 14:16:26 +0100
> Jens Kuske  wrote:
> 
> > after figuring out how to boot a devicetree kernel with allwinner's
> > u-boot I only had to add the mandatory
> > 
> > clock-frequency = <2400>;
> > arm,cpu-registers-not-fw-configured;
> > 
> > to the timer node and v4.5-rc1 booted successfully. They are
> > intentionally left out in the official dt, because documentation says
> > one should prefer to fix the firmware -> mainline u-boot
> > No problems with clocks or uart here.
> 
> You are right, I had these lines in my DT. Thanks.

And even though you had these lines, it was still not working? Or is
it working now? I'm confused.

> But, now, what about the PLL8 (periph1) which should be used by the MMCs?

I just sent another version of the pll6 rework to enable it.

> The A23/A33/H3 (and surely some other SoCs) documentations about
> the peripheral/periph/periph0/periph1 PLLs say:
> 
>   Note: The PLL Output should be fixed to 600MHz, it is not
>   recommended to vary this value arbitrarily.

I don't know if it's worth it at this point. The pll6 seems to work
fine at other rates. Have you experienced any breakage when running at
another frequency?

Thanks!
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] Ditter V21 HDMI Android TV stick - FEL mode?

2016-01-28 Thread Luc Verhaegen 
On Thu, Jan 28, 2016 at 07:41:52AM -0800, Fabio Fumi wrote:
> This is the info from Android /system/build.prop, which should help 
> identifying the device:

This is pretty pointless.

Create a device page, and follow the new device howto.

Luc Verhaegen.

-- 
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] Problem with Allwinner H3 clocks

2016-01-28 Thread Hans de Goede 

Hi,

On 27-01-16 20:02, Jean-Francois Moine wrote:

On Wed, 27 Jan 2016 19:16:42 +0100
Hans de Goede  wrote:


To be sure, I generated a pure 4.5-rc1 kernel. Same result: no UART.
Maybe... one more information: I am using Allwinner's u-boot.


Could be that that is the culprit, why are you not using upstream u-boot?
upstream u-boot has H3 and orangepi-pc support now.


Yes, but using the upstream u-boot may hide the clock problem.


I agree that that could be the case. Would be interesting to figure out
what exactly is needed to get the upstream kernel to work properly
with allwinner's u-boot.

p.s.

Did I understand correctly that you are working on a kms (or fbdev) driver
for the H3? A fellow Dutch hacker (Jelle van der Waa, added to the Cc) is
looking into adding H3 video console support to upstream u-boot. If you
already have a lit-up display with an upstream kernel it would be great
if you could share that, even if it is still wip.

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.

Re: [linux-sunxi] Problem with Allwinner H3 clocks

2016-01-28 Thread Jens Kuske 
On 28/01/16 09:15, Hans de Goede wrote:
> Hi,
> 
> On 27-01-16 20:02, Jean-Francois Moine wrote:
>> On Wed, 27 Jan 2016 19:16:42 +0100
>> Hans de Goede  wrote:
>>
 To be sure, I generated a pure 4.5-rc1 kernel. Same result: no UART.
 Maybe... one more information: I am using Allwinner's u-boot.
>>>
>>> Could be that that is the culprit, why are you not using upstream u-boot?
>>> upstream u-boot has H3 and orangepi-pc support now.
>>
>> Yes, but using the upstream u-boot may hide the clock problem.
> 
> I agree that that could be the case. Would be interesting to figure out
> what exactly is needed to get the upstream kernel to work properly
> with allwinner's u-boot.

Hi,

after figuring out how to boot a devicetree kernel with allwinner's
u-boot I only had to add the mandatory

clock-frequency = <2400>;
arm,cpu-registers-not-fw-configured;

to the timer node and v4.5-rc1 booted successfully. They are
intentionally left out in the official dt, because documentation says
one should prefer to fix the firmware -> mainline u-boot
No problems with clocks or uart here.

Jens

-- 
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] Ditter V21 HDMI Android TV stick - FEL mode?

2016-01-28 Thread Fabio Fumi 
This is the info from Android /system/build.prop, which should help 
identifying the device:

ro.build.id=JDQ39
ro.build.display.id=mars_i11-eng 4.2.2 JDQ39 20131108 test-keys
ro.build.version.incremental=20131108
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=2013年 11月 08日 星期五 09:09:42 CST
ro.build.date.utc=1383872982
ro.build.type=eng
ro.build.user=hbc
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Softwinner
ro.product.brand=softwinners
ro.product.name=mars_i11
ro.product.device=mars_i11
ro.product.board=exdroid
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=fiber
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mars_i11
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=mars_i11-eng 4.2.2 JDQ39 20131108 test-keys
ro.build.fingerprint=softwinners/mars_i11/mars_i11:4.2.2/JDQ39/20131108:eng/test-keys
ro.build.characteristics=tablet

On Thursday, 28 January 2016 16:20:40 UTC+1, Luc Verhaegen wrote:
>
> On Thu, Jan 28, 2016 at 07:04:28AM -0800, ffu...@googlemail.com 
>  wrote: 
> > Hi all, 
> > 
> > I've got a Ditter V21 HDMI Android TV stick, based upon Allwinner A31s 
> SoC: 
> > 
> > 
> http://freaktab.com/forum/tv-player-support/allwinner-tv-players/10567-ditter-v21-a31s-1gb-ram
>  
> > 
> > Mine gets with the two buttons on the main board (v1.3). 
>
> http://linux-sunxi.org/New_Device_howto 
>
> Luc Verhaegen. 
>

-- 
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] Ditter V21 HDMI Android TV stick - FEL mode?

2016-01-28 Thread ffumi68 
Hi all,

I've got a Ditter V21 HDMI Android TV stick, based upon Allwinner A31s SoC:

http://freaktab.com/forum/tv-player-support/allwinner-tv-players/10567-ditter-v21-a31s-1gb-ram

Mine gets with the two buttons on the main board (v1.3).

I'd like to get on FEL mode on this, and my first question to the group here is 
whether anyone can give more info about this board and where to find the serial 
pads on it (if any...).

I anyhow tried getting to FEL though button+power mode, just trying to push the 
right button while pluggin it the USB cable.

Seems like working (I think), as I can read basic FEL info, once plugged in:

$ sudo ./sunxi-fel ver
AWUSBFEX soc=1633(A31) 0001 ver=0001 44 08 scratchpad=7e00  


but the 'fel read' command:

$ sudo ./sunxi-fel read 0x4240 0x82d0 boot1.header 

just hangs... Later, also 'fel ver' fails (returns nothing). 
I also noticed chip getting very hot.

I managed to extract meminfo and script_extractor (from the Android stock 
firmmware), but I'm stuck.

I'd really like to contribute to the Wiki with my device, but apart from these 
info I can't provide much more...

Any suggestion?

thanks
Fabio
(Rome)


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