From: Elliot Berman <quic_eberman@quicinc.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Elliot Berman <quic_eberman@quicinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>
Subject: [PATCH 0/3] mailbox: Allow direct registration to a channel
Date: Mon, 13 Feb 2023 15:25:34 -0800 [thread overview]
Message-ID: <20230213232537.2040976-1-quic_eberman@quicinc.com> (raw)
Two mailbox controllers have channel/client binding mechanisms that are
controller-specific and not using the devicetree binding mechanisms. Mailbox
channel/client is conceptually done in two steps: selecting the channel
and binding the selected to channel to a client. Channel selection is sometimes
controller specific (pcc and omap are examples). The channel/client binding
code is all the same.
This small series de-duplicates and refactors the channel/client binding
into a common framework function: "mbox_bind_client" which all of the
channel selection mechanisms can use.
I found this duplicate code while working on the support for Gunyah hypervisor
message queues [1]. I've only been able to compile-test omap-maiblox and pcc,
however it is a straightforward conversion here.
[1]: https://lore.kernel.org/all/20230120224627.4053418-9-quic_eberman@quicinc.com/
Elliot Berman (3):
mailbox: Allow direct registration to a channel
mailbox: omap: Use mbox_bind_client
mailbox: pcc: Use mbox_bind_client
drivers/mailbox/mailbox.c | 96 ++++++++++++++++++++++++----------
drivers/mailbox/omap-mailbox.c | 22 ++------
drivers/mailbox/pcc.c | 82 ++++++++++++++++-------------
include/linux/mailbox_client.h | 1 +
4 files changed, 118 insertions(+), 83 deletions(-)
base-commit: 09e41676e35ab06e4bce8870ea3bf1f191c3cb90
--
2.39.1
next reply other threads:[~2023-02-13 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 23:25 Elliot Berman [this message]
2023-02-13 23:25 ` [PATCH 2/3] mailbox: omap: Use mbox_bind_client Elliot Berman
2023-02-13 23:25 ` [PATCH 3/3] mailbox: pcc: " Elliot Berman
2023-02-15 10:17 ` [PATCH 0/3] mailbox: Allow direct registration to a channel Sudeep Holla
2023-02-15 16:58 ` Elliot Berman
2023-02-16 9:58 ` Sudeep Holla
2023-02-16 16:41 ` Elliot Berman
2023-02-22 13:59 ` Sudeep Holla
2023-02-16 16:38 ` [PATCH 1/3] " Elliot Berman
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=20230213232537.2040976-1-quic_eberman@quicinc.com \
--to=quic_eberman@quicinc.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®