From: Conor Dooley <conor.dooley@microchip.com>
To: Bin Liu <b-liu@ti.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daire McNamara <daire.mcnamara@microchip.com>,
Valentina Fernandez <valentina.fernandezalanis@microchip.com>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-riscv@lists.infradead.org>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v2 0/2] Add support for PolarFire SoC's musb controller
Date: Mon, 13 Jun 2022 12:46:41 +0100 [thread overview]
Message-ID: <20220613114642.1615292-1-conor.dooley@microchip.com> (raw)
Hey Bin, Greg,
Short series here adding support for USB on Microchip PolarFire SoC FPGAs.
The kconfig dependency for INVENTRA_DMA has become a bit of a mouthful,
is there a better way of dealing with that?
Thanks,
Conor.
Changes since v1:
- Drop unneeded resource copying as per Rob's changes to the other drivers
- Drop the dts patch
Conor Dooley (2):
usb: musb: Add support for PolarFire SoC's musb controller
MAINTAINERS: add musb to PolarFire SoC entry
MAINTAINERS | 1 +
drivers/usb/musb/Kconfig | 13 +-
drivers/usb/musb/Makefile | 1 +
drivers/usb/musb/mpfs.c | 265 ++++++++++++++++++++++++++++++++++++++
4 files changed, 279 insertions(+), 1 deletion(-)
create mode 100644 drivers/usb/musb/mpfs.c
base-commit: f2906aa863381afb0015a9eb7fefad885d4e5a56
--
2.36.1
next reply other threads:[~2022-06-13 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:46 Conor Dooley [this message]
2022-06-13 11:46 ` [PATCH v2 1/2] usb: musb: Add support for PolarFire SoC's musb controller Conor Dooley
2022-06-13 11:46 ` [PATCH v2 2/2] MAINTAINERS: add musb to PolarFire SoC entry Conor Dooley
2022-06-13 11:55 ` [PATCH v2 0/2] Add support for PolarFire SoC's musb controller Conor.Dooley
2022-06-21 14:36 ` Greg Kroah-Hartman
2022-06-21 15:16 ` Conor.Dooley
2022-06-21 15:28 ` Conor.Dooley
2022-06-21 15:41 ` Greg KH
2022-06-21 15:48 ` Conor.Dooley
2022-06-21 17:02 ` Greg KH
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=20220613114642.1615292-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=b-liu@ti.com \
--cc=ben.dooks@codethink.co.uk \
--cc=daire.mcnamara@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=valentina.fernandezalanis@microchip.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