mbox series

[v2,0/2] thermal: amlogic: introduce A1 SoC family Thermal Sensor controller

Message ID 20240328191322.17551-1-ddrokosov@salutedevices.com (mailing list archive)
Headers show
Series thermal: amlogic: introduce A1 SoC family Thermal Sensor controller | expand

Message

Dmitry Rokosov March 28, 2024, 7:13 p.m. UTC
It is primarily based on the G12A thermal controller, with only a slight
variation in the offset value of the efuse parameters. Therefore, this
patch series provides appropriate platform data and dt-bindings to
ensure proper support.

Changes v2 since v1 at [1]:
    - provide Neil RvB
    - remove 'amlogic,a1-thermal' fallback, cause it's not needed

Links:
    [1] https://lore.kernel.org/all/20240328133802.15651-1-ddrokosov@salutedevices.com/

Dmitry Rokosov (2):
  dt-bindings: thermal: amlogic: add support for A1 thermal sensor
  thermal: amlogic: support A1 SoC family Thermal Sensor controller

 .../devicetree/bindings/thermal/amlogic,thermal.yaml | 12 +++++++-----
 drivers/thermal/amlogic_thermal.c                    | 10 ++++++++++
 2 files changed, 17 insertions(+), 5 deletions(-)

Comments

Daniel Lezcano April 4, 2024, 12:23 p.m. UTC | #1
On 28/03/2024 20:13, Dmitry Rokosov wrote:
> It is primarily based on the G12A thermal controller, with only a slight
> variation in the offset value of the efuse parameters. Therefore, this
> patch series provides appropriate platform data and dt-bindings to
> ensure proper support.


Applied, thanks
Dmitry Rokosov April 17, 2024, 8:40 a.m. UTC | #2
Hello Daniel,

Could you please let me know in which repository you have applied this
change? I am trying to cherry-pick the original applied commit and apply
it to our internal mainline branch instead of the internal commit.
However, I am unable to find the applied series in any of the
repositories on git.kernel.org.

On Thu, Apr 04, 2024 at 02:23:21PM +0200, Daniel Lezcano wrote:
> On 28/03/2024 20:13, Dmitry Rokosov wrote:
> > It is primarily based on the G12A thermal controller, with only a slight
> > variation in the offset value of the efuse parameters. Therefore, this
> > patch series provides appropriate platform data and dt-bindings to
> > ensure proper support.
> 
> 
> Applied, thanks
Dmitry Rokosov April 26, 2024, 7:31 a.m. UTC | #3
Hello Neil,

I hope you're doing well. I was wondering if you could assist me with
below problem.

I'm a bit confused about which kernel repository the series was applied
to. I asked Daniel about it, but unfortunately, I didn't receive any
feedback from him. Could you provide some clarification on this matter?

Thank you in advance for your help.

On Wed, Apr 17, 2024 at 11:40:07AM +0300, Dmitry Rokosov wrote:
> Hello Daniel,
> 
> Could you please let me know in which repository you have applied this
> change? I am trying to cherry-pick the original applied commit and apply
> it to our internal mainline branch instead of the internal commit.
> However, I am unable to find the applied series in any of the
> repositories on git.kernel.org.
> 
> On Thu, Apr 04, 2024 at 02:23:21PM +0200, Daniel Lezcano wrote:
> > On 28/03/2024 20:13, Dmitry Rokosov wrote:
> > > It is primarily based on the G12A thermal controller, with only a slight
> > > variation in the offset value of the efuse parameters. Therefore, this
> > > patch series provides appropriate platform data and dt-bindings to
> > > ensure proper support.
> > 
> > 
> > Applied, thanks
>
Daniel Lezcano April 26, 2024, 7:57 a.m. UTC | #4
Hi Dmitry,

On 26/04/2024 09:31, Dmitry Rokosov wrote:
> Hello Neil,
> 
> I hope you're doing well. I was wondering if you could assist me with
> below problem.
> 
> I'm a bit confused about which kernel repository the series was applied
> to. I asked Daniel about it, but unfortunately, I didn't receive any
> feedback from him. Could you provide some clarification on this matter?
> 
> Thank you in advance for your help.

I was OoO the last two weeks.

Your series is in my tree [1], which is pulled automatically by the 
linux-pm tree in its bleeding-edge branch.

Today, this branch will move to the linux-next branch [2] which will 
also be pulled by the linux-pm/next branch automatically.

Hope that helps and sorry for the delay to answer

   -- Daniel

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git/log/?h=thermal/bleeding-edge

[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git/log/?h=thermal/linux-next
Dmitry Rokosov May 3, 2024, 7:52 a.m. UTC | #5
Hello Daniel,

On Fri, Apr 26, 2024 at 09:57:29AM +0200, Daniel Lezcano wrote:
> 
> Hi Dmitry,
> 
> On 26/04/2024 09:31, Dmitry Rokosov wrote:
> > Hello Neil,
> > 
> > I hope you're doing well. I was wondering if you could assist me with
> > below problem.
> > 
> > I'm a bit confused about which kernel repository the series was applied
> > to. I asked Daniel about it, but unfortunately, I didn't receive any
> > feedback from him. Could you provide some clarification on this matter?
> > 
> > Thank you in advance for your help.
> 
> I was OoO the last two weeks.
> 
> Your series is in my tree [1], which is pulled automatically by the linux-pm
> tree in its bleeding-edge branch.
> 
> Today, this branch will move to the linux-next branch [2] which will also be
> pulled by the linux-pm/next branch automatically.
> 
> Hope that helps and sorry for the delay to answer
> 
>   -- Daniel
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git/log/?h=thermal/bleeding-edge
> 
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git/log/?h=thermal/linux-next

Thanks a lot for the update! Now I see the patches in the above repos.