mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Wesley Cheng <quic_wcheng@quicinc.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: core: Add DWC31 version 2.00a controller
Date: Thu, 7 Mar 2024 02:01:57 +0000	[thread overview]
Message-ID: <20240307020153.ll37lvuy7ftxnohx@synopsys.com> (raw)
In-Reply-To: <44f00418-b09b-5ee5-c70c-d4580ffd0049@quicinc.com>

On Fri, Mar 01, 2024, Wesley Cheng wrote:
> Hi Greg,
> 
> On 3/1/2024 1:45 PM, Greg KH wrote:
> > On Fri, Mar 01, 2024 at 01:35:54PM -0800, Wesley Cheng wrote:
> > > Add revision value for identifying DWC31 version 2.00a based controllers.
> > > 
> > > Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com>
> > > ---
> > >   drivers/usb/dwc3/core.h | 1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> > > index df544ec730d2..f3bbbc1947bd 100644
> > > --- a/drivers/usb/dwc3/core.h
> > > +++ b/drivers/usb/dwc3/core.h
> > > @@ -1259,6 +1259,7 @@ struct dwc3 {
> > >   #define DWC31_REVISION_170A	0x3137302a
> > >   #define DWC31_REVISION_180A	0x3138302a
> > >   #define DWC31_REVISION_190A	0x3139302a
> > > +#define DWC31_REVISION_200A	0x3230302a
> > 
> > What code uses this define?
> > 
> 
> Don't think there is anything within the DWC3 core that would be different
> specifically for 2.00a versus previous revisions. (so far)
> 
> > Why add a define that is not used?
> > 
> 
> There is a running list of all the DWC3 revisions.  Not all of them are
> being used, so my understanding was that we're just keeping track of all
> possible version values that can be read from the DWC3 version HW register.
> If this is the not the case, maybe we can just leave this out until we find
> a need to add it.
> 

Greg already picked this up, so it's fine. But I would prefer to only
define new macros when they are needed. There are a lot of versions and
configurations we don't list in dwc3.

Thanks,
Thinh

      reply	other threads:[~2024-03-07  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 21:35 Wesley Cheng
2024-03-01 21:45 ` Greg KH
2024-03-01 22:47   ` Wesley Cheng
2024-03-07  2:01     ` Thinh Nguyen [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=20240307020153.ll37lvuy7ftxnohx@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_wcheng@quicinc.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®