public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 1/2] usb: dwc3: core: add support for remapping global register start address
Date: Thu, 13 Apr 2023 03:44:27 +0000	[thread overview]
Message-ID: <651b2e92a400411f80823aa01635acb5@realtek.com> (raw)
In-Reply-To: 20230412210856.xcbp3crhbedjvnix@synopsys.com


> > > +     /*
> > > +      * For some dwc3 controller, the dwc3 global register start address
> is
> > > +      * not at DWC3_GLOBALS_REGS_START (0xc100).
> > > +      */
> > > +     if (dev->of_node) {
> > > +             int global_regs_starting_offset = 0;
> > > +
> > > +             device_property_read_u32(dev,
> > "snps,global-regs-starting-offset",
> > > +                              &global_regs_starting_offset);
> >
> > I suggested to use compatible string instead since this isn't common
> > and only unique to your platform. Any reason we shouldn't do that?
> >
> > ie. something like this:
> >
> > if (dev->of_node && of_device_is_compatiable(dev->of_node,
> > "your-platform"))
> >         dwc_res.start += your_platform_offset; else
> >         dwc_res.start = DWC3_GLOBALS_REGS_START;
> >
> 
> I will try this suggestion.
> 
> Thanks,
> Stanley

The dwc3/core is a general driver for every dwc3 IP of SoCs,
and vendor's definition and compatible should specify on its parent.
This should be inappropriate if we add a special platform compatible to dwc3/core driver.
Therefore, I define this property to adjust this value. This is more resilient.
If there are other platforms that also have non-standard offset, this property is also applicable.

Thank,
Stanley

  parent reply	other threads:[~2023-04-13  3:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230412033006.10859-1-stanley_chang@realtek.com>
2023-04-12 11:14 ` [PATCH v2 1/2] usb: dwc3: core: add support for remapping global register start address Stanley Chang[昌育德]
     [not found] ` <20230412210856.xcbp3crhbedjvnix@synopsys.com>
2023-04-13  3:44   ` Stanley Chang[昌育德] [this message]
2023-04-13  4:24 ` Stanley Chang
     [not found] ` <20230412033006.10859-2-stanley_chang@realtek.com>
     [not found]   ` <955cc334-eaac-5880-51cf-8ab171f0ef48@kernel.org>
2023-04-12 11:11     ` [PATCH v2 2/2] dt-bindings: usb: snps,dwc3: Add 'snps,global-regs-starting-offset' quirk Stanley Chang[昌育德]
2023-04-12 14:13       ` Krzysztof Kozlowski
     [not found]   ` <CAL_JsqLqTHbHjB1qiLduhzvTaO7EBMgL6KYqZJtgStGVGtX1vQ@mail.gmail.com>
2023-04-13  2:53     ` Stanley Chang[昌育德]
2023-04-14  9:08       ` Krzysztof Kozlowski
2023-04-14  9:36         ` Stanley Chang[昌育德]
2023-04-13  4:25   ` Stanley Chang
2023-04-13  7:32     ` Krzysztof Kozlowski
2023-04-13 14:58       ` Stanley Chang[昌育德]
2023-04-13 16:36         ` Krzysztof Kozlowski
2023-04-14  2:12           ` Stanley Chang[昌育德]
2023-04-14  9:05             ` Krzysztof Kozlowski
2023-04-13 13:00     ` Rob Herring

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=651b2e92a400411f80823aa01635acb5@realtek.com \
    --to=stanley_chang@realtek.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.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