linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas saenz julienne <nsaenz@kernel.org>
To: Michael Stapelberg <michael+lkml@stapelberg.ch>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Vinod Koul <vkoul@kernel.org>,
	 Bjorn Andersson <bjorn.andersson@linaro.org>,
	Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: Commit 8ae030c34 breaks USB on the Raspberry Pi 4
Date: Wed, 15 Sep 2021 09:42:32 +0200	[thread overview]
Message-ID: <03a8235aff7965d7b451d1d5792620567a9c6155.camel@kernel.org> (raw)
In-Reply-To: <CANnVG6m-1oceumzYUF-5zDPKoZA+GgtoU1iVBkQiURcAVSg6iw@mail.gmail.com>

Hi Michael,

On Wed, 2021-09-15 at 08:33 +0200, Michael Stapelberg wrote:
> Thanks for your mail.
> 
> My system does not use any Linux kernel modules (=m), all required
> code is compiled into the kernel itself (=y).
> The root file system does not contain any .ko files.

Are you building your own kernels? Then I suggest to configure the
raspberrypi-reset driver as builtin (=y) so it's available in your kernel
image.

Could you provide more information on how your system/rootfs is built and
setup?

Regards,
Nicolas


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-09-15  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 21:28 Commit 8ae030c34 breaks USB on the Raspberry Pi 4 Michael Stapelberg
2021-09-14 21:47 ` Florian Fainelli
2021-09-15  6:33   ` Michael Stapelberg
2021-09-15  7:42     ` nicolas saenz julienne [this message]
2021-09-15  7:55       ` Michael Stapelberg
2021-09-15  8:54         ` nicolas saenz julienne
2021-09-18  9:28           ` Michael Stapelberg

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=03a8235aff7965d7b451d1d5792620567a9c6155.camel@kernel.org \
    --to=nsaenz@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=michael+lkml@stapelberg.ch \
    --cc=stefan.wahren@i2se.com \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).