Re: [linux-sunxi] "BUG: Bad page state in process ..." on Olimex A64-OLinuXino

[Chris Obbard]

Hi Martin,

You can do a 2nd stage cross-debootstrap on your host machine.
Also, you can build DTS as part of Linux make.
Where are your Kernel modules?

We (64 Studio) are making a scripted auto-debian image maker, watch
this space :-). If you are interested in helping or have some input
please contact me off-list.

Chris
Thanks,

Christopher Obbard
64 Studio Ltd.


On 13 March 2018 at 14:18, Martin Lucina  wrote:
> Hi,
>
> I'm trying to bootstrap Debian on an Olimex A64-OLinuXino board from
> scratch with mainline U-boot and kernel, using Debian stretch on x86_64 as
> the build host. For reference, here is the procedure I'm using:
>
> - cross-built mainline U-boot 2018.01 including the SPL and BL31 from latest
>   https://github.com/apritzel/arm-trusted-firmware.git#allwinner and
>   a64-olinuxino_defconfig:
>
>   (arm-trusted-firmware) $ make PLAT=sun50iw1p1 DEBUG=1 bl31 
> CROSS_COMPILE=aarch64- linux-gnu-
>   (u-boot) $ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- 
> a64-olinuxino_defconfig
>   (u-boot) $ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- 
> BL31=$(pwd)/../arm-trusted-firmware/build/sun50iw1p1/debug/bl31.bin
>
> - cross-built mainline kernel 4.15.7
>
>   (kernel) $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig
>   (kernel) $ make -j4 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
>
> - partitioned and installed to SD card following the instructions in
>   board/sunxi/README.sunxi64
>
>   SD card has a 128MB FAT partition (p1) and the remainder as ext4 (p2)
>
> - ran the debootstrap 1st stage:
>
>   sudo debootstrap --arch=arm64 --variant=minbase --foreign stretch /mnt
>
> - sucessfully booted into /bin/sh using the following boot.scr:
>
>   setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10
>   load mmc 0:1 0x4300 dtb
>   load mmc 0:1 0x4100 Image
>   booti 0x4100 - 0x4300
>
>   (dtb is arch/arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dtb)
>
> However, while running the debootstrap 2nd stage on the board, it seems that
> the kernel is not stable:
>
> # mount -n -o remount,rw /
> [   93.035277] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
> # /debootstrap/debootstrap --second-stage
> I: Keyring file not available at 
> /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror 
> https://deb.debian.org/debian
> I: Installing core packages...
> [  109.616360] random: crng init done
> [  138.840328] BUG: Bad page state in process dpkg  pfn:7bf40
> [  138.845825] page:7eefd000 count:64 mapcount:0 mapping: 
>  (null) index:0x1
> [  138.853908] flags: 0xfffc000()
> [  138.857657] raw: 0fffc000  0001 
> 0040
> [  138.865390] raw: dead0100 dead0200  
> 
> [  138.873119] page dumped because: nonzero _count
> [  138.877641] Modules linked in:
> [  138.880698] CPU: 3 PID: 1472 Comm: dpkg Tainted: GB
> 4.15.7 #1
> [  138.887734] Hardware name: Olimex A64-Olinuxino (DT)
> [  138.892689] Call trace:
> [  138.895144]  dump_backtrace+0x0/0x168
> [  138.898805]  show_stack+0x14/0x20
> [  138.902117]  dump_stack+0x98/0xb8
> [  138.905430]  bad_page+0xe4/0x148
> [  138.908653]  check_new_page_bad+0x64/0xa0
> [  138.912659]  get_page_from_freelist+0xbac/0x1048
> [  138.917269]  __alloc_pages_nodemask+0xdc/0xbd8
> [  138.921711]  alloc_pages_current+0x80/0xe8
> [  138.925805]  __page_cache_alloc+0xa0/0xb0
> [  138.929809]  pagecache_get_page+0xf8/0x280
> [  138.933902]  grab_cache_page_write_begin+0x24/0x40
> [  138.938690]  ext4_da_write_begin+0xa4/0x398
> [  138.942868]  generic_perform_write+0x98/0x180
> [  138.947221]  __generic_file_write_iter+0x130/0x1a0
> [  138.952005]  ext4_file_write_iter+0xe0/0x358
> [  138.956271]  __vfs_write+0xb0/0x118
> [  138.959754]  vfs_write+0xa4/0x1b0
> [  138.963064]  SyS_write+0x44/0xa0
> [  138.966288]  el0_svc_naked+0x30/0x34
> [  146.827756] BUG: Bad page state in process frontend  pfn:7a940
> [  146.833600] page:7eea5000 count:64 mapcount:0 mapping: 
>  (null) index:0x1
> [  146.841682] flags: 0xfffc000()
> [  146.845431] raw: 0fffc000  0001 
> 0040
> [  146.853162] raw: dead0100 dead0200  
> 
> [  146.860891] page dumped because: nonzero _count
> [  146.865413] Modules linked in:
> [  146.868471] CPU: 2 PID: 1499 Comm: frontend Tainted: GB
> 4.15.7 #1
> [  146.875854] Hardware name: Olimex A64-Olinuxino (DT)
> [  146.880810] Call trace:
> [  146.883265]  dump_backtrace+0x0/0x168
> [  146.886926]  show_stack+0x14/0x20
> [  146.890239]  dump_stack+0x98/0xb8
> [  146.893551]  bad_page+0xe4/0x148
> [  146.896775]  

Re: [linux-sunxi] Re: [PATCH v2 6/6] ASoC: sun4i-i2s: Add support for loopback

[Chris Obbard]

Hi Mark,

>
>> +- loopback:  if this property is present then the dai is configured in
>> + loopback mode where the output fifo is redirected to the input
>> + fifo.
>
> This really doesn't seem like something that ought to go into the DT
> and hence ABI given that there's obviously no reason to use this in
> production.  Just make it be a #define in the code or something.

It would be nice to have this as an optional devicetree property so
when testing JACK latency etc I don't have to manually re-compile a
kernel...

-- 
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] H5 I2S status

[Chris Obbard]

Any chance you can post a schematic on GitHub or the like, for
complete-ness?

I managed to just buzz out each pin from the audio codec to the header,
then connected the relevant ones to the header on the OPi :-). Shame the
OPiPC2 doesn't break out all of the I2S pins -- should have made sure
rather than trusting their claim of Pi2 compatibility! Doh!

On 16 December 2017 at 12:18, Matt Flax <flat...@flatmax.org> wrote:

>
> On 16/12/17 17:10, Code Kipper wrote:
>
>> On 16 December 2017 at 02:03, Matt Flax <flat...@flatmax.org> wrote:
>>
>>>
>>> On 16/12/17 06:47, Code Kipper wrote:
>>>
>>>> On 15 December 2017 at 20:05, Chris Obbard <obba...@gmail.com> wrote:
>>>>
>>>>> Thanks Chen-Yu, that patch was literally what I was about to write
>>>>> myself
>>>>> (but in a more spagetti-like way).
>>>>>
>>>>> root@orangepi:~# speaker-test -D hw:1 -c 2
>>>>>> speaker-test 1.1.3
>>>>>> Playback device is hw:1
>>>>>> Stream parameters are 48000Hz, S16_LE, 2 channels
>>>>>> Using 16 octaves of pink noise
>>>>>> Rate set to 48000Hz (requested 48000Hz)
>>>>>> Buffer size range from 128 to 131072
>>>>>> Period size range from 64 to 16384
>>>>>> Using max buffer size 131072
>>>>>> Periods = 4
>>>>>> Unable to set hw params for playback: Invalid argument
>>>>>> Setting of hwparams failed: Invalid argument
>>>>>>
>>>>>
>>>>>
>>>>> dmesg:
>>>>>
>>>>>> [  395.364594] sun4i-i2s 1c22000.i2s: Unsupported oversample rate:
>>>>>> 2083
>>>>>> [  395.370978] sun4i-i2s 1c22000.i2s: ASoC: can't set 1c22000.i2s hw
>>>>>> params: -22
>>>>>>
>>>>>
>>>>>
>>>>> cheers!
>>>>>
>>>> Hi Chris,
>>>> I've just retired from playing with my audio injector..it's no longer
>>>> barfing but nothing is playing at the moment. Do you see any clocking
>>>> on the BLCK or LRCLK?, I've yet to see anything coming off the pins.
>>>> I'll have another play tomorrow but at the moment all that I've really
>>>> changed is that I not longer do the mclk and blck div calculations in
>>>> sun4i_i2s_set_clk_rate as this is for the internal pll.
>>>> CK
>>>>
>>>
>>> Just wanted to see if it were possible to setup as codec master, which
>>> would
>>> generate the clocks from the wm8731 chip.
>>> This is done here :
>>> https://github.com/raspberrypi/linux/blob/rpi-4.9.y/sound/
>>> soc/bcm/audioinjector-pi-soundcard.c#L84
>>>
>>> snd_soc_dai_set_sysclk(rtd->codec_dai, WM8731_SYSCLK_XTAL, 1200,
>>> SND_SOC_CLOCK_IN);
>>>
>> Hi Max,
>> yeah I've seen this example before and was in the process of adding
>> some debugging in the wm8731 driver.
>>
>>> The flag WM8731_SYSCLK_XTAL sets the wm8731->sysclk_type variable here :
>>> https://github.com/raspberrypi/linux/blob/rpi-4.9.y/sound/
>>> soc/codecs/wm8731.c#L396
>>>
>>> Which returns true in wm8731_check_osc:
>>> https://github.com/raspberrypi/linux/blob/rpi-4.9.y/sound/
>>> soc/codecs/wm8731.c#L220
>>>
>>> Which enables the osc in the dapm route :
>>> https://github.com/raspberrypi/linux/blob/rpi-4.9.y/sound/
>>> soc/codecs/wm8731.c#L224
>>>
>>>
>>> You will notice that WM8731_SYSCLK_XTAL == 1 here :
>>> https://github.com/raspberrypi/linux/blob/rpi-4.9.y/sound/
>>> soc/codecs/wm8731.h#L34
>>>
>>> Has this been correctly set in your simple card device tree ?
>>>
>> I'll have a look later today, thanks for the description of the clock
>> setups.
>>
>> My board is plugged directly into the header for the Orange Pi 2(looks
>> to be pin compatible with the RPi2 header), other than the i2s and
>> power pins what pins are used by your board?
>>
>
> Only the I2C pins - nothing esoteric !
>
>
> BR,
>> CK
>>
>>> Matt
>>>
>>>
>>> On 14 December 2017 at 07:34, Chen-Yu Tsai <w...@csie.org> wrote:
>>>>>
>>>>>> On Thu, Dec 14, 2017 at 3:22 PM, Chris Obbard <obba...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Had a tiny bit of tim

Re: [linux-sunxi] H5 I2S status

[Chris Obbard]

Thanks Chen-Yu, that patch was literally what I was about to write myself
(but in a more spagetti-like way).

root@orangepi:~# speaker-test -D hw:1 -c 2
> speaker-test 1.1.3
> Playback device is hw:1
> Stream parameters are 48000Hz, S16_LE, 2 channels
> Using 16 octaves of pink noise
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 128 to 131072
> Period size range from 64 to 16384
> Using max buffer size 131072
> Periods = 4
> Unable to set hw params for playback: Invalid argument
> Setting of hwparams failed: Invalid argument



dmesg:

> [  395.364594] sun4i-i2s 1c22000.i2s: Unsupported oversample rate: 2083
> [  395.370978] sun4i-i2s 1c22000.i2s: ASoC: can't set 1c22000.i2s hw
> params: -22



cheers!

On 14 December 2017 at 07:34, Chen-Yu Tsai <w...@csie.org> wrote:

> On Thu, Dec 14, 2017 at 3:22 PM, Chris Obbard <obba...@gmail.com> wrote:
> > Had a tiny bit of time this morning, had to give it a go. But no joy.
> >
> >>
> >> root@orangepi:~# speaker-test --device hw:1 --channels 2
> >> speaker-test 1.1.3
> >> Playback device is hw:1
> >> Stream parameters are 48000Hz, S16_LE, 2 channels
> >> Using 16 octaves of pink noise
> >> Rate set to 48000Hz (requested 48000Hz)
> >> Buffer size range from 128 to 131072
> >> Period size range from 64 to 16384
> >> Using max buffer size 131072
> >> Periods = 4
> >> Unable to set hw params for playback: Invalid argument
> >> Setting of hwparams failed: Invalid argument
> >
> >
> > Will start delving into the I2S driver later this eve...
>
> Could you try applying the patch I just sent:
>
>https://patchwork.kernel.org/patch/10111589/
>
> This should give you some information about why "set hw params" failed.
>
> ChenYu
>
> > Cheers!
> >
> >
> > On 14 December 2017 at 06:46, Code Kipper <codekip...@gmail.com> wrote:
> >>
> >> On 13 December 2017 at 21:51, Chris Obbard <obba...@gmail.com> wrote:
> >> > Hi CK,
> >> >
> >> > That worked! Thanks.
> >> >
> >> > Here's the desg output now, all looks OK:
> >> >>
> >> >> [5.364112] wm8731 0-001a: Assuming static MCLK
> >> >> [5.368716] wm8731 0-001a: 0-001a supply AVDD not found, using
> dummy
> >> >> regulator
> >> >> [5.376037] wm8731 0-001a: 0-001a supply HPVDD not found, using
> >> >> dummy
> >> >> regulator
> >> >> [5.383089] sun4i-codec 1c22c00.codec: ASoC: codec-analog@1f015c0
> >> >> not
> >> >> registered
> >> >> [5.383098] sun4i-codec 1c22c00.codec: Failed to register our card
> >> >> [5.397183] wm8731 0-001a: 0-001a supply DCVDD not found, using
> >> >> dummy
> >> >> regulator
> >> >> [5.404775] wm8731 0-001a: 0-001a supply DBVDD not found, using
> >> >> dummy
> >> >> regulator
> >> >> [5.413332] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec
> >> >> mapping
> >> >> ok
> >> >> [5.420312] sun4i-codec 1c22c00.codec: ASoC: no DMI vendor name!
> >> >> [5.445524] asoc-simple-card sound: wm8731-hifi <-> 1c22000.i2s
> >> >> mapping
> >> >> ok
> >> >> [5.452773] asoc-simple-card sound: ASoC: no DMI vendor name!
> >> >
> >> >
> >> > The card is now detected by alsa (I also have a USB card plugged in):
> >> >>
> >> >> root@orangepi:~# aplay -l
> >> >>
> >> >>  List of PLAYBACK Hardware Devices 
> >> >> card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 []
> >> >>   Subdevices: 1/1
> >> >>   Subdevice #0: subdevice #0
> >> >> card 1: audio [AudioInjector audio], device 0:
> 1c22000.i2s-wm8731-hifi
> >> >> wm8731-hifi-0 []
> >> >>   Subdevices: 1/1
> >> >>   Subdevice #0: subdevice #0
> >> >> card 2: CODEC [USB AUDIO  CODEC], device 0: USB Audio [USB Audio]
> >> >>   Subdevices: 1/1
> >> >>   Subdevice #0: subdevice #0
> >> >
> >> >
> >> > & I can access Alsamixer to set settings over the already connected
> I2C
> >> > bus.
> >> >
> >> > But when it comes to playing a media file fails (seems to work OK with
> >> > USB
> >> > card):
> >>

Re: [linux-sunxi] H5 I2S status

[Chris Obbard]

Had a tiny bit of time this morning, had to give it a go. But no joy.


> root@orangepi:~# speaker-test --device hw:1 --channels 2
> speaker-test 1.1.3
> Playback device is hw:1
> Stream parameters are 48000Hz, S16_LE, 2 channels
> Using 16 octaves of pink noise
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 128 to 131072
> Period size range from 64 to 16384
> Using max buffer size 131072
> Periods = 4
> Unable to set hw params for playback: Invalid argument
> Setting of hwparams failed: Invalid argument


Will start delving into the I2S driver later this eve...

Cheers!


On 14 December 2017 at 06:46, Code Kipper <codekip...@gmail.com> wrote:

> On 13 December 2017 at 21:51, Chris Obbard <obba...@gmail.com> wrote:
> > Hi CK,
> >
> > That worked! Thanks.
> >
> > Here's the desg output now, all looks OK:
> >>
> >> [5.364112] wm8731 0-001a: Assuming static MCLK
> >> [5.368716] wm8731 0-001a: 0-001a supply AVDD not found, using dummy
> >> regulator
> >> [5.376037] wm8731 0-001a: 0-001a supply HPVDD not found, using dummy
> >> regulator
> >> [5.383089] sun4i-codec 1c22c00.codec: ASoC: codec-analog@1f015c0
> not
> >> registered
> >> [5.383098] sun4i-codec 1c22c00.codec: Failed to register our card
> >> [5.397183] wm8731 0-001a: 0-001a supply DCVDD not found, using dummy
> >> regulator
> >> [5.404775] wm8731 0-001a: 0-001a supply DBVDD not found, using dummy
> >> regulator
> >> [5.413332] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec
> mapping
> >> ok
> >> [5.420312] sun4i-codec 1c22c00.codec: ASoC: no DMI vendor name!
> >> [5.445524] asoc-simple-card sound: wm8731-hifi <-> 1c22000.i2s
> mapping
> >> ok
> >> [5.452773] asoc-simple-card sound: ASoC: no DMI vendor name!
> >
> >
> > The card is now detected by alsa (I also have a USB card plugged in):
> >>
> >> root@orangepi:~# aplay -l
> >>
> >>  List of PLAYBACK Hardware Devices 
> >> card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 []
> >>   Subdevices: 1/1
> >>   Subdevice #0: subdevice #0
> >> card 1: audio [AudioInjector audio], device 0: 1c22000.i2s-wm8731-hifi
> >> wm8731-hifi-0 []
> >>   Subdevices: 1/1
> >>   Subdevice #0: subdevice #0
> >> card 2: CODEC [USB AUDIO  CODEC], device 0: USB Audio [USB Audio]
> >>   Subdevices: 1/1
> >>   Subdevice #0: subdevice #0
> >
> >
> > & I can access Alsamixer to set settings over the already connected I2C
> bus.
> >
> > But when it comes to playing a media file fails (seems to work OK with
> USB
> > card):
> >>
> >> root@orangepi:~# speaker-test --device hw:1
> >>
> >>
> >> speaker-test 1.1.3
> >>
> >>
> >> Playback device is hw:1
> >>
> >> Stream parameters are 48000Hz, S16_LE, 1 channels
> >>
> >> Using 16 octaves of pink noise
> >>
> >> Channels count (1) not available for playbacks: Invalid argument
> >>
> >> Setting of hwparams failed: Invalid argument
>
> you will need to use speaker-test --device hw:1 -c 2
>
> >
> >
> > I will look tomorrow (with a scope) for any sign of twiddling on the I2S
> > pins, but I doubt it...
>
> Have hope?...if you don't hear anything initially can you change what
> is being written to SUN8I_I2S_FMT0_LRCK_PERIOD to 125.
> CK
> >
> >
> > Here's my DTS entry (copied from your WIP branch):
> >>
> >> sound {
> >> compatible = "simple-audio-card";
> >> simple-audio-card,name = "AudioInjector audio";
> >> simple-audio-card,format = "i2s";
> >> simple-audio-card,bitclock-master = <_master>;
> >> simple-audio-card,frame-master = <_master>;
> >> simple-audio-card,widgets =
> >> "Headphone", "Headphone Jack",
> >> "Microphone", "Microphone Jack",
> >> "Line", "Line Jack";
> >> simple-audio-card,routing =
> >>         "Headphone Jack", "RHPOUT",
> >> "Headphone Jack", "LHPOUT"

Re: [linux-sunxi] H5 I2S status

[Chris Obbard]

Hi CK,

That worked! Thanks.

Here's the desg output now, all looks OK:

> [5.364112] wm8731 0-001a: Assuming static MCLK
> [5.368716] wm8731 0-001a: 0-001a supply AVDD not found, using dummy
> regulator
> [5.376037] wm8731 0-001a: 0-001a supply HPVDD not found, using dummy
> regulator
> [5.383089] sun4i-codec 1c22c00.codec: ASoC: codec-analog@1f015c0 not
> registered
> [5.383098] sun4i-codec 1c22c00.codec: Failed to register our card
> [5.397183] wm8731 0-001a: 0-001a supply DCVDD not found, using dummy
> regulator
> [5.404775] wm8731 0-001a: 0-001a supply DBVDD not found, using dummy
> regulator
> [5.413332] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping
> ok
> [5.420312] sun4i-codec 1c22c00.codec: ASoC: no DMI vendor name!
> [5.445524] asoc-simple-card sound: wm8731-hifi <-> 1c22000.i2s mapping
> ok
> [5.452773] asoc-simple-card sound: ASoC: no DMI vendor name!


The card is now detected by alsa (I also have a USB card plugged in):

> root@orangepi:~# aplay -l

 List of PLAYBACK Hardware Devices 
> card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: audio [AudioInjector audio], device 0: 1c22000.i2s-wm8731-hifi
> wm8731-hifi-0 []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 2: CODEC [USB AUDIO  CODEC], device 0: USB Audio [USB Audio]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0


& I can access Alsamixer to set settings over the already connected I2C
bus.

But when it comes to playing a media file fails (seems to work OK with USB
card):

> root@orangepi:~# speaker-test --device hw:1


> speaker-test 1.1.3


> Playback device is hw:1

Stream parameters are 48000Hz, S16_LE, 1 channels

Using 16 octaves of pink noise

Channels count (1) not available for playbacks: Invalid argument

Setting of hwparams failed: Invalid argument


I will look tomorrow (with a scope) for any sign of twiddling on the I2S
pins, but I doubt it...


Here's my DTS entry (copied from your WIP branch):

> sound {
> compatible = "simple-audio-card";
> simple-audio-card,name = "AudioInjector audio";
> simple-audio-card,format = "i2s";
> simple-audio-card,bitclock-master = <_master>;
> simple-audio-card,frame-master = <_master>;
> simple-audio-card,widgets =
> "Headphone", "Headphone Jack",
> "Microphone", "Microphone Jack",
> "Line", "Line Jack";
> simple-audio-card,routing =
> "Headphone Jack", "RHPOUT",
> "Headphone Jack", "LHPOUT",
> "LLINEIN", "Line Jack",
> "MICIN", "Mic Bias",
> "Mic Bias", "Microphone Jack";
> simple-audio-card,cpu {
> sound-dai = <>;
> };
>     codec_master: simple-audio-card,codec {
> sound-dai = <>;
> system-clock-frequency = <1200>;
> };
> };



Cheers!




On 13 December 2017 at 09:57, Code Kipper <codekip...@gmail.com> wrote:

> is CONFIG_DMA_SUN6I=y set in the .config(It isn't by default)?
> CK
>
> On 12 December 2017 at 20:11, Chris Obbard <obba...@gmail.com> wrote:
> > So finally tonight I managed to connect up the Audioinjector to the
> correct
> > pins on the Orangepi PC2.
> >
> > It seems to be talking over i2c to the wm8731 OK, but fails to setup
> using
> > DMAEngine?
> >
> > Here's the relevant parts of dmesg:
> >
> >> [0.00] Linux version 4.15.0-rc2-gbd0835a69-dirty
> >> (chris@sunxi-build) (gcc version 7.2.0 (Debian 7.2.0-11)) #5 SMP
> PREEMPT Mon
> >> Dec 11 18:35:03 GMT 2017
> >> [0.00] Machine model: Xunlong Orange Pi PC 2
> >> [2.001533] ALSA device list:
> >> [2.004504]   No soundcards found.
> >> [7.954144] sun4i-i2s 1c22000.i2s: Could not register PCM
> >> [7.972456] sun4i-codec 1c22c00.codec: Failed to register against
> >> DMAEngine
> >> [8.000740] wm8731 0-001a: Assuming static MCLK
> >> [8.005336] wm8731 0-001a: 0-001a supply AVDD not fou

[linux-sunxi] Re: [PATCH 2/2] pinctrl: sunxi: Disable strict mode for H5 driver

[Chris Obbard]

Excellent, thanks Linus.  The new DTS files are not in mainline, but this
can wait ;-)


Cheers!

On 12 December 2017 at 08:52, Linus Walleij <linus.wall...@linaro.org>
wrote:

> On Thu, Nov 30, 2017 at 5:07 PM, Andre Przywara <andre.przyw...@arm.com>
> wrote:
> > On 30/11/17 15:51, Linus Walleij wrote:
> >> On Sat, Nov 25, 2017 at 1:02 PM, Andre Przywara <andre.przyw...@arm.com>
> wrote:
> >>
> >>> All of the H5 boards in the kernel reference the MMC0 CD pin twice in
> >>> their DT, so strict mode will make the MMC driver fail to load.
> >>> To keep existing DTs working, disable strict mode in the H5 driver.
> >>>
> >>> Signed-off-by: Andre Przywara <andre.przyw...@arm.com>
> >>> Reported-by: Chris Obbard <obba...@gmail.com>
> >>
> >> Patch applied with Maxime's ACK.
> >
> > Thanks for that (also to Maxime and Chen-Yu) and the smooth handling!
> >
> > Sorry, I just see that I didn't point this out explicitly, but this is
> > to fix a regression introduced in 4.15-rc1, so is this on a branch that
> > will be pushed for 4.15-rc, still? (Couldn't find anything quickly on
> > kernel.org)
>
> Should be upstream as:
> commit 07c43a382d7de3db01cc28bf2e17ed151cde2046
>
> Yours,
> Linus Walleij
>

-- 
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] H5 I2S status

[Chris Obbard]

Hi CK,

I have added the simple-soundcard node and the other relevant stuff in the
DTS and all seems to be OK.

Looks like the GPIO header on Orange Pi PC2 doesn't have access to
PCM0_DOUT (or PCM0_MCLK, but that doesn't matter so much), so I'm at a
stand-still until I can de-solder the resistor attached to the status LED.


I am testing with the AudioInjector Stereo, I was hoping it would be a
simple case of just plugging the Pi HAT in, but it never seems to be as
simple as that :-).


Will keep you updated with progress.

Cheers!


On 11 December 2017 at 13:16, Code Kipper <codekip...@gmail.com> wrote:

> Hi Chris.
> H5 support went in with the H3 so it should work. You will need to
> make dts changes or overlays for the devices that you're using.
> CK
>
> On 11 December 2017 at 12:41, Chris Obbard <obba...@gmail.com> wrote:
> > Hey
> >
> > I am looking into the H5 i2s mainline support, can anyone update me on
> the
> > status of this, point me to a wip branch or patch?
> >
> >
> > Cheers!
> >
> > --
> > 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] H5 I2S status

[Chris Obbard]

Hey

I am looking into the H5 i2s mainline support, can anyone update me on the
status of this, point me to a wip branch or patch?


Cheers!

-- 
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] OrangePi PC2 CPU Voltage Regulator

[Chris Obbard]

Hi Ondřej,

Interesting, looks like you are on the way to implementing a cpufreq
driver?  Are these patches submitted yet?

Cheers!

On 26 November 2017 at 16:15, Ondřej Jirman <meg...@megous.com> wrote:

> Chris Obbard píše v Ne 26. 11. 2017 v 15:24 +:
>
> Hi guys,
>
> Looking into the COU core voltage regulator on the opipc2. By default,
> through resistors on the PCB, the regulator is set to 1.1V and should be
> set by u-boot to 1.2V before bringing up the cpu core PLL as the cpu is
> spec'd at 1.2V.
>
> The u-boot sources (i am using tag v2017.09) already have support for the
> regulator on sunxi, so it's just a case of enabling that. Great!
>
> So I added the following into orangepi_pc2_defconfig (copied from
> orangepi_pc_defconfig):-
>
> > CONFIG_SPL_I2C_SUPPORT=y
> > CONFIG_SY8106A_POWER=y
>
> When compiling, I get:
>
> > aarch64-linux-gnu-ld.bfd: u-boot-spl section `.u_boot_list' will not fit
> in region `.sram'
> > aarch64-linux-gnu-ld.bfd: region `.sram' overflowed by 488 bytes
> > scripts/Makefile.spl:346: recipe for target 'spl/u-boot-spl' failed
>
> I guess this is due to the image generated from u-boot being too large now
> I have enabled a full I2C driver. I have tried manually configuring u-boot
> to remove some drivers like ethernet and video, but nothing can reduce this
> SPL size.
>
>
> Any ideas?
>
>
> Hi,
>
> if you won't be able to reduce SPL size, you can cherry pick some commits
> from this branch:
>
> https://github.com/megous/linux/commits/ths-4.14
>
> to get working SY8106A suppport on PC2.
>
> regards,
> o.
>
>
> cheers!
> --
> 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] OrangePi PC2 CPU Voltage Regulator

[Chris Obbard]

Hi guys,

Looking into the COU core voltage regulator on the opipc2. By default,
through resistors on the PCB, the regulator is set to 1.1V and should be
set by u-boot to 1.2V before bringing up the cpu core PLL as the cpu is
spec'd at 1.2V.

The u-boot sources (i am using tag v2017.09) already have support for the
regulator on sunxi, so it's just a case of enabling that. Great!

So I added the following into orangepi_pc2_defconfig (copied from
orangepi_pc_defconfig):-

> CONFIG_SPL_I2C_SUPPORT=y
> CONFIG_SY8106A_POWER=y

When compiling, I get:

> aarch64-linux-gnu-ld.bfd: u-boot-spl section `.u_boot_list' will not fit
in region `.sram'
> aarch64-linux-gnu-ld.bfd: region `.sram' overflowed by 488 bytes
> scripts/Makefile.spl:346: recipe for target 'spl/u-boot-spl' failed

I guess this is due to the image generated from u-boot being too large now
I have enabled a full I2C driver. I have tried manually configuring u-boot
to remove some drivers like ethernet and video, but nothing can reduce this
SPL size.


Any ideas?

cheers!

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

Hi,


>
> > Mmh, I guess it's related to:
> > commit 1396007286b1e2fd5dd10ae6a5ccaaaed51ab762
> > Author: Maxime Ripard 
> > Date:   Mon Oct 9 22:53:39 2017 +0200
> >
> > pinctrl: sunxi: Enforce the strict mode by default
> >
> > This is probably due to the fact that we reference PF6 twice:
> >
> > arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts:
> >>  {
> >> pinctrl-names = "default";
> >> pinctrl-0 = <_pins_a>, <_cd_pin>;
> >
> > Once here:^^
> >
>
> Drop this one.
>
> >> vmmc-supply = <_vcc3v3>;
> >> bus-width = <4>;
> >> cd-gpios = < 5 6 GPIO_ACTIVE_LOW>; /* PF6 */
> >
> > And then again here:  
> >
>
> And keep this one.
>
> ChenYu
>
>
Awesome, removing that line and recompiling sorted it.

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

Hi andre,

I used the orange pi pc2 dt  from mainline. Which hasn’t changed a while...

I’ll try to find the commit I used that found the sd  card from last week
when I’m home

Cheers!

On Fri, 24 Nov 2017 at 12:13, Andre Przywara <andre.przyw...@arm.com> wrote:

> Hi,
>
> On 24/11/17 11:58, Chris Obbard wrote:
> > [2.982523] sun50i-h5-pinctrl 1c20800.pinctrl: pin PF6 already
> > requested by 1c0f000.mmc; cannot claim for 1c20800.pinctrl:166
> > [2.993845] sun50i-h5-pinctrl 1c20800.pinctrl: pin-166
> > (1c20800.pinctrl:166) status -22
> > [3.002001] sunxi-mmc: probe of 1c0f000.mmc failed with error -22
>
> Did you change anything in the DT?
> Which DT do you actually use? Can you dump it here as well?
>
> I will try it later tonight at home.
>
> Cheers,
> Andre.
>

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

n root device "mmcblk0p1" or
> unknown-block(0,0): error -6
> [8.936340] Please append a correct "root=" boot option; here are the
> available partitions:
> [8.944705] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> [8.952960] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0-g5a787756b
> #1
> [8.959822] Hardware name: Xunlong Orange Pi PC 2 (DT)
> [8.964950] Call trace:
> [8.967405]  dump_backtrace+0x0/0x190
> [8.971065]  show_stack+0x14/0x20
> [8.974379]  dump_stack+0x9c/0xbc
> [8.977692]  panic+0x11c/0x290
> [8.980746]  mount_block_root+0x190/0x264
> [8.984750]  mount_root+0x11c/0x134
> [8.988233]  prepare_namespace+0x12c/0x174
> [8.992324]  kernel_init_freeable+0x200/0x224
> [8.996677]  kernel_init+0x10/0x100
> [9.000162]  ret_from_fork+0x10/0x18
> [9.003737] SMP: stopping secondary CPUs
> [9.007656] Kernel Offset: disabled
> [9.011139] CPU features: 0x002004
> [9.014534] Memory Limit: none
> [9.017589] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(0,0)
> [   19.528424] WARNING: CPU: 0 PID: 8 at kernel/irq_work.c:68
> irq_work_queue_on+0x110/0x128
> [   19.536505] CPU: 0 PID: 8 Comm: rcu_preempt Not tainted
> 4.14.0-g5a787756b #1
> [   19.543540] Hardware name: Xunlong Orange Pi PC 2 (DT)
> [   19.548669] task: 80003d9de200 task.stack: 08068000
> [   19.554580] pstate: 2085 (nzCv daIf -PAN -UAO)
> [   19.559367] pc : irq_work_queue_on+0x110/0x128
> [   19.563807] lr : rcu_implicit_dynticks_qs+0x2b8/0x2e8
> [   19.568849] sp : 0806bd30
> [   19.572158] x29: 0806bd30 x28: 0960a880
> [   19.577465] x27: 0001 x26: 
> [   19.582771] x25: 095eab48 x24: 0812d740
> [   19.588078] x23: 0001 x22: 095ead78
> [   19.593384] x21: 80003efa9480 x20: 0a42
> [   19.598691] x19: 0960a880 x18: 0010
> [   19.603997] x17: 0001 x16: 03ff
> [   19.609303] x15:  x14: 0400
> [   19.614609] x13:  x12: 
> [   19.619915] x11: 0001 x10: 0a00
> [   19.625221] x9 : 8000359d7000 x8 : 0019
> [   19.630527] x7 : 0001 x6 : 095e7000
> [   19.635833] x5 : 0002 x4 : 
> [   19.641140] x3 : 095ead68 x2 : 
> [   19.646445] x1 : 0001 x0 : 80003efa95e0
> [   19.651751] Call trace:
> [   19.654197]  irq_work_queue_on+0x110/0x128
> [   19.658289]  rcu_implicit_dynticks_qs+0x2b8/0x2e8
> [   19.662987]  force_qs_rnp+0x144/0x1d0
> [   19.45]  rcu_gp_kthread+0x468/0x790
> [   19.670477]  kthread+0x128/0x130
> [   19.673701]  ret_from_fork+0x10/0x18
> [   19.677270] ---[ end trace 00e4bb0d8d93413c ]---


On 24 November 2017 at 08:55, Andre Przywara <andre.przyw...@arm.com> wrote:

> Hi Chris,
>
> On 23/11/17 20:56, Chris Obbard wrote:
> > hi guys,
> >
> > had a bit of time to debug this tonight. here's my environment:
> >
> > u-boot v2017.09 with lower-default-cpufreq-H5.path applied.
> >
> > linux mainline, modules built-in, no ramdisk
> >
> > it's like it doesn't find the SD card, for whatever reason.
>
> Can you please dump the whole kernel log? It would be good to see what
> the MMC driver has to say and whether there are other issues (pinctrl?
> clocks?)
>
> Cheers,
> Andre.
>

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

hi guys,

had a bit of time to debug this tonight. here's my environment:

u-boot v2017.09 with lower-default-cpufreq-H5.path applied.

linux mainline, modules built-in, no ramdisk

it's like it doesn't find the SD card, for whatever reason.




[8.928343] VFS: Cannot open root device "mmcblk0p1" or
> unknown-block(0,0): error -6
> [8.936096] Please append a correct "root=" boot option; here are the
> available partitions:
> [8.944461] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> [8.952717] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.0-g5a787756b
> #1
> [8.959579] Hardware name: Xunlong Orange Pi PC 2 (DT)
> [8.964707] Call trace:
> [8.967161]  dump_backtrace+0x0/0x190
> [8.970820]  show_stack+0x14/0x20
> [8.974134]  dump_stack+0x9c/0xbc
> [8.977448]  panic+0x11c/0x290
> [8.980501]  mount_block_root+0x190/0x264
> [8.984505]  mount_root+0x11c/0x134
> [8.987989]  prepare_namespace+0x12c/0x174
> [8.992080]  kernel_init_freeable+0x200/0x224
> [8.996433]  kernel_init+0x10/0x100
> [8.19]  ret_from_fork+0x10/0x18
> [9.003493] SMP: stopping secondary CPUs
> [9.007411] Kernel Offset: disabled
> [9.010896] CPU features: 0x002004
> [9.014290] Memory Limit: none
> [9.017346] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(0,0)





On 21 November 2017 at 08:44, Chris Obbard <obba...@gmail.com> wrote:

> It is most likely the switch of the mmc regulators from a fixed one
>> to the AXP regulators.
>>
>> Please ensure you have the AXP mfd and regulator drivers built-in.
>> AFAIK the RSB variant of the AXP mfd driver does not support auto
>> loading of the module.
>
>
> I should have been more specific, I am using the Orange Pi PC2 which has
> a SY8106A regulator.  This is set to 1.1V by default without any comms from
> kernel.
>
> I am unsure as to why a regulator driver change would cause my SD card to
> not be found by the Kernel? On the Orange Pi PC2 the SD card is permanently
> wired to 3v3.
>
>
> Chris
>

-- 
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] [PATCH] sunxi: set the default CPUx frequency of H5 to 816MHz

[Chris Obbard]

At 1.1V & maximum cpufreq my Orange Pi PC2 boards kernel panic 90% of the 
time.  This patch works perfectly for my board.  Please apply patch to 
mainline.

Hopefully the idea is to run the regulator at it's default speed (& set a 
low maximum CPU speed from u-boot) then once the kernel has taken over 
control, set the regulator to (some-higher-voltage)V and set the cpufreq to 
it's maximum.  This would keep the boot-loader code fairly minimal.

Cheers!


On Monday, November 6, 2017 at 8:10:46 AM UTC, Jagan Teki wrote:
>
> On Fri, Nov 3, 2017 at 10:00 PM, Maxime Ripard 
>  wrote: 
> > On Fri, Nov 03, 2017 at 02:21:51PM +0530, Jagan Teki wrote: 
> >> On Thu, Nov 2, 2017 at 7:26 PM, Maxime Ripard 
> >>  wrote: 
> >> > On Wed, Nov 01, 2017 at 08:31:46AM +0800, Icenowy Zheng wrote: 
> >> >> 在 2017-10-31 21:54，Maxime Ripard 写道： 
> >> >> > On Tue, Oct 31, 2017 at 04:05:36PM +0800, ice...@aosc.io 
>  wrote: 
> >> >> > > 在 2017-10-31 15:57，Jagan Teki 写道： 
> >> >> > > > On Tue, Oct 31, 2017 at 5:06 AM, Icenowy Zheng  > wrote: 
> >> >> > > > > Some H5 boards are designed to start at 1.1V CPUx voltage 
> (e.g. Nano 
> >> >> > > > > Pi 
> >> >> > > > > NEO2), which may not work properly at 1008MHz if the chip's 
> quality is 
> >> >> > > > > not so good. 
> >> >> > > > > 
> >> >> > > > > Lower the default CPUx frequency of H5 to 816MHz. 
> >> >> > > > > 
> >> >> > > > > Signed-off-by: Icenowy Zheng  
> >> >> > > > > --- 
> >> >> > > > >  arch/arm/mach-sunxi/Kconfig | 2 +- 
> >> >> > > > >  1 file changed, 1 insertion(+), 1 deletion(-) 
> >> >> > > > > 
> >> >> > > > > diff --git a/arch/arm/mach-sunxi/Kconfig 
> b/arch/arm/mach-sunxi/Kconfig 
> >> >> > > > > index 09cfec6f57..1fededd0a3 100644 
> >> >> > > > > --- a/arch/arm/mach-sunxi/Kconfig 
> >> >> > > > > +++ b/arch/arm/mach-sunxi/Kconfig 
> >> >> > > > > @@ -397,9 +397,9 @@ config SYS_CLK_FREQ 
> >> >> > > > > default 100800 if MACH_SUN5I 
> >> >> > > > > default 100800 if MACH_SUN6I 
> >> >> > > > > default 91200 if MACH_SUN7I 
> >> >> > > > > +   default 81600 if MACH_SUN50I || MACH_SUN50I_H5 
> >> >> > > > > default 100800 if MACH_SUN8I 
> >> >> > > > 
> >> >> > > > Even orangepi pc2 has 1.1v after power-on and it's work fine 
> [1] did 
> >> >> > > > you find an issue with neo2? 
> >> >> > 
> >> >> > So you have one single model that fails, and you change the 
> default 
> >> >> > frequency of all the boards using that SoC? 
> >> >> 
> >> >> But I think we have already set the default frequency to 816MHz for 
> >> >> A64, and it seems that several H5 boards are designed to start at 
> 1.1v 
> >> >> (see the notes by Jagan above). 
> >> >> 
> >> >> > 
> >> >> > It seems a bit overkill. 
> >> >> > 
> >> >> > I guess we have two solutions: 
> >> >> >   1) Change the frequency in that board config 
> >> >> >   2) Change the voltage in that board config 
> >> >> 
> >> >> NEO2 don't have any voltage adjusting, it's fixed at 1.1V. 
> >> >> 
> >> >> And according to the Orange Pi PC2 and Prime schematics, they both 
> >> >> start at 1.1V. (The Prime schematics even says "For H5 adjust 
> >> >> VDD-CPUX to 1.1V). 
> >> > 
> >> > And what about the Zero Plus 2 ? 
> >> 
> >> Same equation with same reg values, but missing reg names on specific 
> >> register area Page 7 [4] but hope both were same. 
> > 
> > Ok, so it's not some H5 boards, it's all of them. It makes sense then, 
> > once the commit log has been changed. 
>
> Let me test and will apply all fine. 
>
> thanks! 
> -- 
> Jagan Teki 
> Free Software Engineer | www.openedev.com 
> U-Boot, Linux | Upstream Maintainer 
> Hyderabad, India. 
>

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

>
> It is most likely the switch of the mmc regulators from a fixed one
> to the AXP regulators.
>
> Please ensure you have the AXP mfd and regulator drivers built-in.
> AFAIK the RSB variant of the AXP mfd driver does not support auto
> loading of the module.


I should have been more specific, I am using the Orange Pi PC2 which has
a SY8106A regulator.  This is set to 1.1V by default without any comms from
kernel.

I am unsure as to why a regulator driver change would cause my SD card to
not be found by the Kernel? On the Orange Pi PC2 the SD card is permanently
wired to 3v3.


Chris

-- 
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] Latest kernel does not find SD card

[Chris Obbard]

A change between Friday and Sunday evening to sunxi-next Kernel has caused 
my H5-based Orange Pi PC2 to not find the SD card.   Is this a known 
problem?



Sorry for the lack of information; I am not at that terminal.

-- 
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: [PATCH v2 00/10] Allwinner H3/H5/A64(DE2) SimpleFB support

[Chris Obbard]

Hi Everyone,

What's the status of HDMI/SimpleFB driver for H5?

I don't see anything related to HDMI in linux-next dts files:

arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts  (example board)
arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi
arch/arm/boot/dts/sunxi-h3-h5.dtsi

On 6 November 2017 at 08:40, Daniel Vetter  wrote:

> On Thu, Nov 02, 2017 at 04:44:47PM +0100, Maxime Ripard wrote:
> > On Thu, Nov 02, 2017 at 04:51:29PM +0800, Icenowy Zheng wrote:
> > > 在 2017-10-27 23:06，Icenowy Zheng 写道：
> > > > This patchset adds support for the SimpleFB on Allwinner SoCs with
> > > > "Display Engine 2.0".
> > > >
> > > > PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs.
> > > >
> > > > PATCH 4 adds the pipeline strings for DE2 SimpleFB.
> > > >
> > > > PATCH 5 to 7 adds necessary device tree nodes (DE2 CCU and SimpleFB)
> > > > for H3/H5 SoCs.
> > > >
> > > > PATCH 8 to 10 are for Allwinner A64 SoC to enable SimpleFB.
> > > >
> > > > Icenowy Zheng (10):
> > > >   dt-bindings: fix the binding of Allwinner DE2 CCU of A83T and H3
> > > >   clk: sunxi-ng: add support for Allwinner H3 DE2 CCU
> > > >   clk: sunxi-ng: fix the A64/H5 clock description of DE2 CCU
> > > >   dt-bindings: simplefb-sunxi: add pipelines for DE2
> > > >   ARM: sun8i: h3/h5: add DE2 CCU device node for H3
> > > >   arm64: allwinner: h5: add compatible string for DE2 CCU
> > > >   ARM: sunxi: h3/h5: add simplefb nodes
> > > >   dt-bindings: add binding for A64 DE2 CCU SRAM
> > > >   arm64: allwinner: a64: add DE2 CCU for A64 SoC
> > > >   arm64: allwinner: a64: add simplefb for A64 SoC
> > >
> > > Maxime, could you review and, if possible, apply the H3/5
> > > part of this patchset?
> >
> > This came a bit late, we're too close from the merge window
> > now. Please resend them after -rc1 is out.
>
> Just dropping here that drm-misc is open all the time, making for a much
> better process for contributors :-)
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
>
> --
> 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] Re: [PATCH 1/1] add rgb888 pins to a20 to enable parallel rgb LCD

[Chris Obbard]

Hi Giulio,

If the board is available to buy, for general public use, then I think YES
it should go in as a separate DTS ;-).

Cheers!

On 7 November 2017 at 13:19, Giulio Benetti <giulio.bene...@micronovasrl.com
> wrote:

> As publicly available what do you mean?
> Need schematics and gerbers?
> Or that is possible to buy it online?
>
> --
> Giulio Benetti
> R Manager &
> Advanced Research
>
> MICRONOVA SRL
> Sede: Via A. Niedda 3 - 35010 Vigonza
> <https://maps.google.com/?q=Via+A.+Niedda+3+-+35010+Vigonza=gmail=g>
> (PD)
> Tel. 049/8931563 - Fax 049/8931346
> Cod.Fiscale - P.IVA 02663420285
> Capitale Sociale € 26.000 i.v.
> Iscritta al Reg. Imprese di Padova N. 02663420285
> Numero R.E.A. 258642
>
> Il 07/11/2017 14:14, Chris Obbard ha scritto:
>
>> I'd say no, do not merge if hardware is not publicly available, make a
>> separate DTS in your separate Tree that extends the board you are closest
>> to with your custom changes.
>>
>> Cheers!
>>
>> On 7 November 2017 at 13:13, Giulio Benetti <
>> giulio.bene...@micronovasrl.com <mailto:giulio.bene...@micronovasrl.com>>
>> wrote:
>>
>> It's a custom board of my Company.
>> Its complete dts is not ready, but that part works.
>> Do I have to submit this when I will submit entire board dts?
>> If yes, since our board has software open source, but not opensource
>> hardware,
>> will you accept our dts in the future?
>>
>> Thank you
>>
>> Il giorno martedì 7 novembre 2017 14:03:51 UTC+1, Maxime Ripard ha
>> scritto:
>>
>> On Tue, Nov 07, 2017 at 01:49:59PM +0100, Giulio Benetti wrote:
>>  > On sun7i-a20-* there's no way to enable PA00--PA27 as RGB888
>> LCD0 pins.
>>  >
>>  > Add lcd_rgb888_pins in sun7i-a20.dtsi.
>>  >
>>  > It can be used on sun7i-a20-olinuxino-lime.dts.
>>  > This patch gives possibility to set parallel lcd pins for
>> RGB888.
>>  > To be used with tcon0 in your .dts
>>
>> My question was on which board do you want to use it right now.
>> If the
>> answer is none, then we won't merge that patch, we have too many
>> pinctrl already to not add the unused ones.
>>
>> Maxime
>>
>> -- Maxime Ripard, Free Electrons
>> Embedded Linux and Kernel 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
>> <mailto:linux-sunxi+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout
>> <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] Re: [PATCH 1/1] add rgb888 pins to a20 to enable parallel rgb LCD

[Chris Obbard]

I'd say no, do not merge if hardware is not publicly available, make a
separate DTS in your separate Tree that extends the board you are closest
to with your custom changes.

Cheers!

On 7 November 2017 at 13:13, Giulio Benetti  wrote:

> It's a custom board of my Company.
> Its complete dts is not ready, but that part works.
> Do I have to submit this when I will submit entire board dts?
> If yes, since our board has software open source, but not opensource
> hardware,
> will you accept our dts in the future?
>
> Thank you
>
> Il giorno martedì 7 novembre 2017 14:03:51 UTC+1, Maxime Ripard ha scritto:
>>
>> On Tue, Nov 07, 2017 at 01:49:59PM +0100, Giulio Benetti wrote:
>> > On sun7i-a20-* there's no way to enable PA00--PA27 as RGB888 LCD0 pins.
>> >
>> > Add lcd_rgb888_pins in sun7i-a20.dtsi.
>> >
>> > It can be used on sun7i-a20-olinuxino-lime.dts.
>> > This patch gives possibility to set parallel lcd pins for RGB888.
>> > To be used with tcon0 in your .dts
>>
>> My question was on which board do you want to use it right now. If the
>> answer is none, then we won't merge that patch, we have too many
>> pinctrl already to not add the unused ones.
>>
>> Maxime
>>
>> --
>> Maxime Ripard, Free Electrons
>> Embedded Linux and Kernel 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.
>

-- 
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: [PATCH 1/1] add rgb888 pins to a20 to enable parallel rgb LCD

[Chris Obbard]

Hi Giulio,

Sounds good to me.  I guess you are developing using the Olimex Lime board,
in which case the DTS patch is useless to anyone else?

Cheers!

On 7 November 2017 at 13:27, Giulio Benetti <giulio.bene...@micronovasrl.com
> wrote:

> Sure,
>
> that is the idea.
> Here is one of the boards:
> http://www.micronovasrl.com/en/q027/
>
> We still don't have an e-commerce on website,
> but you can write us an e-mail and we can sell it to everybody.
>
> So when I will be ready with full DTS of that board,
> I will submit a patchset including rgb888_pins.
>
> Right?
>
> --
> Giulio Benetti
> R Manager &
> Advanced Research
>
> MICRONOVA SRL
> Sede: Via A. Niedda 3 - 35010 Vigonza
> <https://maps.google.com/?q=Via+A.+Niedda+3+-+35010+Vigonza=gmail=g>
> (PD)
> Tel. 049/8931563 - Fax 049/8931346
> Cod.Fiscale - P.IVA 02663420285
> Capitale Sociale € 26.000 i.v.
> Iscritta al Reg. Imprese di Padova N. 02663420285
> Numero R.E.A. 258642
>
> Il 07/11/2017 14:23, Chris Obbard ha scritto:
>
>> Hi Giulio,
>>
>> If the board is available to buy, for general public use, then I think
>> YES it should go in as a separate DTS ;-).
>>
>> Cheers!
>>
>> On 7 November 2017 at 13:19, Giulio Benetti <
>> giulio.bene...@micronovasrl.com <mailto:giulio.bene...@micronovasrl.com>>
>> wrote:
>>
>> As publicly available what do you mean?
>> Need schematics and gerbers?
>> Or that is possible to buy it online?
>>
>> -- Giulio Benetti
>> R Manager &
>> Advanced Research
>>
>> MICRONOVA SRL
>> Sede: Via A. Niedda 3 - 35010 Vigonza
>> <https://maps.google.com/?q=Via+A.+Niedda+3+-+35010+Vigonza;
>> entry=gmail=g>
>> (PD)
>> Tel. 049/8931563 - Fax 049/8931346
>> Cod.Fiscale - P.IVA 02663420285
>> Capitale Sociale € 26.000 i.v.
>> Iscritta al Reg. Imprese di Padova N. 02663420285
>> Numero R.E.A. 258642
>>
>> Il 07/11/2017 14:14, Chris Obbard ha scritto:
>>
>> I'd say no, do not merge if hardware is not publicly available,
>> make a separate DTS in your separate Tree that extends the board
>> you are closest to with your custom changes.
>>
>> Cheers!
>>
>> On 7 November 2017 at 13:13, Giulio Benetti
>> <giulio.bene...@micronovasrl.com
>> <mailto:giulio.bene...@micronovasrl.com>
>> <mailto:giulio.bene...@micronovasrl.com
>>
>> <mailto:giulio.bene...@micronovasrl.com>>> wrote:
>>
>>  It's a custom board of my Company.
>>  Its complete dts is not ready, but that part works.
>>  Do I have to submit this when I will submit entire board dts?
>>  If yes, since our board has software open source, but not
>> opensource
>>  hardware,
>>  will you accept our dts in the future?
>>
>>  Thank you
>>
>>  Il giorno martedì 7 novembre 2017 14:03:51 UTC+1, Maxime
>> Ripard ha
>>  scritto:
>>
>>  On Tue, Nov 07, 2017 at 01:49:59PM +0100, Giulio
>> Benetti wrote:
>>   > On sun7i-a20-* there's no way to enable PA00--PA27
>> as RGB888
>>  LCD0 pins.
>>   >
>>   > Add lcd_rgb888_pins in sun7i-a20.dtsi.
>>   >
>>   > It can be used on sun7i-a20-olinuxino-lime.dts.
>>   > This patch gives possibility to set parallel lcd
>> pins for
>>  RGB888.
>>   > To be used with tcon0 in your .dts
>>
>>  My question was on which board do you want to use it
>> right now.
>>  If the
>>  answer is none, then we won't merge that patch, we have
>> too many
>>  pinctrl already to not add the unused ones.
>>
>>  Maxime
>>
>>  -- Maxime Ripard, Free Electrons
>>  Embedded Linux and Kernel 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,
>>