[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJKOXPfQ3nXHVYXUn0iDfzVQc+ML1sSCz3NG_bwUw=WDK0id_w@mail.gmail.com>
Date: Thu, 28 Sep 2017 08:21:26 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Linus Lüssing <linus.luessing@...3.blue>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
Russell King <linux@...linux.org.uk>,
Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver
On Thu, Sep 28, 2017 at 4:40 AM, Linus Lüssing <linus.luessing@...3.blue> wrote:
> The Odroid U3 (Exynos 4412 based) for instance needs this driver,
> otherwise its USB hub will not come up.
>
> exynos_defconfig already has this enabled as built-in, too. So
> just doing the same here in multi_v7_defconfig.
>
> Signed-off-by: Linus Lüssing <linus.luessing@...3.blue>
>
> ---
> Thanks to Tobias Jakobi, who indirectly made me aware of why USB
> did not work for me.
>
> arch/arm/configs/multi_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Partially this was part of my patchset fixing powersequence for
usb3503 and lan9730:
https://patchwork.kernel.org/patch/9502939/
but that patch waits still for power sequence.
Anyway please define this as a module (unless it can't... but it
worked in my case).
Best regards,
Krzysztof
Powered by blists - more mailing lists