From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Danila Tikhonov <danila@jiaxyga.com>,
robdclark@gmail.com, quic_abhinavk@quicinc.com,
dmitry.baryshkov@linaro.org, sean@poorly.run,
marijn.suijten@somainline.org, airlied@gmail.com,
daniel@ffwll.ch, johan+linaro@kernel.org, andersson@kernel.org
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] drm/msm/adreno: Add support for SM7150 SoC machine
Date: Tue, 26 Sep 2023 20:40:30 +0200 [thread overview]
Message-ID: <42a1d0ab-4e8d-461d-bb2c-977a793e52b2@linaro.org> (raw)
In-Reply-To: <20230926174243.161422-2-danila@jiaxyga.com>
On 26.09.2023 19:42, Danila Tikhonov wrote:
> SM7150 has 5 power levels which correspond to 5 speed-bin values: 0,
> 128, 146, 167, 172. Speed-bin value is calulated as FMAX/4.8MHz round up
> to zero decimal places.
>
> Also a618 on SM7150 uses a615 zapfw. Add a squashed version (.mbn).
>
> Add this as machine = "qcom,sm7150", because speed-bin values are
> different from atoll (sc7180/sm7125).
>
> Signed-off-by: Danila Tikhonov <danila@jiaxyga.com>
> ---
What's the downstream dt name for 7150?
Do you have some more complete tree published somewhere?
Konrad
next prev parent reply other threads:[~2023-09-26 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 17:42 [PATCH v2 0/1] drm/msm/adreno: Add support for SM7150 Danila Tikhonov
2023-09-26 17:42 ` [PATCH v2 1/1] drm/msm/adreno: Add support for SM7150 SoC machine Danila Tikhonov
2023-09-26 18:40 ` Konrad Dybcio [this message]
[not found] ` <1695755445.902336096@f165.i.mail.ru>
2023-09-26 20:03 ` Konrad Dybcio
2023-10-16 14:32 ` Dmitry Baryshkov
2023-11-22 20:28 ` Konrad Dybcio
2023-11-22 21:03 ` Danila Tikhonov
2023-12-07 19:46 ` Akhil P Oommen
2023-12-07 19:48 ` Konrad Dybcio
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=42a1d0ab-4e8d-461d-bb2c-977a793e52b2@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=danila@jiaxyga.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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).