From: Konrad Dybcio <konradybcio@kernel.org>
To: Rob Herring <robh@kernel.org>, Saravana Kannan <saravanak@google.com>
Cc: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Melody Olvera <quic_molvera@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH 0/2] Allow 'nonposted-mmio' on single devices
Date: Wed, 19 Mar 2025 15:25:56 +0100 [thread overview]
Message-ID: <20250319-topic-nonposted_mmio-v1-0-dfb886fbd15f@oss.qualcomm.com> (raw)
For a plethora of reasons, usually not very pretty, a single device on
a given bus/platform may require a different type of memory mapping.
With nonposted-mmio specifically, we want to limit the scope of setting
it where it's not necessary, so as not to shoot ourselves in the foot
in the performance department.
This series allows mapping a single device as nE on arm64.
A user will be sent separately, as a new node for a QC platform.
The dt-bindings part is handled in the checker itself, see the following:
https://github.com/devicetree-org/dt-schema/pull/156
Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
---
Konrad Dybcio (2):
of: address: Expand nonposted-mmio to non-Apple Silicon platforms
of: address: Allow to specify nonposted-mmio per-device
drivers/of/address.c | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
---
base-commit: c4d4884b67802c41fd67399747165d65c770621a
change-id: 20250315-topic-nonposted_mmio-5393a3de0d35
Best regards,
--
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
next reply other threads:[~2025-03-19 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 14:25 Konrad Dybcio [this message]
2025-03-19 14:25 ` [PATCH 1/2] of: address: Expand nonposted-mmio to non-Apple Silicon platforms Konrad Dybcio
2025-03-21 16:27 ` Rob Herring (Arm)
2025-03-19 14:25 ` [PATCH 2/2] of: address: Allow to specify nonposted-mmio per-device Konrad Dybcio
2025-03-21 16:27 ` Rob Herring (Arm)
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=20250319-topic-nonposted_mmio-v1-0-dfb886fbd15f@oss.qualcomm.com \
--to=konradybcio@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_molvera@quicinc.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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®