From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH RFT 0/3] drivers/thermal/rcar_gen3_thermal: add Gen4 fuse support
Date: Sat, 11 Feb 2023 14:30:52 +0100 [thread overview]
Message-ID: <Y+eYjJIITr2rgz7e@sleipner.dyn.berto.se> (raw)
In-Reply-To: <20230211084728.27832-1-wsa+renesas@sang-engineering.com>
Hi Wolfram,
Thanks for your work.
On 2023-02-11 09:47:24 +0100, Wolfram Sang wrote:
> R-Car Gen4 has the fuse registers at different locations and with
> different names, but with the same purpose. So, first refactor IP core
> differences into a 'info' struct, then add the fuse_read callback to it.
>
> Patches are based on top of:
>
> [PATCH v2 0/3] drivers/thermal/rcar_gen3_thermal: Fix device initialization
> [PATCH 0/2] thermal: Add support for R-Car V4H
>
> They have been tested on R-Car H3 ES2.0 and M3-N against regressions.
> Actual testing of the new fuses on S4-8 still needs to be done because I
> don't have access to such HW.
>
> @Shimoda-san: maybe the BSP team or Test team can test these patches?
>
> Looking forward to other review comments, too, of course.
For the whole series,
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
I boot tested this on V4H, but on that board the fuses where not set so
the driver fall-back to the default values. We had a similar situation
when we enabled fuses for Gen3. IIRC the BSP team helped out testing
that on a board that had the fuses set.
>
> Happy hacking,
>
> Wolfram
>
>
> Wolfram Sang (3):
> drivers/thermal/rcar_gen3_thermal: introduce 'info' structure
> drivers/thermal/rcar_gen3_thermal: refactor reading fuses into
> seprarate function
> drivers/thermal/rcar_gen3_thermal: add reading fuses for Gen4
>
> drivers/thermal/rcar_gen3_thermal.c | 141 ++++++++++++++++++++--------
> 1 file changed, 102 insertions(+), 39 deletions(-)
>
> --
> 2.30.2
>
--
Kind Regards,
Niklas Söderlund
prev parent reply other threads:[~2023-02-11 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 8:47 Wolfram Sang
2023-02-11 8:47 ` [PATCH RFT 1/3] drivers/thermal/rcar_gen3_thermal: introduce 'info' structure Wolfram Sang
2023-02-11 8:47 ` [PATCH RFT 2/3] drivers/thermal/rcar_gen3_thermal: refactor reading fuses into seprarate function Wolfram Sang
2023-02-11 8:47 ` [PATCH RFT 3/3] drivers/thermal/rcar_gen3_thermal: add reading fuses for Gen4 Wolfram Sang
2023-02-11 13:30 ` Niklas Söderlund [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=Y+eYjJIITr2rgz7e@sleipner.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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
all inboxes | Powered by JetHome®