From: Icenowy Zheng <icenowy@aosc.io>
To: Samuel Holland <samuel@sholland.org>,
Vasily Khoruzhick <anarsoul@gmail.com>,
Yangtao Li <tiny.windzz@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] thermal: sun8i: add R329 THS
Date: Sat, 23 Apr 2022 07:41:51 +0800 [thread overview]
Message-ID: <a80fa962ac4a852b599ccf8e383e43e8eea7d12e.camel@aosc.io> (raw)
In-Reply-To: <f21303dd-14e2-80e6-ef07-2a1584d93b2e@sholland.org>
在 2022-04-22星期五的 18:39 -0500,Samuel Holland写道:
> Hi Icenowy,
>
> On 4/22/22 11:11 AM, icenowy@outlook.com wrote:
> > From: Icenowy Zheng <icenowy@aosc.io>
> >
> > The thermal sensor controller on R329 is similar to the one on H6,
> > but
> > with only one sensor. Calibration method is still unknown because
> > no
> > calibration is implemented in BSP kernel, neither is it documented
> > in
> > the user manual.
>
> Looking at the BSP smartx-r329-tina-for-jishu-community-v0.2, I see:
>
> ths_calib: calib@14 {
> reg = <0x14 4>;
> };
>
> And the BSP driver (drivers/thermal/sunxi_thermal-ng.c) claims that
> R329 uses
> the same calibration method as for H616. Maybe you are looking at an
> older BSP?
Yes. All these r329 work is done the last year during my internship at
Sipeed.
I will check the newer version of BSP and if okay I will add the
calibrate routine in the next revision.
>
> Regards,
> Samuel
>
> >
> > Add its support to sun8i-thermal driver. Calibrating it is now
> > prevented.
> >
> > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> > ---
> > drivers/thermal/sun8i_thermal.c | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/thermal/sun8i_thermal.c
> > b/drivers/thermal/sun8i_thermal.c
> > index d9cd23cbb671..3a2f381005b4 100644
> > --- a/drivers/thermal/sun8i_thermal.c
> > +++ b/drivers/thermal/sun8i_thermal.c
> > @@ -312,7 +312,8 @@ static int sun8i_ths_calibrate(struct
> > ths_device *tmdev)
> > goto out;
> > }
> >
> > - tmdev->chip->calibrate(tmdev, caldata, callen);
> > + if (tmdev->chip->calibrate)
> > + tmdev->chip->calibrate(tmdev, caldata, callen);
> >
> > kfree(caldata);
> > out:
> > @@ -628,6 +629,17 @@ static const struct ths_thermal_chip
> > sun50i_h6_ths = {
> > .calc_temp = sun8i_ths_calc_temp,
> > };
> >
> > +static const struct ths_thermal_chip sun50i_r329_ths = {
> > + .sensor_num = 1,
> > + .has_bus_clk_reset = true,
> > + .offset = 188744,
> > + .scale = 672,
> > + .temp_data_base = SUN50I_H6_THS_TEMP_DATA,
> > + .init = sun50i_h6_thermal_init,
> > + .irq_ack = sun50i_h6_irq_ack,
> > + .calc_temp = sun8i_ths_calc_temp,
> > +};
> > +
> > static const struct of_device_id of_ths_match[] = {
> > { .compatible = "allwinner,sun8i-a83t-ths", .data =
> > &sun8i_a83t_ths },
> > { .compatible = "allwinner,sun8i-h3-ths", .data =
> > &sun8i_h3_ths },
> > @@ -636,6 +648,7 @@ static const struct of_device_id of_ths_match[]
> > = {
> > { .compatible = "allwinner,sun50i-a100-ths", .data =
> > &sun50i_a100_ths },
> > { .compatible = "allwinner,sun50i-h5-ths", .data =
> > &sun50i_h5_ths },
> > { .compatible = "allwinner,sun50i-h6-ths", .data =
> > &sun50i_h6_ths },
> > + { .compatible = "allwinner,sun50i-r329-ths", .data =
> > &sun50i_r329_ths },
> > { /* sentinel */ },
> > };
> > MODULE_DEVICE_TABLE(of, of_ths_match);
> >
>
>
prev parent reply other threads:[~2022-04-22 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220422161156.1075227-1-icenowy@outlook.com>
2022-04-22 16:11 ` [PATCH 2/2] thermal: sun8i: add R329 THS icenowy
2022-04-22 18:49 ` Vasily Khoruzhick
2022-04-22 23:39 ` Samuel Holland
2022-04-22 23:41 ` Icenowy Zheng [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=a80fa962ac4a852b599ccf8e383e43e8eea7d12e.camel@aosc.io \
--to=icenowy@aosc.io \
--cc=amitk@kernel.org \
--cc=anarsoul@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=samuel@sholland.org \
--cc=tiny.windzz@gmail.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).