From: Conor Dooley <conor@kernel.org>
To: arnd@arndb.de
Cc: conor@kernel.org, palmer@dabbelt.com,
linux-riscv@lists.infradead.org, soc@kernel.org
Subject: [GIT PULL] RISC-V SoC drivers for v6.4
Date: Thu, 6 Apr 2023 21:11:23 +0100 [thread overview]
Message-ID: <20230406-islamist-mop-81d651b8830d@spud> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2679 bytes --]
Hey Arnd,
Please pull some updates for the "otherwise unloved" RISC-V SoC drivers
for v6.4! The bulk of this is my fixing my own driver, and there's a fix
in here to make sure that we don't hit randconfig build issues once !MMU
is enabled for 32-bit kernels.
Thanks,
Conor.
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-soc-for-v6.4
for you to fetch changes up to 4dd472bdafcb660bea17bc63a97d06e24fcb36ed:
soc: microchip: mpfs: add a prefix to rx_callback() (2023-04-03 20:32:43 +0100)
----------------------------------------------------------------
RISC-V SoC drivers for v6.4
Microchip:
Mailbox controller & client changes for the system controller on
PolarFire SoC. The controller bits have been acked by Jassi.
Primarily the changes work around a "hardware" bug (really the system
controller's software, but it may as well be hardware as customers
cannot change it) where interrupts are not generated if a service fails.
The mailbox controller driver is tweaked to use polling, rather than
interrupt, mode and there are some changes to timeout code required in
the client driver as a result. There's some opportunistic cleanup that I
performed while doing the swap too.
Canaan:
A single fix for some randconfig issues that crop up when !mmu is
enabled for 32-bit kernels, due to my changes in a previous release that
swapped out select based entablement of the driver.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Conor Dooley (10):
mailbox: mpfs: fix an incorrect mask width
mailbox: mpfs: switch to txdone_poll
mailbox: mpfs: ditch a useless busy check
mailbox: mpfs: check the service status in .tx_done()
soc: microchip: mpfs: fix some horrible alignment
soc: microchip: mpfs: use a consistent completion timeout
soc: microchip: mpfs: simplify error handling in mpfs_blocking_transaction()
soc: microchip: mpfs: handle timeouts and failed services differently
Merge patch series "mailbox,soc: mpfs: add support for fallible services"
soc: microchip: mpfs: add a prefix to rx_callback()
Jesse Taube (1):
soc: canaan: Make K210_SYSCTL depend on CLK_K210
drivers/mailbox/mailbox-mpfs.c | 55 +++++++++++++++-------------
drivers/soc/canaan/Kconfig | 5 +--
drivers/soc/microchip/mpfs-sys-controller.c | 56 +++++++++++++++++++----------
3 files changed, 72 insertions(+), 44 deletions(-)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2023-04-06 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230406-islamist-mop-81d651b8830d@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).