From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Orgad Shaneh <orgads@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Octeon: apply USB FDT fixups also when USB is modular
Date: Tue, 8 Sep 2026 16:15:18 +0200 [thread overview]
Message-ID: <aqAYdvTNO4DOYAdF@alpha.franken.de> (raw)
In-Reply-To: <20260901193357.1352617-1-orgads@gmail.com>
On Tue, Sep 01, 2026 at 07:33:55PM +0000, Orgad Shaneh wrote:
> The uctl/usbn device-tree fixups in octeon_prune_device_tree() - which
> set the board's USB reference-clock frequency and type from
> __cvmx_helper_board_usb_get_clock_type() - are guarded by
> "#ifdef CONFIG_USB", which is false when USB is built as a module. The
> fixups then silently disappear and octeon-hcd sees whatever default the
> DTS carries (12MHz crystal in octeon_3xxx.dts), leaving the PHY dead or
> the bus erroring on boards with a different reference clock.
>
> Use IS_ENABLED() so USB=m gets the same fixups as USB=y.
>
> Fixes: 7fd57ab9d9cf ("MIPS: Octeon: Fix compile error when USB is not enabled.")
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Orgad Shaneh <orgads@gmail.com>
> ---
>
> v2: no code change; added the Assisted-by tag for the AI assistance used
> (Documentation/process/coding-assistants.rst).
>
> diff --git a/arch/mips/cavium-octeon/octeon-platform.c b/arch/mips/cavium-octeon/octeon-platform.c
> --- a/arch/mips/cavium-octeon/octeon-platform.c
> +++ b/arch/mips/cavium-octeon/octeon-platform.c
> @@ -18,7 +18,7 @@
> #include <asm/octeon/octeon.h>
> #include <asm/octeon/cvmx-helper-board.h>
>
> -#ifdef CONFIG_USB
> +#if IS_ENABLED(CONFIG_USB)
> #include <linux/usb/ehci_def.h>
> #include <linux/usb/ehci_pdriver.h>
> #include <linux/usb/ohci_pdriver.h>
> @@ -1080,7 +1080,7 @@
> ;
> }
>
> -#ifdef CONFIG_USB
> +#if IS_ENABLED(CONFIG_USB)
> /* OHCI/UHCI USB */
> alias_prop = fdt_getprop(initial_boot_params, aliases,
> "uctl", NULL);
> --
> 2.47.0
applied to mips-fixes
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-09-08 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 17:57 [PATCH] " Orgad Shaneh
2026-09-01 19:33 ` [PATCH v2] " Orgad Shaneh
2026-09-08 14:15 ` Thomas Bogendoerfer [this message]
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=aqAYdvTNO4DOYAdF@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=orgads@gmail.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
all inboxes | Powered by JetHome®