From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: musb is broken in master
Date: Tue, 18 Feb 2020 12:48:13 +0100 [thread overview]
Message-ID: <43978130-6f7d-759c-ef63-a005cb6f0934@pengutronix.de> (raw)
In-Reply-To: <CAGm1_ktTGx1MMY-jcbVrOwnwqHeHm8Qe2f2iRxEQxmY0y5HM4g@mail.gmail.com>
On 2/18/20 12:19 PM, Yegor Yefremov wrote:
> Hello Ahmad,
>
> On Tue, Feb 18, 2020 at 11:57 AM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>>
>> Hello Yegor,
>>
>> On 2/18/20 10:58 AM, Yegor Yefremov wrote:
>>> I have bisected the musb driver on am335x (baltos system
>>> arch/arm/dts/am335x-baltos-minimal.dts) from v2019.11.0 and this is
>>> the result:
>>>
>>> 574eed3f6fcf056aa4c9e46c4b5224e3f7844d8d is the first bad commit
>>> commit 574eed3f6fcf056aa4c9e46c4b5224e3f7844d8d
>>> Author: Sascha Hauer <s.hauer@pengutronix.de>
>>> Date: Thu Dec 19 05:46:54 2019 +0100
>>>
>>> dts: update to v5.5-rc1
>>>
>>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>>>
>>> :040000 040000 4f6416a5af14d6328ef2c8ac46d9ac4a17a37404
>>> 525e33dda1e735ef2f633f4d99c501ba938a7263 M dts
>>>
>>> I need only the host functionality to mount a USB drive. My defconfig
>>> can be found here [1].
>>>
>>> Any idea what could have happened?
>>
>> git log v5.4..v5.5-rc1 arch/arm/boot/dts/am335x*.dtsi
>> gives me kernel commit 12afc0cf81 ("ARM: dts: Drop pointless status changing for am3 musb").
>> Does reverting it fix the issue for you?
>
> Yes, it does. Though the revert result is a little bit ugly i.e. at
> least one conflict.
yes, it's not meant as permanent solution.
Which status = "okay" is the one that 'fixes' it?
> But when I start the kernel 5.6-rc2 that already incorporates these
> DTS changes, I have no problems with USB. So far only the barebox is
> affected by this change.
Possibly a device driver in barebox for the now-disabled peripheral
turns on a clock, enables a regulator, toggles a reset or initializes
some register that also affects the USB working at all.
Best course of action would be to check which driver it is, check whether
Linux uses it, comment out stuff to find what the magic sauce is that
the driver does and add that to the driver that misses it.
(sometimes it's just that the device tree binding changed. In that case,
you can either patch in a missing property in arch/arm/dts or patch
barebox drivers to accept the new binding as well)
Cheers
Ahmad
>
> Cheers,
> Yegor
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-02-18 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 9:58 Yegor Yefremov
2020-02-18 10:57 ` Ahmad Fatoum
2020-02-18 11:19 ` Yegor Yefremov
2020-02-18 11:48 ` Ahmad Fatoum [this message]
2020-02-24 11:09 ` Yegor Yefremov
2020-02-24 11:50 ` Ahmad Fatoum
2020-02-24 11:54 ` Yegor Yefremov
2020-02-24 11:55 ` Yegor Yefremov
2020-02-24 12:02 ` Ahmad Fatoum
2020-02-24 14:08 ` Yegor Yefremov
2020-02-25 17:13 ` Ahmad Fatoum
2020-02-26 7:27 ` Yegor Yefremov
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=43978130-6f7d-759c-ef63-a005cb6f0934@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=yegorslists@googlemail.com \
/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