From: Krzysztof Kozlowski <krzk@kernel.org>
To: caohang@eswincomputing.com, gregkh@linuxfoundation.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Thinh.Nguyen@synopsys.com, p.zabel@pengutronix.de,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
pinkesh.vaghela@einfochips.com,
Senchuan Zhang <zhangsenchuan@eswincomputing.com>
Subject: Re: [PATCH v5 2/2] usb: dwc3: eic7700: Add EIC7700 USB driver
Date: Tue, 4 Nov 2025 08:59:13 +0100 [thread overview]
Message-ID: <76ec3e26-a38c-4643-aaab-7806cc39bd89@kernel.org> (raw)
In-Reply-To: <20251104065226.1513-1-caohang@eswincomputing.com>
On 04/11/2025 07:52, caohang@eswincomputing.com wrote:
> From: Hang Cao <caohang@eswincomputing.com>
>
> Add the eic7700 usb driver, which is responsible for
> identifying,configuring and connecting usb devices.
>
> Signed-off-by: Senchuan Zhang <zhangsenchuan@eswincomputing.com>
> Signed-off-by: Hang Cao <caohang@eswincomputing.com>
...
> +
> static int dwc3_generic_probe(struct platform_device *pdev)
> {
> const struct dwc3_properties *properties;
> @@ -83,6 +119,12 @@ static int dwc3_generic_probe(struct platform_device *pdev)
> else
> probe_data.properties = DWC3_DEFAULT_PROPERTIES;
>
> + if (of_device_is_compatible(dev->of_node, "eswin,eic7700-dwc3")) {
No, you have driver match data for that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-04 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 6:50 [PATCH v5 0/2] Add driver support for ESWIN EIC7700 SoC USB controller caohang
2025-11-04 6:52 ` [PATCH v5 1/2] dt-bindings: usb: Add ESWIN EIC7700 " caohang
2025-11-04 8:26 ` Rob Herring (Arm)
2025-11-04 6:52 ` [PATCH v5 2/2] usb: dwc3: eic7700: Add EIC7700 USB driver caohang
2025-11-04 7:59 ` Krzysztof Kozlowski [this message]
2025-11-05 12:27 ` Hang Cao
2025-11-05 23:41 ` Thinh Nguyen
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=76ec3e26-a38c-4643-aaab-7806cc39bd89@kernel.org \
--to=krzk@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=caohang@eswincomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--cc=zhangsenchuan@eswincomputing.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;
as well as URLs for NNTP newsgroup(s).