From: Rob Herring <robh@kernel.org>
To: 施錕鴻 <vincent.sunplus@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stern@rowland.harvard.edu, p.zabel@pengutronix.de,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, wells.lu@sunplus.com
Subject: Re: [PATCH v1 0/2] Add USB HOST OHCI driver for Sunplus SP7021 SoC
Date: Thu, 24 Mar 2022 08:18:34 -0500 [thread overview]
Message-ID: <YjxvqoZRV3ZWpZL4@robh.at.kernel.org> (raw)
In-Reply-To: <CAPvp3RjPW1x-k4oA7QHHXm+QCNySMJLiR5TcqtCK-0geRtrd8A@mail.gmail.com>
On Thu, Mar 24, 2022 at 06:48:41PM +0800, 施錕鴻 wrote:
> Rob Herring <robh@kernel.org> 於 2022年3月24日 週四 上午2:07寫道：
> >
> > On Mon, Mar 14, 2022 at 01:32:02PM +0800, Vincent Shih wrote:
> > > This is a patch series for USB HOST OHCI driver for Sunplus SP7021 SoC.
> > >
> > > Sunplus SP7021 is an ARM Cortex A7 (4 cores) based SoC. It integrates
> > > many peripherals (ex: UART, I2C, SPI, SDIO, eMMC, USB, SD Card and
> > > etc.) into a single chip. It is designed for industrial control.
> >
> > Looks to me like the generic-ohci binding and driver should work for
> > this?
> >
> The generic-ohci binding and driver did work for Sunplus SP7021.
> And do I need to submit the patch for the ohci driver and binding doc
> for Sunplus
> SP7021 SoC ?
Just need to add the compatible string to the generic-ohci binding. For
the driver, I don't know, did you have to change anything?
Rob
prev parent reply other threads:[~2022-03-24 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 5:32 [PATCH v1 0/2] Add USB HOST OHCI driver for Sunplus SP7021 SoC Vincent Shih
2022-03-14 5:32 ` [PATCH v1 1/2] usb: host: ohci-sunplus: Add driver for USB HOST OHCI in " Vincent Shih
2022-03-14 5:32 ` [PATCH v1 2/2] dt-bindings: usb: Add bindings doc for Sunplus USB HOST OHCI driver Vincent Shih
2022-03-14 16:42 ` Krzysztof Kozlowski
2022-03-17 10:24 ` 施錕鴻
2022-03-23 18:07 ` [PATCH v1 0/2] Add USB HOST OHCI driver for Sunplus SP7021 SoC Rob Herring
2022-03-24 10:48 ` 施錕鴻
2022-03-24 13:18 ` Rob Herring [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=YjxvqoZRV3ZWpZL4@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stern@rowland.harvard.edu \
--cc=vincent.sunplus@gmail.com \
--cc=wells.lu@sunplus.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 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.