public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: qcom: ipq8064: add v2 dtsi variant
Date: Thu, 11 Aug 2022 14:53:20 +0200	[thread overview]
Message-ID: <62f4fbc1.170a0220.a7511.8fa9@mx.google.com> (raw)
In-Reply-To: <736b8e63-3d81-c34d-f693-7dc2120dd885@somainline.org>

On Thu, Aug 11, 2022 at 02:48:29PM +0200, Konrad Dybcio wrote:
> 
> 
> On 8.08.2022 15:35, Christian Marangi wrote:
> > On Mon, Aug 08, 2022 at 12:55:36PM +0200, Konrad Dybcio wrote:
> >>
> >>
> >> On 7.08.2022 15:00, Christian Marangi wrote:
> >>> On Mon, Jul 18, 2022 at 06:18:24PM +0200, Christian Marangi wrote:
> >>>> Add ipq8064-v2.0 dtsi variant that differ from original ipq8064 SoC for
> >>>> some additional pcie, sata and usb configuration values, additional
> >>>> reserved memory and serial output.
> >>>>
> >>>> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> >>>
> >>> Any news for this?Unless Qualcomm naming was different back then, you should simply merge
> >> all of these changes into ipq8064.dtsi, as v1 is often the pre-production,
> >> internal chip revision and only the last one (or the last and second-last)
> >> are shipped in production devices.
> >>
> > 
> > Mhh, this is not the case, there are dev board based on v1 and we also
> > have some device based on v1 (that have some difference for pci and usb)
> > One example is a Netgear r7500 where we have 2 revision one based on
> > ipq8064-v1.0 and one based on ipq8064-v2.0.
> Very interesting.. but if there really are devices shipping with v1, I guess
> it's the correct thing to keep both.
> 
> Konrad

Yep, that is the case. Main concern here is the fact that we have to
have smb208 dtsi variant for each revision and we can't reuse v2 for
ipq8065 and ipq8062 as they have different opp for the CPU core.
(currently not present but they will be added in the future when we will
finally have a correct krait cache devfreq driver)

-- 
	Ansuel

  reply	other threads:[~2022-08-11 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 16:18 [PATCH 1/3] ARM: dts: qcom: ipq8064: add v2 dtsi variant Christian Marangi
2022-07-18 16:18 ` [PATCH 2/3] ARM: dts: qcom: ipq8064: add ipq8062 variant Christian Marangi
2022-07-18 16:18 ` [PATCH 3/3] ARM: dts: qcom: ipq8064: add ipq8065 variant Christian Marangi
2022-08-07 13:00 ` [PATCH 1/3] ARM: dts: qcom: ipq8064: add v2 dtsi variant Christian Marangi
2022-08-08 10:55   ` Konrad Dybcio
2022-08-08 13:35     ` Christian Marangi
2022-08-11 12:48       ` Konrad Dybcio
2022-08-11 12:53         ` Christian Marangi [this message]
2022-08-29 23:45 ` (subset) " Bjorn Andersson

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=62f4fbc1.170a0220.a7511.8fa9@mx.google.com \
    --to=ansuelsmth@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=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.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