From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net
Cc: evgreen@chromium.org.net, subashab@codeaurora.org,
cpratapa@codeaurora.org, bjorn.andersson@linaro.org,
agross@kernel.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/4] net: ipa: I/O map SMEM and IMEM
Date: Fri, 1 May 2020 16:46:21 -0500 [thread overview]
Message-ID: <20200501214625.31539-1-elder@linaro.org> (raw)
This series adds the definition of two memory regions that must be
mapped for IPA to access through an SMMU. It defines the SMMU for
the SDM845 SoC; the SC7180 already had this defined, though these
memory regions were not previously defined or mapped.
-Alex
Alex Elder (4):
arm64: dts: sdm845: add IPA iommus property
net: ipa: redefine struct ipa_mem_data
net: ipa: define IMEM memory region for IPA
net: ipa: define SMEM memory region for IPA
arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +
drivers/net/ipa/ipa.h | 10 ++
drivers/net/ipa/ipa_data-sc7180.c | 14 +-
drivers/net/ipa/ipa_data-sdm845.c | 14 +-
drivers/net/ipa/ipa_data.h | 23 +--
drivers/net/ipa/ipa_main.c | 2 +-
drivers/net/ipa/ipa_mem.c | 209 ++++++++++++++++++++++++++-
drivers/net/ipa/ipa_mem.h | 3 +-
8 files changed, 256 insertions(+), 21 deletions(-)
--
2.20.1
next reply other threads:[~2020-05-01 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 21:46 Alex Elder [this message]
2020-05-01 21:46 ` [PATCH net-next 1/4] arm64: dts: sdm845: add IPA iommus property Alex Elder
2020-05-01 21:59 ` Alex Elder
2020-05-01 21:46 ` [PATCH net-next 2/4] net: ipa: redefine struct ipa_mem_data Alex Elder
2020-05-01 21:46 ` [PATCH net-next 3/4] net: ipa: define IMEM memory region for IPA Alex Elder
2020-05-01 21:46 ` [PATCH net-next 4/4] net: ipa: define SMEM " Alex Elder
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=20200501214625.31539-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=subashab@codeaurora.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).