From: Otto Meier <gf435@gmx.net>
To: Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, u-boot-amlogic@groups.io,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [BUG]odroid-c2 does not hotplug usb-devices
Date: Mon, 7 Dec 2020 13:43:43 +0100 [thread overview]
Message-ID: <dd160e55-55e9-1c41-afcb-22990a05a86b@gmx.net> (raw)
In-Reply-To: <0d05671d-b5f4-55e4-f5bd-58410cc92d08@baylibre.com>
Am 07.12.20 um 13:29 schrieb Neil Armstrong:
> Hi,
>
> (Please CC u-boot-amlogic@groups.io when U-Boot is concerned)
>
> On 07/12/2020 13:19, Otto Meier wrote:
>> Hi Martin,
>>
>>
>> I did a lot of googling this weekend and found some interesting problems with
>> odroid-c2.
>>
>> 1. booting from emmc stop after u-boot 2020.04 (this hits me also)
>
> Indeed, this already has been reported, but the root cause is unknown
>
>> 2. usb did not work with newer kernels.
>>
>> This gaves me the idea that something in the configuration of the s905 soc
>> is not ok.
>>
>> here: https://forum.libreelec.tv/thread/12330-balbes150-le-images-with-kodi-19-for-s9xxx/?postID=147212#post147212
>> and here: https://lists.denx.de/pipermail/u-boot/2020-November/thread.html
>>
>> in https://groups.io/g/u-boot-amlogic/topic/77816805#661 some problems in pinctrl related to booting from emmc is discussed.
>>
>> i found that commit dd5f2351e99aad8fcbedbc1305b8b51b09952336 of u-boot
>> rendered the situation for odroid-c2 bad.
>>
>> i gave the following patch on Top of commit ee1e04558ff8c8ed812b986939447f129bb0b0bb of u-boot
>> a try ad it fixes the odroid-c2 boot issue.
>>
>> --- u-boot.git/arch/arm/dts/meson-gxbb.dtsi.orig 2020-11-27 17:20:04.624193561 +0100
>> +++ u-boot.git/arch/arm/dts/meson-gxbb.dtsi 2020-11-27 17:23:18.472088934 +0100
>> @@ -403,36 +403,33 @@
>> gpio-ranges = <&pinctrl_periphs 0 0 119>;
>> };
>>
>> - emmc_pins: emmc {
>> - mux-0 {
>> - groups = "emmc_nand_d07",
>> - "emmc_cmd";
>> - function = "emmc";
>> - bias-pull-up;
>> - };
>>
>> - mux-1 {
>> - groups = "emmc_clk";
>> - function = "emmc";
>> - bias-disable;
>> - };
>> - };
>> + emmc_pins: emmc {
>> + mux {
>> + groups = "emmc_nand_d07",
>> + "emmc_cmd",
>> + "emmc_clk";
>> + function = "emmc";
>> + };
>> + };
>>
>> - emmc_ds_pins: emmc-ds {
>> - mux {
>> - groups = "emmc_ds";
>> - function = "emmc";
>> - bias-pull-down;
>> - };
>> - };
>> + emmc_ds_pins: emmc-ds {
>> + mux {
>> + groups = "emmc_ds";
>> + function = "emmc";
>> + };
>> + };
>>
>> - emmc_clk_gate_pins: emmc_clk_gate {
>> - mux {
>> - groups = "BOOT_8";
>> - function = "gpio_periphs";
>> - bias-pull-down;
>> - };
>> - };
>> + emmc_clk_gate_pins: emmc_clk_gate {
>> + mux {
>> + groups = "BOOT_8";
>> + function = "gpio_periphs";
>> + };
>> + cfg-pull-down {
>> + pins = "BOOT_8";
>> + bias-pull-down;
>> + };
>> + };
>>
>> nor_pins: nor {
>> mux {
>>
>>
>>
>> So with the latest u-boot and the kernel from https://github.com/chewitt/linux/tree/amlogic-5.10.y
>> commit 725fc8df7898102f9031ba2075f763884ffa3ee8 everything is working again.
>> USB does hotplugging as expected.
>
> So, this fixes USB under Linux ?? It's not clear
>
> Neil
The above patch fixes booting from emmc for me.
Using a newer uboot then 2020.04 is mandatory for using the above mentioned kernel.
The usb issue, i had with earlier kernels from the above mentioned tree.
Hope that clearifies it. I wanted to run the newest kernel on my system which boots from emmc.
I think these issues are probaly independant but in my system they did interfere.
Best regards
Otto
>
>>
>> For me this make it work again. But i`m sorry, I don´t know what would be a real fix.
>>
>>
>>
>>
>>
>>
>> Am 05.12.20 um 20:55 schrieb Martin Blumenstingl:
>>> Hi Otto,
>>>
>>> On Sat, Dec 5, 2020 at 6:40 PM Otto Meier <gf435@gmx.net> wrote:
>>>>
>>>> Hi Martin,
>>>>
>>>> i have tried your second notice. but it does'nt solve the issue.
>>>> if at leased on device is pluged in new devices are detected. if
>>>> all devices have been removed, no new device will be detected anymore.
>>> thanks for trying this out and for reporting back.
>>> can you please also test if running "lsusb -vvv" (as root) makes the
>>> devices show up?
>>>
>>> background info: the Amlogic Meson GXBB SoC on your Odroid-C2 board
>>> uses a "dwc2" USB 2.0 controller.
>>> I don't have any GXBB based board, but my Odroid-C1+ uses the same
>>> controller and overall setup. There I can reproduce the problem you
>>> are seeing.
>>>
>>> I am not sure which part of the "infrastructure" (on-board 4-port USB
>>> hub, dwc2 controller, ...) is causing this issue.
>>> My suggestion is to involve the linux-usb mailing list and dwc2 driver
>>> maintainer:
>>> - Minas Harutyunyan <hminas@synopsys.com> (dwc2 driver maintainer)
>>> - linux-usb@vger.kernel.org (usb mailing list)
>>>
>>> In the past they provided information and helped to debug issues.
>>> Please also keep me Cc'ed so I can help with any Amlogic specific
>>> questions, drivers, etc.
>>>
>>>
>>> Best regards,
>>> Martin
>>>
>
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-12-07 12:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 17:09 Otto Meier
2020-12-05 11:54 ` Martin Blumenstingl
2020-12-05 17:40 ` Otto Meier
2020-12-05 19:55 ` Martin Blumenstingl
2020-12-07 12:19 ` Otto Meier
2020-12-07 12:29 ` Neil Armstrong
2020-12-07 12:43 ` Otto Meier [this message]
2020-12-13 18:46 ` Martin Blumenstingl
2020-12-14 19:33 ` Otto Meier
2020-12-19 13:58 ` Martin Blumenstingl
2020-12-19 18:41 ` Otto Meier
2020-12-19 19:53 ` Anand Moon
2020-12-19 22:31 ` Martin Blumenstingl
2020-12-20 10:28 ` Otto Meier
2020-12-20 13:46 ` Anand Moon
2020-12-20 14:33 ` Martin Blumenstingl
2020-12-21 14:15 ` Anand Moon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd160e55-55e9-1c41-afcb-22990a05a86b@gmx.net \
--to=gf435@gmx.net \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®