From: Doug Anderson <dianders@chromium.org>
To: Yunlong Jia <yunlong.jia@ecs.corp-partner.google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bob Moragues <moragues@chromium.org>,
Henry Sun <henrysun@google.com>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360
Date: Fri, 26 Aug 2022 17:05:55 -0700 [thread overview]
Message-ID: <CAD=FV=U2N2gd6jCsxucwuU1xxnzBc5nL3odQp7vcQXmJsjwHOQ@mail.gmail.com> (raw)
In-Reply-To: <20220826102513.1.If97ef7a7d84bcc2cf20e0479b3e00c4a8fb5a2fd@changeid>
Hi,
On Fri, Aug 26, 2022 at 3:27 AM Yunlong Jia
<yunlong.jia@ecs.corp-partner.google.com> wrote:
>
> pazquel360 is an extension project based on pazquel.
> We create 3 sku on pazquel360:
> sku 20 for LTE with physical SIM _and_ eSIM and WiFi
> sku 21 for WiFi only
> sku 22 for LTE with only a physical SIM
> Both sku20 and sku22 are LTE SKUs.
> One has the eSIM stuffed and one doesn't.
> There is a single shared device tree for the two.
>
> Signed-off-by: Yunlong Jia <yunlong.jia@ecs.corp-partner.google.com>
>
> ---
>
> Documentation/devicetree/bindings/arm/qcom.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
Reviewed-by: Douglas Anderson <dianders@chromium.org>
prev parent reply other threads:[~2022-08-27 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 10:26 [PATCH 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360 Yunlong Jia
2022-08-26 10:26 ` [PATCH 2/2] arm64: dts: qcom: Add sc7180-pazquel360 Yunlong Jia
2022-08-27 0:05 ` Doug Anderson
2022-08-26 17:41 ` [PATCH 1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360 Krzysztof Kozlowski
2022-08-27 0:05 ` Doug Anderson [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='CAD=FV=U2N2gd6jCsxucwuU1xxnzBc5nL3odQp7vcQXmJsjwHOQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=henrysun@google.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moragues@chromium.org \
--cc=robh+dt@kernel.org \
--cc=yunlong.jia@ecs.corp-partner.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;
as well as URLs for NNTP newsgroup(s).