From: Iskren Chernev <iskren.chernev@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Jassi Brar <jassisinghbrar@gmail.com>,
Sivaprakash Murugesan <sivaprak@codeaurora.org>
Subject: Re: [PATCH v1 1/2] dt-bindings: mailbox: qcom: Add SM6115, SM4250 APCS compatible
Date: Wed, 14 Jul 2021 23:48:24 +0300 [thread overview]
Message-ID: <1bfa7490-2d00-15b0-0096-0fd9a27a491e@gmail.com> (raw)
In-Reply-To: <20210714180554.GA2855492@robh.at.kernel.org>
On 7/14/21 9:05 PM, Rob Herring wrote:
> On Tue, 22 Jun 2021 23:37:58 +0300, Iskren Chernev wrote:
>> Add compatible for the Qualcomm SM6115 and SM4250 APCS block to the
>> Qualcomm APCS binding.
>>
>> Signed-off-by: Iskren Chernev <iskren.chernev@gmail.com>
>> ---
>> .../devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>
> Acked-by: Rob Herring <robh@kernel.org>
>
As was discussed in the pinctrl series [1], the two compatibles are actually
different bins of the same SoC (codename bengal), so there would be only one
SoC dtsi, so I made v2 of all of my series, the v2 for this one is here [2]
Let me know what the right thing to do is (keep just sm6115 or have both around).
[1] https://lkml.org/lkml/2021/6/25/918
[2] https://lkml.org/lkml/2021/6/27/167
prev parent reply other threads:[~2021-07-14 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 20:37 [PATCH v1 1/2] dt-bindings: mailbox: qcom: Add SM6115, SM4250 APCS compatible Iskren Chernev
2021-06-22 20:37 ` [PATCH v1 2/2] mailbox: qcom: Add support for sm4125 sm6115 APCS IPC Iskren Chernev
2021-08-27 15:42 ` Nicolas Dechesne
2021-08-28 6:21 ` Iskren Chernev
2021-07-14 18:05 ` [PATCH v1 1/2] dt-bindings: mailbox: qcom: Add SM6115, SM4250 APCS compatible Rob Herring
2021-07-14 20:48 ` Iskren Chernev [this message]
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=1bfa7490-2d00-15b0-0096-0fd9a27a491e@gmail.com \
--to=iskren.chernev@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sivaprak@codeaurora.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).