public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: u-boot@lists.denx.de, Mattijs Korpershoek <mkorpershoek@kernel.org>
Subject: Re: [PATCH] usb: gadget: Move USB_GADGET_DUALSPEED to be slightly more visible
Date: Sat, 21 Mar 2026 11:34:53 -0600	[thread overview]
Message-ID: <20260321173453.GG502704@bill-the-cat> (raw)
In-Reply-To: <03a11b96-88f4-4ca0-9705-0bfe8409ee6c@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

On Sat, Mar 21, 2026 at 02:53:13AM +0100, Marek Vasut wrote:
> On 3/20/26 2:53 PM, Tom Rini wrote:
> 
> [...]
> 
> > > @@ -371,3 +367,11 @@ config SPL_SDP_USB_DEV
> > >            so it can be used in compiled environment.
> > > 
> > >   endif # SPL_USB_GADGET
> > > +
> > > +if USB_GADGET || SPL_USB_GADGET
> > > +
> > > +# Selected by UDC drivers that support high-speed operation.
> > > +config USB_GADGET_DUALSPEED
> > > +       bool
> > > +
> > > +endif
> > > "
> > 
> > You don't need to guard hidden symbols.
> 
> We also do not want to expose this Kconfig symbol unless it makes sense to
> expose it ? In fact, if the symbol is not available and someone attempts to
> use it in Kconfig, they would get a warning, which should provide a clue
> that they are doing something wrong ?

It's a hidden symbol, so it's not exposed to the user. The problem is
that today someone is getting it wrong as you suggest but it's hard to
trigger a warning over it. That said, your patch also fixes the problem,
so:

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-03-21 17:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  1:24 [PATCH] usb: gadget: Move USB_GADGET_DUALSPEED to be slightly more visible Tom Rini
2026-03-17  2:34 ` Marek Vasut
2026-03-17 13:41   ` Tom Rini
2026-03-17 19:42     ` Marek Vasut
2026-03-18  1:26       ` Tom Rini
2026-03-19  0:50         ` Marek Vasut
2026-03-19 13:39           ` Tom Rini
2026-03-19 17:57             ` Marek Vasut
2026-03-20 13:53               ` Tom Rini
2026-03-21  1:53                 ` Marek Vasut
2026-03-21 17:34                   ` Tom Rini [this message]
2026-03-21 18:50                     ` Marek Vasut
2026-03-23 14:32 ` [PATCH v2] " Tom Rini
2026-03-23 15:05   ` Marek Vasut
2026-03-26  8:57   ` Mattijs Korpershoek
2026-04-08  9:26   ` Mattijs Korpershoek

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=20260321173453.GG502704@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=marek.vasut@mailbox.org \
    --cc=mkorpershoek@kernel.org \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox