All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@kernel.org>
To: Casey Connolly <casey.connolly@linaro.org>
Cc: u-boot-qcom@groups.io, neil.armstrong@linaro.org,
	trini@konsulko.com, dmitry.baryshkov@oss.qualcomm.com,
	u-boot@lists.denx.de, Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH v2] qcom_defconfig: Add VID/PID to represent fastboot device
Date: Thu, 14 Aug 2025 11:18:19 +0530	[thread overview]
Message-ID: <aJ14o75G4SnU_Emp@sumit-X1> (raw)
In-Reply-To: <4816e2ef-b690-4f56-acf3-9c8b7a491b5f@linaro.org>

On Wed, Aug 13, 2025 at 03:50:21PM +0200, Casey Connolly wrote:
> Hi Sumit,
> 
> On 24/07/2025 13:19, Sumit Garg wrote:
> > From: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > 
> > Currently fastboot mode is enumerated as VID/PID: 0000:0000 which is
> > not appropriate. On Qcom platforms, fastboot mode is rather enumerated
> > as VID/PID: 18d1:d00d in ABL or from fastboot.efi app. So lets use the
> > same VID/PID pair in U-Boot to represent fastboot mode.
> 
> Since we have different defconfigs going on for Qualcomm, I think it
> makes more sense to set defaults in drivers/usb/gadget/Kconfig like
> rockchip does, then we don't need to update all the defconfigs and we
> can just override them if desired. Would you mind respinning this? Sorry
> this is coming so late...

No worries, Kconfig option sounds reasonable to me. I can spin up a v3
with that.

-Sumit

> 
> Kind regards,>
> > Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > ---
> > 
> > Changes in v2:
> > - Rebased to tip of master since v1 didn't apply cleanly there.
> > 
> >  configs/qcom_defconfig | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/configs/qcom_defconfig b/configs/qcom_defconfig
> > index b9ba7a677d9..4e24a43b888 100644
> > --- a/configs/qcom_defconfig
> > +++ b/configs/qcom_defconfig
> > @@ -140,6 +140,8 @@ CONFIG_USB_XHCI_DWC3=y
> >  CONFIG_USB_DWC3=y
> >  CONFIG_USB_DWC3_GENERIC=y
> >  CONFIG_USB_GADGET=y
> > +CONFIG_USB_GADGET_VENDOR_NUM=0x18d1
> > +CONFIG_USB_GADGET_PRODUCT_NUM=0xd00d
> >  CONFIG_USB_FUNCTION_MASS_STORAGE=y
> >  CONFIG_UFS=y
> >  CONFIG_QCOM_UFS=y
> 
> -- 
> // Casey (she/her)
> 

      reply	other threads:[~2025-08-14  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 11:19 [PATCH v2] qcom_defconfig: Add VID/PID to represent fastboot device Sumit Garg
2025-07-24 11:42 ` neil.armstrong
2025-07-25 13:20 ` Casey Connolly
2025-08-13 13:50 ` Casey Connolly
2025-08-14  5:48   ` Sumit Garg [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=aJ14o75G4SnU_Emp@sumit-X1 \
    --to=sumit.garg@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=trini@konsulko.com \
    --cc=u-boot-qcom@groups.io \
    --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 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.