From: Iskren Chernev <iskren.chernev@gmail.com>
To: Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 7/9] arm64: dts: qcom: sm6115: Add basic soc dtsi
Date: Sun, 4 Sep 2022 16:24:52 +0300 [thread overview]
Message-ID: <eac61be4-7d66-f07c-55ce-2ffb2caabbca@gmail.com> (raw)
In-Reply-To: <0583bec6-3bcd-b4b5-910e-bb82ec72028e@somainline.org>
On 9/3/22 22:46, Konrad Dybcio wrote:
>> + user_contig_mem: memory@fbc00000 {
>> + reg = <0x0 0xfbc00000 0x0 0x1000000>;
> Pretty sure this and linux_cma_mem don't need to be reserved at a precise
> location.. I might be wrong, though..
In downstream pretty much no reserved memory location have precise location.
How do you figure out which one is which?
>> + timer {
>> + compatible = "arm,armv8-timer";
>> + interrupts = <GIC_PPI 1 0xf08>,
>> + <GIC_PPI 2 0xf08>,
>> + <GIC_PPI 3 0xf08>,
>> + <GIC_PPI 0 0xf08>;
>> + clock-frequency = <19200000>;
> Remove clock-frequency if the platform boots without it.
And if not stick it in DTS?
next prev parent reply other threads:[~2022-09-04 13:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 17:41 [PATCH v2 0/9] Add support for sm6115,4250 and OnePlus Nord N100 Iskren Chernev
2022-09-03 17:41 ` [PATCH v2 1/9] dt-bindings: ufs: qcom: Add sm6115 binding Iskren Chernev
2022-09-06 8:29 ` Krzysztof Kozlowski
2022-09-06 8:38 ` Iskren Chernev
2022-09-03 17:41 ` [PATCH v2 2/9] dt-bindings: firmware: document Qualcomm SM6115 SCM Iskren Chernev
2022-09-03 18:56 ` Caleb Connolly
2022-09-03 18:58 ` Caleb Connolly
2022-09-04 19:14 ` Krzysztof Kozlowski
2022-09-05 7:32 ` Iskren Chernev
2022-09-08 19:42 ` Guru Das Srinagesh
2022-09-03 17:41 ` [PATCH v2 3/9] dt-bindings: nvmem: Add SoC compatible for sm6115 Iskren Chernev
2022-09-03 18:57 ` Caleb Connolly
2022-09-04 19:15 ` Krzysztof Kozlowski
2022-09-09 9:45 ` Srinivas Kandagatla
2022-09-03 17:41 ` [PATCH v2 4/9] dt-bindings: pinctrl: qcom: sm6115: Add reserved ranges Iskren Chernev
2022-09-03 18:59 ` Caleb Connolly
2022-09-08 8:09 ` Linus Walleij
2022-09-03 17:41 ` [PATCH v2 5/9] dt-bindings: arm: cpus: Add kryo240 compatible Iskren Chernev
2022-09-03 17:41 ` [PATCH v2 6/9] dt-bindings: arm: qcom: Add compatible for oneplus,billie2 phone Iskren Chernev
2022-09-03 19:08 ` Caleb Connolly
2022-09-03 17:41 ` [PATCH v2 7/9] arm64: dts: qcom: sm6115: Add basic soc dtsi Iskren Chernev
2022-09-03 19:46 ` Konrad Dybcio
2022-09-04 13:24 ` Iskren Chernev [this message]
2022-09-03 17:41 ` [PATCH v2 8/9] arm64: dts: qcom: sm4250: Add " Iskren Chernev
2022-09-06 8:29 ` Krzysztof Kozlowski
2022-09-03 17:41 ` [PATCH v2 9/9] arm64: dts: qcom: sm4250: Add support for oneplus-billie2 Iskren Chernev
2022-09-06 8:33 ` Krzysztof Kozlowski
2022-09-06 8:42 ` Iskren Chernev
2022-09-08 17:52 ` Iskren Chernev
2022-09-09 8:13 ` Krzysztof Kozlowski
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=eac61be4-7d66-f07c-55ce-2ffb2caabbca@gmail.com \
--to=iskren.chernev@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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=~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).