From: Rob Herring <robh@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: djakov@kernel.org, dmitry.baryshkov@linaro.org,
benl@squareup.com, bjorn.andersson@linaro.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, agross@kernel.org,
jun.nie@linaro.org, shawn.guo@linaro.org,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: interconnect: Convert snoc-mm to a sub-node of snoc
Date: Wed, 9 Feb 2022 14:57:33 -0600 [thread overview]
Message-ID: <YgQqvVA0HaqWsAMA@robh.at.kernel.org> (raw)
In-Reply-To: <20220129032735.2410936-2-bryan.odonoghue@linaro.org>
On Sat, 29 Jan 2022 03:27:34 +0000, Bryan O'Donoghue wrote:
> snoc and snoc-mm in downstream use the same address space a mistake which
> we have carried over into upstream. In silicon terms snoc-mm has been
> tacked on to the original snoc which came from msm8916.
>
> Convert to a better description where snoc-mm is a sub-node of snoc, thus
> avoiding a mmio remap collision when using the RPM interconnect driver.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
> .../bindings/interconnect/qcom,rpm.yaml | 33 +++++++++++++++++--
> 1 file changed, 31 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-09 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 3:27 [PATCH v2 0/2] interconnect: qcom: msm8939: Coalesce snoc and snoc_mm Bryan O'Donoghue
2022-01-29 3:27 ` [PATCH v2 1/2] dt-bindings: interconnect: Convert snoc-mm to a sub-node of snoc Bryan O'Donoghue
2022-02-09 20:57 ` Rob Herring [this message]
2022-01-29 3:27 ` [PATCH v2 2/2] interconnect: qcom: msm8939: Remove snoc_mm specific regmap Bryan O'Donoghue
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=YgQqvVA0HaqWsAMA@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=benl@squareup.com \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.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