From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Kukjin Kim <kgene@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver
Date: Thu, 28 Sep 2017 12:43:51 +0200 [thread overview]
Message-ID: <20170928104351.GE6726@otheros> (raw)
In-Reply-To: <CAJKOXPfQ3nXHVYXUn0iDfzVQc+ML1sSCz3NG_bwUw=WDK0id_w@mail.gmail.com>
Hi Krzysztof,
Thanks for your quick reply!
On Thu, Sep 28, 2017 at 08:21:26AM +0200, Krzysztof Kozlowski wrote:
> [...]
> Anyway please define this as a module (unless it can't... but it
> worked in my case).
In that case you used an initrd, right? I see various cases of USB
built-ins, like CONFIG_USB_STORAGE=y, CONFIG_USB_DWC2=y and so on in
multi_v7_defconfig. So my impression was that multi_v7_defconfig was
supposed to allow booting a rootfs from a USB storage device even
without an initrd.
Let me know if that impression is wrong though, I'll happily resend
(and test) the patch with CONFIG_USB_HSIC_USB3503=m then :-).
Regards, Linus
WARNING: multiple messages have this Message-ID (diff)
From: linus.luessing@c0d3.blue (Linus Lüssing)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver
Date: Thu, 28 Sep 2017 12:43:51 +0200 [thread overview]
Message-ID: <20170928104351.GE6726@otheros> (raw)
In-Reply-To: <CAJKOXPfQ3nXHVYXUn0iDfzVQc+ML1sSCz3NG_bwUw=WDK0id_w@mail.gmail.com>
Hi Krzysztof,
Thanks for your quick reply!
On Thu, Sep 28, 2017 at 08:21:26AM +0200, Krzysztof Kozlowski wrote:
> [...]
> Anyway please define this as a module (unless it can't... but it
> worked in my case).
In that case you used an initrd, right? I see various cases of USB
built-ins, like CONFIG_USB_STORAGE=y, CONFIG_USB_DWC2=y and so on in
multi_v7_defconfig. So my impression was that multi_v7_defconfig was
supposed to allow booting a rootfs from a USB storage device even
without an initrd.
Let me know if that impression is wrong though, I'll happily resend
(and test) the patch with CONFIG_USB_HSIC_USB3503=m then :-).
Regards, Linus
next prev parent reply other threads:[~2017-09-28 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 2:40 [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver Linus Lüssing
2017-09-28 2:40 ` Linus Lüssing
2017-09-28 2:40 ` Linus Lüssing
2017-09-28 6:21 ` Krzysztof Kozlowski
2017-09-28 6:21 ` Krzysztof Kozlowski
2017-09-28 10:43 ` Linus Lüssing [this message]
2017-09-28 10:43 ` Linus Lüssing
2017-09-28 12:22 ` Krzysztof Kozlowski
2017-09-28 12:22 ` Krzysztof Kozlowski
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=20170928104351.GE6726@otheros \
--to=linus.luessing@c0d3.blue \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tjakobi@math.uni-bielefeld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.