linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ben Levinsky <ben.levinsky@amd.com>
To: <jassisinghbrar@gmail.com>, <michal.simek@amd.com>,
	<shubhrajyoti.datta@amd.com>, <tanmay.shah@amd.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v3 0/3] mailbox: zynqmp: Enable Bufferless IPIs for Versal based SOCs
Date: Wed, 10 Apr 2024 10:08:22 -0700	[thread overview]
Message-ID: <20240410170825.1132324-1-ben.levinsky@amd.com> (raw)

For Xilinx-AMD Versal and Versal NET SOC's there exist also
inter-processor-interrupts (IPIs) without IPI Message Buffers. For these
enable use of IPI Mailbox driver for send/receive as well.

This is enabled with new compatible string: "xlnx,versal-ipi-mailbox"

Original, buffered usage for ZynqMP based SOC is still supported.

Note that Versal bindings are already present in xlnx,zynqmp-ipi-mailbox.yaml

v2:
- formatting in 2/3 patch
- remove extra handling in 3/3 versal_ipi_setup()
v3:
1/3 - removed additional newline to avoid
./scripts/checkpatch.pl --strict -f drivers/mailbox/zynqmp-ipi-mailbox.c
CHECK: Please don't use multiple blank lines
#434: FILE: drivers/mailbox/zynqmp-ipi-mailbox.c:434:
+
+
2/3 - remove unused variable dev
drivers/mailbox/zynqmp-ipi-mailbox.c:565:24: warning: variable 'dev' set but not 
used [-Wunused-but-set-variable]
         struct device *mdev, *dev;
3/3 - remove unused variable dev
                               ^
drivers/mailbox/zynqmp-ipi-mailbox.c:666:24: warning: variable 'dev' set but not 
used [-Wunused-but-set-variable]
         struct device *mdev, *dev;
                               ^

Ben Levinsky (3):
  mailbox: zynqmp: Move of_match structure closer to usage
  mailbox: zynqmp: Move buffered IPI setup to of_match selected routine
  mailbox: zynqmp: Enable Bufferless IPI usage on Versal-based SOC's

 drivers/mailbox/zynqmp-ipi-mailbox.c | 257 ++++++++++++++++++++++-----
 1 file changed, 212 insertions(+), 45 deletions(-)

-- 
2.25.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2024-04-10 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 17:08 Ben Levinsky [this message]
2024-04-10 17:08 ` [PATCH v3 1/3] mailbox: zynqmp: Move of_match structure closer to usage Ben Levinsky
2024-04-10 17:08 ` [PATCH v3 2/3] mailbox: zynqmp: Move buffered IPI setup to of_match selected routine Ben Levinsky
2024-04-10 17:08 ` [PATCH v3 3/3] mailbox: zynqmp: Enable Bufferless IPI usage on Versal-based SOC's Ben Levinsky
     [not found] ` <24bd320a-ba89-4ad0-a905-6915e00b705d@amd.com>
2024-04-25 14:40   ` Fwd: [PATCH v3 0/3] mailbox: zynqmp: Enable Bufferless IPIs for Versal based SOCs Ben Levinsky
2024-05-01  1:39     ` Jassi Brar

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=20240410170825.1132324-1-ben.levinsky@amd.com \
    --to=ben.levinsky@amd.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=tanmay.shah@amd.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).