Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
	"peter.griffin@linaro.org" <peter.griffin@linaro.org>,
	"andre.draszik@linaro.org" <andre.draszik@linaro.org>,
	"tudor.ambarus@linaro.org" <tudor.ambarus@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: google: Initialise probe properties with DWC3_DEFAULT_PROPERTIES
Date: Tue, 1 Sep 2026 16:32:09 +0200	[thread overview]
Message-ID: <2026090102-sponge-enjoyably-89f6@gregkh> (raw)
In-Reply-To: <ao404zOD-rXKZ84C@vbox>

On Wed, Aug 26, 2026 at 12:36:29AM +0000, Thinh Nguyen wrote:
> On Wed, Aug 19, 2026, Radhey Shyam Pandey wrote:
> > dwc3_google_probe() zero initialises struct dwc3_probe_data and never
> > assigns its properties member. The unspecified state of gsbuscfg0_reqinfo
> > is encoded as DWC3_GSBUSCFG0_REQINFO_UNSPECIFIED (0xffffffff), not as
> > zero, so dwc3_get_software_properties() reads the zeroed field as a value
> > the glue explicitly requested:
> > 
> > 	if (properties->gsbuscfg0_reqinfo !=
> > 	    DWC3_GSBUSCFG0_REQINFO_UNSPECIFIED) {
> > 		dwc->gsbuscfg0_reqinfo = properties->gsbuscfg0_reqinfo;
> > 		return;
> > 	}
> > 
> > Two things follow. dwc3_config_soc_bus() programs GSBUSCFG0.REQINFO with
> > zero on hardware that never asked for it, and the early return skips the
> > walk over the parent devices, so a swnode or device tree supplied
> > snps,gsbuscfg0-reqinfo would be ignored.
> > 
> > Assign DWC3_DEFAULT_PROPERTIES so the unset fields carry their unspecified
> > sentinels and the controller is left alone.
> > 
> > Fixes: 8995a37371bf ("usb: dwc3: Add Google Tensor SoC DWC3 glue driver")
> 
> Does this need Cc stable?

I'll add it, thanks.


      reply	other threads:[~2026-09-01 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 18:21 [PATCH] usb: dwc3: google: Initialise probe properties with DWC3_DEFAULT_PROPERTIES Radhey Shyam Pandey
2026-08-26  0:36 ` Thinh Nguyen
2026-09-01 14:32   ` gregkh [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=2026090102-sponge-enjoyably-89f6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=andre.draszik@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=tudor.ambarus@linaro.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