public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Cyril Brulebois <kibi@debian.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	bcm-kernel-feedback-list@broadcom.com, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: dts: bcm2711-rpi-cm4-io: Enable xHCI host
Date: Mon, 27 Nov 2023 17:56:11 +0100	[thread overview]
Message-ID: <d22e404b-30e5-4c1f-add0-77c0bb88351d@gmx.net> (raw)
In-Reply-To: <20231127130225.lyk2jngfru5lw6sd@mraw.org>

Hi Cyril,

Am 27.11.23 um 14:02 schrieb Cyril Brulebois:
> Stefan Wahren <wahrenst@gmx.net> (2023-11-27):
>> Could you please provide the following information:
>>
>> - settings of config.txt
> Here you go:
>
>      arm_64bit=1
>      enable_uart=1
>      upstream_kernel=1
>
>      kernel=vmlinuz-6.6.0+
>      initramfs initrd.img-6.6.0+
>
>      enable_jtag_gpio=1
>      force_turbo=1
can you please check what happens if you add the following to config.txt:

[cm4]
otg_mode=1

>
>> - VC firmware version
> This is pieeprom-2023-01-11.bin
>
> I know there's pieeprom-2023-05-11.bin as well, but I've been keeping
> the former as a constant throughout the PCIe patch series testing once
> I realized how critical it was (old beta EEPROM versions found in some
> CM4s made everything much harder initially).
>
> In case the config matters:
>
>      [all]
>      BOOT_UART=0
>      WAKE_ON_GPIO=1
>      POWER_OFF_ON_HALT=0
>      BOOT_ORDER=0xf25641
>      ENABLE_SELF_UPDATE=1
>
>> - did you use arm64/defconfig or something special?
> I'm using a “distribution config”, starting from the latest arm64 config
> found in Debian unstable (6.5.10-1), and applying `make oldconfig`.
>
> You'll find it attached.
>
>
> Cheers,


  parent reply	other threads:[~2023-11-27 16:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26  2:56 [PATCH 0/3] ARM: dts: bcm2711-rpi-cm4-io: Enable xHCI host Stefan Wahren
2023-11-26  2:56 ` [PATCH 1/3] dt-bindings: usb: xhci: Add optional power-domains Stefan Wahren
2023-11-26 11:14   ` Conor Dooley
2023-11-26  2:56 ` [PATCH 2/3] ARM: dts: bcm2711: Add generic xHCI Stefan Wahren
2023-11-26  2:56 ` [PATCH 3/3] ARM: dts: bcm2711-rpi-cm4-io: Enable xHCI host Stefan Wahren
2023-11-27  0:34 ` [PATCH 0/3] " Cyril Brulebois
2023-11-27 10:57   ` Stefan Wahren
2023-11-27 11:55     ` Cyril Brulebois
2023-11-27 12:38       ` Stefan Wahren
2023-11-27 13:02         ` Cyril Brulebois
2023-11-27 15:16           ` Stefan Wahren
2023-11-27 15:59             ` Cyril Brulebois
2023-11-27 16:56           ` Stefan Wahren [this message]
2023-11-27 18:21             ` Cyril Brulebois
2023-11-27 18:52           ` Stefan Wahren
2023-11-27  6:02 ` Justin Chen
2023-11-27 11:08   ` Stefan Wahren
2023-11-27 11:22     ` Phil Elwell
2023-11-27 11:38       ` Stefan Wahren
2023-11-27 11:58         ` Phil Elwell
2023-11-27 12:33           ` Stefan Wahren
2023-11-27 16:28             ` Phil Elwell
2023-11-27 17:44               ` Justin Chen
2023-11-27 18:41                 ` Florian Fainelli
2023-11-27 19:22                   ` Stefan Wahren
2023-11-27 21:49                     ` Florian Fainelli
2023-11-28  6:44                       ` Stefan Wahren
2023-11-28 14:46                         ` Phil Elwell

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=d22e404b-30e5-4c1f-add0-77c0bb88351d@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kibi@debian.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=robh+dt@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