Testing.

Testing.

[Oleg]

Hi
I want to help the platform support Amlogic (S8xx\S9xxx) on the new kernel.
I have a few different model boards with the Amlogic S8xx\S9xxx with a 
connected console UART \ SSH.
I can help with testing variants of the kernel on these boards.
In what form can I help the project ?

Excuse my English, I use computer translation.

Testing.

[Martin Blumenstingl]

Hi Oleg,

On Tue, May 2, 2017 at 8:37 AM, Oleg <balbes-150@yandex.ru> wrote:
> Hi
> I want to help the platform support Amlogic (S8xx\S9xxx) on the new kernel.
> I have a few different model boards with the Amlogic S8xx\S9xxx with a
> connected console UART \ SSH.
> I can help with testing variants of the kernel on these boards.
> In what form can I help the project ?
I am currently trying to improve support for the older (32-bit) Meson SoCs.
Unfortunately I only have a device with S812 (Meson8m2) - do you have
any boards with Meson8 (S802) or Meson8b (S805) SoC? we could team up
and add mainline support for your boards

current status on my Meson8m2 device is:
- USB works (I only tested host mode)
- SD card can be read and written
- ethernet (my device has 10/100Mbit/s only) works


Regards,
Martin

Testing.

[Oleg]

> On Tue, May 2, 2017 at 8:37 AM, Oleg <balbes-150@yandex.ru> wrote:
>> Hi
>> I want to help the platform support Amlogic (S8xx\S9xxx) on the new kernel.
>> I have a few different model boards with the Amlogic S8xx\S9xxx with a
>> connected console UART \ SSH.
>> I can help with testing variants of the kernel on these boards.
>> In what form can I help the project ?
> I am currently trying to improve support for the older (32-bit) Meson SoCs.
> Unfortunately I only have a device with S812 (Meson8m2) - do you have
> any boards with Meson8 (S802) or Meson8b (S805) SoC? we could team up
> and add mainline support for your boards
>
> current status on my Meson8m2 device is:
> - USB works (I only tested host mode)
> - SD card can be read and written
> - ethernet (my device has 10/100Mbit/s only) works
>
>
> Regards,
> Martin
Hi Martin.

I have a TV box S812 MXIII_Plus (2\16 eMMC), and the 2 model S805 (1\8 
NAND). I know there are several users with different models s802 s805 
s812 who are willing to participate in testing. Today I tried to use 
Your kernel (branch meson-mx integration-4.12-20170506-5) to build a 
test image Armbian (Ubuntu server). The kernel runs, but the system 
fully not starts, stops without error message. I think this is due to 
the fact that I use dtb data that is not priznachena for my model s812. 
I have asked members from the forum Armbian check out this image 
(kernel) on different models s8xxx. I hope that in a short time, you 
should see information from other users about how to start Your kernel 
on different models s8xxx. Soon I'll try to check - another of my 
existing models s805 and will report the results. You can write, and 
what else to check.

https://forum.armbian.com/index.php?/topic/3023-armbian-for-amlogic-s802s812/&do=findComment&comment=31246 

Testing.

[Martin Blumenstingl]

Hi Oleg,

On Sun, May 7, 2017 at 7:36 PM, Oleg <balbes-150@yandex.ru> wrote:
>
>> On Tue, May 2, 2017 at 8:37 AM, Oleg <balbes-150@yandex.ru> wrote:
>>>
>>> Hi
>>> I want to help the platform support Amlogic (S8xx\S9xxx) on the new
>>> kernel.
>>> I have a few different model boards with the Amlogic S8xx\S9xxx with a
>>> connected console UART \ SSH.
>>> I can help with testing variants of the kernel on these boards.
>>> In what form can I help the project ?
>>
>> I am currently trying to improve support for the older (32-bit) Meson
>> SoCs.
>> Unfortunately I only have a device with S812 (Meson8m2) - do you have
>> any boards with Meson8 (S802) or Meson8b (S805) SoC? we could team up
>> and add mainline support for your boards
>>
>> current status on my Meson8m2 device is:
>> - USB works (I only tested host mode)
>> - SD card can be read and written
>> - ethernet (my device has 10/100Mbit/s only) works
>>
>>
>> Regards,
>> Martin
>
> Hi Martin.
>
> I have a TV box S812 MXIII_Plus (2\16 eMMC), and the 2 model S805 (1\8
> NAND). I know there are several users with different models s802 s805 s812
> who are willing to participate in testing. Today I tried to use Your kernel
> (branch meson-mx integration-4.12-20170506-5) to build a test image Armbian
> (Ubuntu server). The kernel runs, but the system fully not starts, stops
> without error message. I think this is due to the fact that I use dtb data
> that is not priznachena for my model s812.
is the .dtb (or .dts) of your device available in your github repo [0]?
also please note that you need to change the bootargs in u-boot before
you can boot a mainline kernel (see also [1]): setenv bootargs
"console=ttyAML0,115200" (without this your serial console won't work)


Regards,
Martin

[0] https://github.com/150balbes/Amlogic_s905
[1] http://linux-meson.com/doku.php?id=start#bit_socs_meson8b_s805_or_older

Testing.

[Oleg]

> is the .dtb (or .dts) of your device available in your github repo [0]?
> also please note that you need to change the bootargs in u-boot before
> you can boot a mainline kernel (see also [1]): setenv bootargs
> "console=ttyAML0,115200" (without this your serial console won't work)
>
>
> Regards,
> Martin
>
> [0] https://github.com/150balbes/Amlogic_s905
> [1] http://linux-meson.com/doku.php?id=start#bit_socs_meson8b_s805_or_older
I use the kernel 3.14.29 these dts .
For my model s812


-------------- next part --------------


meson8m2_n200_2G_1000.dts

https://github.com/150balbes/Amlogic_s8xx-kernel/tree/S812/arch/arm/boot/dts


and s805   2 models.

meson8b_i5.dts
meson8b_hd180.dts

https://github.com/150balbes/Amlogic_s8xx-kernel/tree/S805/arch/arm/boot/dts

This is the source test file, which is obtained when compiling the executable script s805_autoscript (used in multi-boot mode), 
which sets the required variables and performs the automatic startup of the system from removable media when testing. 
Internal firmware remains unchanged, this allows any non-trained user with no risk to test any system.

boot-vegas812_AM.cmd

https://github.com/150balbes/lib/tree/master/config/bootscripts

Perhaps You will be more clear what is happening on the logs from the console UART while trying to start at s812 and s805.

https://yadi.sk/i/rhJQe_qi3HpNQr

https://yadi.sk/i/czHlGCyt3HpNQD

Testing.

[Martin Blumenstingl]

Hi Oleg,

On Sun, May 7, 2017 at 8:36 PM, Oleg <balbes-150@yandex.ru> wrote:
>
> Hi Oleg,
>
> On Sun, May 7, 2017 at 7:36 PM, Oleg <balbes-150@yandex.ru> wrote:
>
> On Tue, May 2, 2017 at 8:37 AM, Oleg <balbes-150@yandex.ru> wrote:
>
> Hi
> I want to help the platform support Amlogic (S8xx\S9xxx) on the new
> kernel.
> I have a few different model boards with the Amlogic S8xx\S9xxx with a
> connected console UART \ SSH.
> I can help with testing variants of the kernel on these boards.
> In what form can I help the project ?
>
> I am currently trying to improve support for the older (32-bit) Meson
> SoCs.
> Unfortunately I only have a device with S812 (Meson8m2) - do you have
> any boards with Meson8 (S802) or Meson8b (S805) SoC? we could team up
> and add mainline support for your boards
>
> current status on my Meson8m2 device is:
> - USB works (I only tested host mode)
> - SD card can be read and written
> - ethernet (my device has 10/100Mbit/s only) works
>
>
> Regards,
> Martin
>
> Hi Martin.
>
> I have a TV box S812 MXIII_Plus (2\16 eMMC), and the 2 model S805 (1\8
> NAND). I know there are several users with different models s802 s805 s812
> who are willing to participate in testing. Today I tried to use Your kernel
> (branch meson-mx integration-4.12-20170506-5) to build a test image Armbian
> (Ubuntu server). The kernel runs, but the system fully not starts, stops
> without error message. I think this is due to the fact that I use dtb data
> that is not priznachena for my model s812.
>
> is the .dtb (or .dts) of your device available in your github repo [0]?
> also please note that you need to change the bootargs in u-boot before
> you can boot a mainline kernel (see also [1]): setenv bootargs
> "console=ttyAML0,115200" (without this your serial console won't work)
>
>
> Regards,
> Martin
>
> [0] https://github.com/150balbes/Amlogic_s905
> [1] http://linux-meson.com/doku.php?id=start#bit_socs_meson8b_s805_or_older
>
>
> I use the kernel 3.14.29 these dts .
> For my model s812
>
> meson8m2_n200_2G_1000.dts
>
> https://github.com/150balbes/Amlogic_s8xx-kernel/tree/S812/arch/arm/boot/dts
>
>
> and s805   2 models.
>
> meson8b_i5.dts
> meson8b_hd180.dts
>
> https://github.com/150balbes/Amlogic_s8xx-kernel/tree/S805/arch/arm/boot/dts
>
> This is the source test file, which is obtained when compiling the
> executable script s805_autoscript (used in multi-boot mode), which sets the
> required variables and performs the automatic startup of the system from
> removable media when testing. Internal firmware remains unchanged, this
> allows any non-trained user with no risk to test any system.
>
> boot-vegas812_AM.cmd
>
> https://github.com/150balbes/lib/tree/master/config/bootscripts
OK, I see - thanks for the details!

>
> Perhaps You will be more clear what is happening on the logs from the
> console UART while trying to start at s812 and s805.
OK, there are two different "problems", see below

> https://yadi.sk/i/rhJQe_qi3HpNQr
I forgot a patch which enables CONFIG_MMC_MESON_MX_SDIO on the
multi_v7_defconfig. I just pushed an update: [0] (but you can simply
enable that symbol in your .config - just make sure you set it to =y).
same with the USB2 PHY driver (CONFIG_PHY_MESON8B_USB2)

> https://yadi.sk/i/czHlGCyt3HpNQD
I only enabled SD/USB/etc. for the M8S board, so additional patches
are needed for other boards.

PS: I've just seen that you sent some mails as HTML-mails.
the mailing list rejects these - please always send plain-text mails!


Regards,
Martin


[0] https://github.com/xdarklight/linux/tree/meson-mx-integration-4.12-20170507

Testing.

[Oleg]

> I forgot a patch which enables CONFIG_MMC_MESON_MX_SDIO on the
> multi_v7_defconfig. I just pushed an update: [0] (but you can simply
> enable that symbol in your .config - just make sure you set it to =y).
> same with the USB2 PHY driver (CONFIG_PHY_MESON8B_USB2)
Thanks for the explanation, tomorrow I'll check it out on their models.
I apologize for the duplication.

Testing.

[Martin Blumenstingl]

On Sun, May 7, 2017 at 9:09 PM, Oleg <balbes-150@yandex.ru> wrote:
>
>
>> I forgot a patch which enables CONFIG_MMC_MESON_MX_SDIO on the
>> multi_v7_defconfig. I just pushed an update: [0] (but you can simply
>> enable that symbol in your .config - just make sure you set it to =y).
>> same with the USB2 PHY driver (CONFIG_PHY_MESON8B_USB2)
>
> Thanks for the explanation, tomorrow I'll check it out on their models.
perfect, thank you already for testing this!
please note that (typically) I have limited time during the week - so
I may not reply before next weekend

good luck with testing!


Regards,
Martin

Testing.

[Oleg]

> perfect, thank you already for testing this!
> please note that (typically) I have limited time during the week - so
> I may not reply before next weekend
>
> good luck with testing!
Assembled a new test image with the meson 
branch-mx-integration-4.12-20170507 ,
included in the config file the option CONFIG_MMC_MESON_MX_SDIO=y and 
CONFIG_PHY_MESON8B_USB2=y .
Tried to run from SD card new version, yet the result is the same as 
before. I do not consider ?
What compiler is better to use 4.9.4 or 6.3.1 ?

Testing.

[Martin Blumenstingl]

On Sun, May 7, 2017 at 10:44 PM, Oleg <balbes-150@yandex.ru> wrote:
>
>> perfect, thank you already for testing this!
>> please note that (typically) I have limited time during the week - so
>> I may not reply before next weekend
>>
>> good luck with testing!
>
> Assembled a new test image with the meson
> branch-mx-integration-4.12-20170507 ,
> included in the config file the option CONFIG_MMC_MESON_MX_SDIO=y and
> CONFIG_PHY_MESON8B_USB2=y .
> Tried to run from SD card new version, yet the result is the same as before.
so the kernel output is still the same? can you please share your .config then?

> What compiler is better to use 4.9.4 or 6.3.1 ?
personally I'm using arm-none-eabi-gcc 6.3.1 (from Arch Linux' community repo)

Testing.

[Oleg]

> so the kernel output is still the same? can you please share your .config then?
>
The config used when building image.

https://github.com/150balbes/lib/blob/master/config/kernel/linux-vegas812-next.config

Testing.

[Oleg]

[    5.784393] tegra-ehci: Tegra EHCI driver
[    5.788381] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    5.794471] ohci-pci: OHCI PCI platform driver
[    5.798903] ohci-platform: OHCI generic platform driver
[    5.804174] ohci-omap3: OHCI OMAP3 driver
[    5.808132] SPEAr-ohci: OHCI SPEAr driver
[    5.812119] ohci-st: OHCI STMicroelectronics driver
[    5.816989] ohci-atmel: OHCI Atmel driver
[    5.821290] usbcore: registered new interface driver usb-storage
[    5.829289] i2c /dev entries driver
[    5.835640] meson_wdt c1109900.watchdog: Watchdog enabled (timeout=8 
sec, nowayout=0)
[    5.839928] sdhci: Secure Digital Host Controller Interface driver
[    5.844316] sdhci: Copyright(c) Pierre Ossman
[    5.849477] Synopsys Designware Multimedia Card Interface Driver
[    5.856562] sdhci-pltfm: SDHCI platform and OF driver helper
[    5.861442] of_pwm_get(): PWM chip not found
[    5.864538] leds_pwm pwmleds: unable to request PWM for 
m8s:blue:power: -517
[    5.871728] ledtrig-cpu: registered to indicate activity on CPUs
[    5.877766] usbcore: registered new interface driver usbhid
[    5.883048] usbhid: USB HID core driver
[    5.944209] NET: Registered protocol family 10
[    5.944923] Segment Routing with IPv6
[    5.946713] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.953100] NET: Registered protocol family 17
[    5.956991] can: controller area network core (rev 20120528 abi 9)
[    5.963199] NET: Registered protocol family 29
[    5.967561] can: raw protocol (rev 20120528)
[    5.971808] can: broadcast manager protocol (rev 20161123 t)
[    5.977457] can: netlink gateway (rev 20130117) max_hops=1
[    5.983198] Key type dns_resolver registered
[    5.987424] ThumbEE CPU extension supported.
[    5.991403] Registering SWP/SWPB emulation handler
[    5.997855] Btrfs loaded, crc32c=crc32c-generic
[    6.005513] dwc2 c9040000.usb: c9040000.usb supply vusb_d not found, 
using dummy regulator
[    6.008952] dwc2 c9040000.usb: c9040000.usb supply vusb_a not found, 
using dummy regulator
[    6.018320] phy phy-c1108800.phy.0: USB ID detect failed!
[    6.022538] phy phy-c1108800.phy.0: phy poweron failed --> -22
[    6.028450] dwc2: probe of c9040000.usb failed with error -22
[    6.035485] dwc2 c90c0000.usb: c90c0000.usb supply vusb_d not found, 
using dummy regulator
[    6.042337] dwc2 c90c0000.usb: c90c0000.usb supply vusb_a not found, 
using dummy regulator
[    6.182662] dwc2 c90c0000.usb: DWC OTG Controller
[    6.182732] dwc2 c90c0000.usb: new USB bus registered, assigned bus 
number 1
[    6.188786] dwc2 c90c0000.usb: irq 23, io mem 0xc90c0000
[    6.194739] hub 1-0:1.0: USB hub found
[    6.197804] hub 1-0:1.0: 1 port detected
[    6.206952] of_pwm_get(): PWM chip not found
[    6.207005] leds_pwm pwmleds: unable to request PWM for 
m8s:blue:power: -517
[    6.213401] hctosys: unable to open rtc device (rtc0)
[    6.218262] VCC3V3: disabling
[    6.222866] Freeing unused kernel memory: 2048K
[    6.622590] usb 1-1: new high-speed USB device number 2 using dwc2
[    6.832594] usb 1-1: device descriptor read/64, error -32
[    7.162580] usb 1-1: device descriptor read/64, error -32
[    7.492542] usb 1-1: new high-speed USB device number 3 using dwc2
[    7.702535] usb 1-1: device descriptor read/64, error -32
[    8.032534] usb 1-1: device descriptor read/64, error -32
[    8.362547] usb 1-1: new high-speed USB device number 4 using dwc2
[    8.802534] usb 1-1: device not accepting address 4, error -32
[    9.012535] usb 1-1: new high-speed USB device number 5 using dwc2
[    9.452534] usb 1-1: device not accepting address 5, error -32
[    9.452767] usb usb1-port1: unable to enumerate USB device
[  133.312550] random: crng init done

Testing.

[Martin Blumenstingl]

On Sun, May 7, 2017 at 10:57 PM, Oleg <balbes-150@yandex.ru> wrote:
> [    5.784393] tegra-ehci: Tegra EHCI driver
> [    5.788381] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> [    5.794471] ohci-pci: OHCI PCI platform driver
> [    5.798903] ohci-platform: OHCI generic platform driver
> [    5.804174] ohci-omap3: OHCI OMAP3 driver
> [    5.808132] SPEAr-ohci: OHCI SPEAr driver
> [    5.812119] ohci-st: OHCI STMicroelectronics driver
> [    5.816989] ohci-atmel: OHCI Atmel driver
> [    5.821290] usbcore: registered new interface driver usb-storage
> [    5.829289] i2c /dev entries driver
> [    5.835640] meson_wdt c1109900.watchdog: Watchdog enabled (timeout=8 sec,
> nowayout=0)
> [    5.839928] sdhci: Secure Digital Host Controller Interface driver
> [    5.844316] sdhci: Copyright(c) Pierre Ossman
> [    5.849477] Synopsys Designware Multimedia Card Interface Driver
> [    5.856562] sdhci-pltfm: SDHCI platform and OF driver helper
> [    5.861442] of_pwm_get(): PWM chip not found
> [    5.864538] leds_pwm pwmleds: unable to request PWM for m8s:blue:power:
> -517
> [    5.871728] ledtrig-cpu: registered to indicate activity on CPUs
> [    5.877766] usbcore: registered new interface driver usbhid
> [    5.883048] usbhid: USB HID core driver
> [    5.944209] NET: Registered protocol family 10
> [    5.944923] Segment Routing with IPv6
> [    5.946713] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> [    5.953100] NET: Registered protocol family 17
> [    5.956991] can: controller area network core (rev 20120528 abi 9)
> [    5.963199] NET: Registered protocol family 29
> [    5.967561] can: raw protocol (rev 20120528)
> [    5.971808] can: broadcast manager protocol (rev 20161123 t)
> [    5.977457] can: netlink gateway (rev 20130117) max_hops=1
> [    5.983198] Key type dns_resolver registered
> [    5.987424] ThumbEE CPU extension supported.
> [    5.991403] Registering SWP/SWPB emulation handler
> [    5.997855] Btrfs loaded, crc32c=crc32c-generic
> [    6.005513] dwc2 c9040000.usb: c9040000.usb supply vusb_d not found,
> using dummy regulator
> [    6.008952] dwc2 c9040000.usb: c9040000.usb supply vusb_a not found,
> using dummy regulator
> [    6.018320] phy phy-c1108800.phy.0: USB ID detect failed!
> [    6.022538] phy phy-c1108800.phy.0: phy poweron failed --> -22
> [    6.028450] dwc2: probe of c9040000.usb failed with error -22
I assume your device has an internal USB hub? this probably has to be
turned on before the controller starts working

> [    6.035485] dwc2 c90c0000.usb: c90c0000.usb supply vusb_d not found,
> using dummy regulator
> [    6.042337] dwc2 c90c0000.usb: c90c0000.usb supply vusb_a not found,
> using dummy regulator
> [    6.182662] dwc2 c90c0000.usb: DWC OTG Controller
> [    6.182732] dwc2 c90c0000.usb: new USB bus registered, assigned bus
> number 1
> [    6.188786] dwc2 c90c0000.usb: irq 23, io mem 0xc90c0000
> [    6.194739] hub 1-0:1.0: USB hub found
> [    6.197804] hub 1-0:1.0: 1 port detected
> [    6.206952] of_pwm_get(): PWM chip not found
this sounds innocent at first but actually it's crucial for MMC (at
least in the current M8S configuration). PWM_E is used to generate the
32.768 kHz clock for the wifi chip. so without CONFIG_PWM_MESON the
pwm_ef node won't get probed, meaning that a dependency of the mmc
controller is missing.
I'll fix that as well next weekend (it also has to be enabled in
multi_v7_defconfig)

> [    6.207005] leds_pwm pwmleds: unable to request PWM for m8s:blue:power:
> -517
> [    6.213401] hctosys: unable to open rtc device (rtc0)
> [    6.218262] VCC3V3: disabling
> [    6.222866] Freeing unused kernel memory: 2048K
> [    6.622590] usb 1-1: new high-speed USB device number 2 using dwc2
> [    6.832594] usb 1-1: device descriptor read/64, error -32
> [    7.162580] usb 1-1: device descriptor read/64, error -32
> [    7.492542] usb 1-1: new high-speed USB device number 3 using dwc2
> [    7.702535] usb 1-1: device descriptor read/64, error -32
> [    8.032534] usb 1-1: device descriptor read/64, error -32
> [    8.362547] usb 1-1: new high-speed USB device number 4 using dwc2
> [    8.802534] usb 1-1: device not accepting address 4, error -32
> [    9.012535] usb 1-1: new high-speed USB device number 5 using dwc2
> [    9.452534] usb 1-1: device not accepting address 5, error -32
> [    9.452767] usb usb1-port1: unable to enumerate USB device
this looks suspicious, do you have anything connected to that port?
I've seen that when connecting a 2.5" HDD when the PSU doesn't have
enough power to spin up the HDD as well.


Martin

Testing.

[Oleg]

> this sounds innocent at first but actually it's crucial for MMC (at
> least in the current M8S configuration). PWM_E is used to generate the
> 32.768 kHz clock for the wifi chip. so without CONFIG_PWM_MESON the
> pwm_ef node won't get probed, meaning that a dependency of the mmc
> controller is missing.
> I'll fix that as well next weekend (it also has to be enabled in
> multi_v7_defconfig)
I found in the configuration CONFIG_PWM_MESON and put =y.
  Or you need to add code / patch in the source code ?

> this looks suspicious, do you have anything connected to that port?
> I've seen that when connecting a 2.5" HDD when the PSU doesn't have
> enough power to spin up the HDD as well.
This TV box have 2 USB port.
One port is connected to the external hub
(this hub connecned USB keyboard and mouse from PC).

Testing.

[Martin Blumenstingl]

On Sun, May 7, 2017 at 11:23 PM, Oleg <balbes-150@yandex.ru> wrote:
>
>> this sounds innocent at first but actually it's crucial for MMC (at
>> least in the current M8S configuration). PWM_E is used to generate the
>> 32.768 kHz clock for the wifi chip. so without CONFIG_PWM_MESON the
>> pwm_ef node won't get probed, meaning that a dependency of the mmc
>> controller is missing.
>> I'll fix that as well next weekend (it also has to be enabled in
>> multi_v7_defconfig)
>
> I found in the configuration CONFIG_PWM_MESON and put =y.
>  Or you need to add code / patch in the source code ?
adding the configuration should be enough - Neil did a good job with
the actual driver code (it's working fine for me :))

>> this looks suspicious, do you have anything connected to that port?
>> I've seen that when connecting a 2.5" HDD when the PSU doesn't have
>> enough power to spin up the HDD as well.
>
> This TV box have 2 USB port.
> One port is connected to the external hub
> (this hub connecned USB keyboard and mouse from PC).
I am assuming you are testing on the MXIII Plus [0]:
the S812 SoC (just like all other Amlogic SoCs) comes with two USB controllers:
- one for the OTG port
- a second one which only acts in host mode -> this is typically
connected to an internal hub (often through a GL852 USB hub
controller) which then provides more than one port

I had a quick look at the .dts files - on my Akaso M8S GPIOZ_1 is not
connected anywhere (at least toggling the GPIO doesn't change anything
in terms of USB VBUS signal).
however, your board has: gpio-vbus-power = "GPIOZ_1";
it's very likely that the GL852 hub is powered off by default and is
powered on by enabling GPIOZ_1
but since my .dts is not enabling GPIOZ_1 the hub stays powered off
and USB is not working for you
(in other words: this will require additional changes in the .dts to
make it work)


Regards,
Martin

[0] http://www.tronsmart.com/products/tronsmart-mxiii-plus-2g/8g-quad-core-android-tv-box

Testing.

[Oleg]

> adding the configuration should be enough - Neil did a good job with
> the actual driver code (it's working fine for me :))
I added to config this variable. This kernel changed the behavior.
Now there is a reaction to change :)

https://yadi.sk/i/rzF14Hx03HqeRh

> I had a quick look at the .dts files - on my Akaso M8S GPIOZ_1 is not
> connected anywhere (at least toggling the GPIO doesn't change anything
> in terms of USB VBUS signal).
> however, your board has: gpio-vbus-power = "GPIOZ_1";
> it's very likely that the GL852 hub is powered off by default and is
> powered on by enabling GPIOZ_1
> but since my .dts is not enabling GPIOZ_1 the hub stays powered off
> and USB is not working for you
> (in other words: this will require additional changes in the .dts to
> make it work)
I found dtb to kernel 3.14 the string

gpio-vbus-power = "GPIOZ_1";

You can simply copy it to the unit or it needs to change according to 
certain rules ?

&usb0 {
     status = "okay";
};

S805/S812 Device Tree upstreaming (was: Testing.)

[Andreas Färber]

Hi,

Am 08.05.2017 um 11:42 schrieb Oleg:
>> I had a quick look at the .dts files - on my Akaso M8S GPIOZ_1 is not
>> connected anywhere (at least toggling the GPIO doesn't change anything
>> in terms of USB VBUS signal).
>> however, your board has: gpio-vbus-power = "GPIOZ_1";
>> it's very likely that the GL852 hub is powered off by default and is
>> powered on by enabling GPIOZ_1
>> but since my .dts is not enabling GPIOZ_1 the hub stays powered off
>> and USB is not working for you
>> (in other words: this will require additional changes in the .dts to
>> make it work)
> I found dtb to kernel 3.14 the string
> 
> gpio-vbus-power = "GPIOZ_1";
> 
> You can simply copy it to the unit or it needs to change according to
> certain rules ?

You need to read the latest bindings documentation, for example:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

Testing.

[Oleg]

> I am currently trying to improve support for the older (32-bit) Meson SoCs.
> Unfortunately I only have a device with S812 (Meson8m2) - do you have
> any boards with Meson8 (S802) or Meson8b (S805) SoC? we could team up
> and add mainline support for your boards
>
> current status on my Meson8m2 device is:
> - USB works (I only tested host mode)
> - SD card can be read and written
> - ethernet (my device has 10/100Mbit/s only) works
>
>
> Regards,
> Martin
Another user connected to the test.
Perhaps You may have some additional instructions for its tests.
This is a topic with the discussion.

https://forum.armbian.com/index.php?/topic/3023-armbian-for-amlogic-s802s812/&do=findComment&comment=31591

Testing.

[Tobias Baumann]

hi martin

oleg (balbes150)  from armbian forum told me you could need some help

iam new to linux but i can test images and files for you

my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT 
Combo HDMI 2xUSB

( run as server for USB Printer and Sane server for canon scanner)

at the moment i use the armbian unbuntu rom from oleg with 3.10.99 
kernel (14 04 2017 ) with working wifi usb and internet also i could run 
a successful test the 4.11 kernel

my project now is to control the front LED

but there is a problem  oleg send my the dts for led but without gpio .

maybe you can assist

thanks Tobias

PS: i am from Germany so i am more comfortable and faster in german


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
https://www.avast.com/antivirus

Testing.

[Martin Blumenstingl]

Hi Tobias,

On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
<017623705678@o2online.de> wrote:
> hi martin
>
> oleg (balbes150)  from armbian forum told me you could need some help
>
> iam new to linux but i can test images and files for you
>
> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT
> Combo HDMI 2xUSB
>
> ( run as server for USB Printer and Sane server for canon scanner)
>
> at the moment i use the armbian unbuntu rom from oleg with 3.10.99 kernel
> (14 04 2017 ) with working wifi usb and internet also i could run a
> successful test the 4.11 kernel
disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel

> my project now is to control the front LED
what are you trying to control exactly?

> but there is a problem  oleg send my the dts for led but without gpio .
my m8s.dts doesn't use a GPIO because the LED is connected to
GPIO_TEST_N which can also be controlled by one of the PWM controllers
(this allows dimming the LED to a certain level, but in my case the
LED is a dual-color LED with blue and red: the further you reduce the
brightness of the (blue) LED the more you see of the red one -> if you
turn off the blue LED it turns red)

> maybe you can assist
>
> thanks Tobias
>
> PS: i am from Germany so i am more comfortable and faster in german
>
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
> https://www.avast.com/antivirus
>
>
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic

Testing.

[raptorsds]

Hi Martin

> Hi Tobias,
>
> On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
> <017623705678@o2online.de> wrote:
>> hi martin
>>
>> oleg (balbes150)  from armbian forum told me you could need some help
>>
>> iam new to linux but i can test images and files for you
>>
>> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT
>> Combo HDMI 2xUSB
>>
>> ( run as server for USB Printer and Sane server for canon scanner)
>>
>> at the moment i use the armbian unbuntu rom from oleg with 3.10.99 kernel
>> (14 04 2017 ) with working wifi usb and internet also i could run a
>> successful test the 4.11 kernel
> disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel

But  maybe than  i can help by 4.11 kernel test for older devices
>> my project now is to control the front LED
> what are you trying to control exactly?

red = stop
blue = boot/start
red/blue (maybe dimming) = run
blinking = update (maybe)

>
>> but there is a problem  oleg send my the dts for led but without gpio .
> my m8s.dts doesn't use a GPIO because the LED is connected to
> GPIO_TEST_N which can also be controlled by one of the PWM controllers
> (this allows dimming the LED to a certain level, but in my case the
> LED is a dual-color LED with blue and red: the further you reduce the
> brightness of the (blue) LED the more you see of the red one -> if you
> turn off the blue LED it turns red)

I though  " GPIO_TEST_N " was a placeholder .  I havent any trigger at 
/sys/class/leds , how  can i controll PWM for LED
>> maybe you can assist
>>
>> thanks Tobias
>>
>> PS: i am from Germany so i am more comfortable and faster in german
>>
>>
>> ---
>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
>> https://www.avast.com/antivirus
>>
>>
>>
>> _______________________________________________
>> linux-amlogic mailing list
>> linux-amlogic at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic

Testing.

[Martin Blumenstingl]

On Sat, May 27, 2017 at 4:57 PM, raptorsds <raptorsds@googlemail.com> wrote:
> Hi Martin
>
>> Hi Tobias,
>>
>> On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
>> <017623705678@o2online.de> wrote:
>>>
>>> hi martin
>>>
>>> oleg (balbes150)  from armbian forum told me you could need some help
>>>
>>> iam new to linux but i can test images and files for you
>>>
>>> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT
>>> Combo HDMI 2xUSB
>>>
>>> ( run as server for USB Printer and Sane server for canon scanner)
>>>
>>> at the moment i use the armbian unbuntu rom from oleg with 3.10.99 kernel
>>> (14 04 2017 ) with working wifi usb and internet also i could run a
>>> successful test the 4.11 kernel
>>
>> disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel
>
>
> But  maybe than  i can help by 4.11 kernel test for older devices
you need to be aware of the fact that my kernel patches are experimental.
what you get is:
- one CPU core at the frequency set by the bootloader
- maybe USB (Oleg has problems with it while it works for me)
- maybe ethernet (again, Oleg has problems while it works for me)
- SD card
- front LED

basically everything else is broken (wifi, CPU cores 2-4, cpu frequency
scaling, etc.). I even managed to corrupt u-boot when I was testing my
NAND driver.

what "older" devices do you have? and do you have access to the serial
console of these devices?

>>>
>>> my project now is to control the front LED
>>
>> what are you trying to control exactly?
>
>
> red = stop
> blue = boot/start
> red/blue (maybe dimming) = run
> blinking = update (maybe)
let me explain how where the LED is controlled currently:
- red LED turns on automatically (probably because it's wired to VCC)
when the device is powered on
- u-boot turns on the blue LED
- (kernel boots)
- the kernel can now control the LED partially (as explained in my
previous mail, you can only set the "mix" between red and blue - you
can't turn it off)

so with another kernel you can only change the LED color from the
point on where the kernel is started. you'll have no control over it
(without additional work on the u-boot side) for the first seconds
after powering on the device.

>>
>>> but there is a problem  oleg send my the dts for led but without gpio .
>>
>> my m8s.dts doesn't use a GPIO because the LED is connected to
>> GPIO_TEST_N which can also be controlled by one of the PWM controllers
>> (this allows dimming the LED to a certain level, but in my case the
>> LED is a dual-color LED with blue and red: the further you reduce the
>> brightness of the (blue) LED the more you see of the red one -> if you
>> turn off the blue LED it turns red)
>
>
> I though  " GPIO_TEST_N " was a placeholder .  I havent any trigger at
> /sys/class/leds , how  can i controll PWM for LED
are you testing this on a 3.10/3.14 kernel or on a kernel with my
patches? I think the Amlogic kernel does not use the kernel's LED
framework, so the LEDs are not exposed in /sys/class/leds
if it's one of my kernels (I think Oleg has compiled some images with
them) then please post the kernel log (dmesg)

>>> maybe you can assist
>>>
>>> thanks Tobias
>>>
>>> PS: i am from Germany so i am more comfortable and faster in german
>>>
>>>
>>> ---
>>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
>>> https://www.avast.com/antivirus
>>>
>>>
>>>
>>> _______________________________________________
>>> linux-amlogic mailing list
>>> linux-amlogic at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>
>> _______________________________________________
>> linux-amlogic mailing list
>> linux-amlogic at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
>

Testing.

[raptorsds]

Am 27.05.2017 um 18:08 schrieb Martin Blumenstingl:
> On Sat, May 27, 2017 at 4:57 PM, raptorsds <raptorsds@googlemail.com> wrote:
>> Hi Martin
>>
>>> Hi Tobias,
>>>
>>> On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
>>> <017623705678@o2online.de> wrote:
>>>> hi martin
>>>>
>>>> oleg (balbes150)  from armbian forum told me you could need some help
>>>>
>>>> iam new to linux but i can test images and files for you
>>>>
>>>> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT
>>>> Combo HDMI 2xUSB
>>>>
>>>> ( run as server for USB Printer and Sane server for canon scanner)
>>>>
>>>> at the moment i use the armbian unbuntu rom from oleg with 3.10.99 kernel
>>>> (14 04 2017 ) with working wifi usb and internet also i could run a
>>>> successful test the 4.11 kernel
>>> disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel
>>
>> But  maybe than  i can help by 4.11 kernel test for older devices
> you need to be aware of the fact that my kernel patches are experimental.
> what you get is:
> - one CPU core at the frequency set by the bootloader
> - maybe USB (Oleg has problems with it while it works for me)
> - maybe ethernet (again, Oleg has problems while it works for me)
> - SD card
> - front LED
>
> basically everything else is broken (wifi, CPU cores 2-4, cpu frequency
> scaling, etc.). I even managed to corrupt u-boot when I was testing my
> NAND driver.
>
> what "older" devices do you have? and do you have access to the serial
> console of these devices?

Yes Serial console  only my s812 box ,
>>>> my project now is to control the front LED
>>> what are you trying to control exactly?
>>
>> red = stop
>> blue = boot/start
>> red/blue (maybe dimming) = run
>> blinking = update (maybe)
> let me explain how where the LED is controlled currently:
> - red LED turns on automatically (probably because it's wired to VCC)
> when the device is powered on
> - u-boot turns on the blue LED
> - (kernel boots)
> - the kernel can now control the LED partially (as explained in my
> previous mail, you can only set the "mix" between red and blue - you
> can't turn it off)
>
> so with another kernel you can only change the LED color from the
> point on where the kernel is started. you'll have no control over it
> (without additional work on the u-boot side) for the first seconds
> after powering on the device.
ok thank you for your explanation , it would be great when after kernelk 
boot (maybe inside rc.local) the LED will have a color change


>>>> but there is a problem  oleg send my the dts for led but without gpio .
>>> my m8s.dts doesn't use a GPIO because the LED is connected to
>>> GPIO_TEST_N which can also be controlled by one of the PWM controllers
>>> (this allows dimming the LED to a certain level, but in my case the
>>> LED is a dual-color LED with blue and red: the further you reduce the
>>> brightness of the (blue) LED the more you see of the red one -> if you
>>> turn off the blue LED it turns red)
>>
>> I though  " GPIO_TEST_N " was a placeholder .  I havent any trigger at
>> /sys/class/leds , how  can i controll PWM for LED
> are you testing this on a 3.10/3.14 kernel or on a kernel with my
> patches? I think the Amlogic kernel does not use the kernel's LED
> framework, so the LEDs are not exposed in /sys/class/leds
> if it's one of my kernels (I think Oleg has compiled some images with
> them) then please post the kernel log (dmesg)

yes i use 3.10.99 kernel from the image from oleg with a dtb files with 
your Led infos about "gpio test n"
i also found a older info about system LED

https://lists.freebsd.org/pipermail/freebsd-arm/2015-February/010126.html

there is a info about gpio ao 13

i send you a private mail with my dmesg with oleg dts file with led line


>>>> maybe you can assist
>>>>
>>>> thanks Tobias
>>>>
>>>> PS: i am from Germany so i am more comfortable and faster in german
>>>>
>>>>
>>>> ---
>>>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
>>>> https://www.avast.com/antivirus
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> linux-amlogic mailing list
>>>> linux-amlogic at lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>> _______________________________________________
>>> linux-amlogic mailing list
>>> linux-amlogic at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>

Testing.

[Martin Blumenstingl]

On Sat, May 27, 2017 at 8:06 PM, raptorsds <raptorsds@googlemail.com> wrote:
>
>
> Am 27.05.2017 um 18:08 schrieb Martin Blumenstingl:
>>
>> On Sat, May 27, 2017 at 4:57 PM, raptorsds <raptorsds@googlemail.com>
>> wrote:
>>>
>>> Hi Martin
>>>
>>>> Hi Tobias,
>>>>
>>>> On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
>>>> <017623705678@o2online.de> wrote:
>>>>>
>>>>> hi martin
>>>>>
>>>>> oleg (balbes150)  from armbian forum told me you could need some help
>>>>>
>>>>> iam new to linux but i can test images and files for you
>>>>>
>>>>> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI
>>>>> BT
>>>>> Combo HDMI 2xUSB
>>>>>
>>>>> ( run as server for USB Printer and Sane server for canon scanner)
>>>>>
>>>>> at the moment i use the armbian unbuntu rom from oleg with 3.10.99
>>>>> kernel
>>>>> (14 04 2017 ) with working wifi usb and internet also i could run a
>>>>> successful test the 4.11 kernel
>>>>
>>>> disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel
>>>
>>>
>>> But  maybe than  i can help by 4.11 kernel test for older devices
>>
>> you need to be aware of the fact that my kernel patches are experimental.
>> what you get is:
>> - one CPU core at the frequency set by the bootloader
>> - maybe USB (Oleg has problems with it while it works for me)
>> - maybe ethernet (again, Oleg has problems while it works for me)
>> - SD card
>> - front LED
>>
>> basically everything else is broken (wifi, CPU cores 2-4, cpu frequency
>> scaling, etc.). I even managed to corrupt u-boot when I was testing my
>> NAND driver.
>>
>> what "older" devices do you have? and do you have access to the serial
>> console of these devices?
>
>
> Yes Serial console  only my s812 box ,
>>>>>
>>>>> my project now is to control the front LED
>>>>
>>>> what are you trying to control exactly?
>>>
>>>
>>> red = stop
>>> blue = boot/start
>>> red/blue (maybe dimming) = run
>>> blinking = update (maybe)
>>
>> let me explain how where the LED is controlled currently:
>> - red LED turns on automatically (probably because it's wired to VCC)
>> when the device is powered on
>> - u-boot turns on the blue LED
>> - (kernel boots)
>> - the kernel can now control the LED partially (as explained in my
>> previous mail, you can only set the "mix" between red and blue - you
>> can't turn it off)
>>
>> so with another kernel you can only change the LED color from the
>> point on where the kernel is started. you'll have no control over it
>> (without additional work on the u-boot side) for the first seconds
>> after powering on the device.
>
> ok thank you for your explanation , it would be great when after kernelk
> boot (maybe inside rc.local) the LED will have a color change
>
>
>>>>> but there is a problem  oleg send my the dts for led but without gpio .
>>>>
>>>> my m8s.dts doesn't use a GPIO because the LED is connected to
>>>> GPIO_TEST_N which can also be controlled by one of the PWM controllers
>>>> (this allows dimming the LED to a certain level, but in my case the
>>>> LED is a dual-color LED with blue and red: the further you reduce the
>>>> brightness of the (blue) LED the more you see of the red one -> if you
>>>> turn off the blue LED it turns red)
>>>
>>>
>>> I though  " GPIO_TEST_N " was a placeholder .  I havent any trigger at
>>> /sys/class/leds , how  can i controll PWM for LED
>>
>> are you testing this on a 3.10/3.14 kernel or on a kernel with my
>> patches? I think the Amlogic kernel does not use the kernel's LED
>> framework, so the LEDs are not exposed in /sys/class/leds
>> if it's one of my kernels (I think Oleg has compiled some images with
>> them) then please post the kernel log (dmesg)
>
>
> yes i use 3.10.99 kernel from the image from oleg with a dtb files with your
> Led infos about "gpio test n"
like I said in a previous mail, I can't say much about the 3.10/3.14
kernel - it contains a lot of "custom" code which duplicates
functionality that it already provided by various frameworks inside
the Linux kernel. this is also the reason why your LED doesn't show up
in /sys/class/leds

> i also found a older info about system LED
>
> https://lists.freebsd.org/pipermail/freebsd-arm/2015-February/010126.html
>
> there is a info about gpio ao 13
the LED pin is board specific - GPIOAO_13 is correct for the Odroid-C1

> i send you a private mail with my dmesg with oleg dts file with led line
that is a kernel log and dts files from a 3.10 kernel. you can have a
look at the "aml_sysled" code from their 3.10 kernel, see [0]
but I'm a afraid this is all I can do for you here

if you switch to one of Oleg's images with my patches then the LED
will show up in /sys/class/leds, but like I mentioned previously all
this is pretty experimental


Regards,
Martin


[0] https://github.com/endlessm/linux-meson/blob/master/drivers/amlogic/led/aml_sysled.c