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>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH 0/3] Add support for PolarFire SoC's musb controller
Date: Tue, 7 Jun 2022 14:22:01 +0100 [thread overview]
Message-ID: <20220607132204.746180-1-conor.dooley@microchip.com> (raw)
Hey Bin, Greg,
Short series here adding support for USB on Microchip PolarFire SoC FPGAs.
The kconfig dependancy for INVENTRA_DMA has become a bit of a mouthful,
is there a better way of dealing with that?
Thanks,
Conor.
Conor Dooley (3):
usb: musb: Add support for PolarFire SoC's musb controller
MAINTAINERS: add musb to PolarFire SoC entry
riscv: dts: microchip: fix icicle kit's dr_mode
MAINTAINERS | 1 +
.../boot/dts/microchip/mpfs-icicle-kit.dts | 2 +-
drivers/usb/musb/Kconfig | 13 +-
drivers/usb/musb/Makefile | 1 +
drivers/usb/musb/mpfs.c | 285 ++++++++++++++++++
5 files changed, 300 insertions(+), 2 deletions(-)
create mode 100644 drivers/usb/musb/mpfs.c
--
2.36.1
next reply other threads:[~2022-06-07 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:22 Conor Dooley [this message]
2022-06-07 13:22 ` [PATCH 1/3] usb: musb: Add support for PolarFire SoC's musb controller Conor Dooley
2022-06-07 15:18 ` Ben Dooks
2022-06-12 22:14 ` Conor.Dooley
2022-06-07 13:22 ` [PATCH 2/3] MAINTAINERS: add musb to PolarFire SoC entry Conor Dooley
2022-06-07 13:22 ` [PATCH 3/3] riscv: dts: microchip: fix icicle kit's dr_mode Conor Dooley
2022-06-08 12:21 ` Heinrich Schuchardt
2022-06-08 12:49 ` Conor.Dooley
2022-06-09 8:23 ` Conor.Dooley
2022-06-07 17:53 ` [PATCH 0/3] Add support for PolarFire SoC's musb controller Conor.Dooley
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=20220607132204.746180-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=b-liu@ti.com \
--cc=daire.mcnamara@microchip.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).