From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
"Adam Ford" <adam.ford@logicpd.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
devicetree <devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: omap3: Add cpu trips and cooling map for omap34/36 families
Date: Mon, 17 Aug 2020 14:48:47 +0300 [thread overview]
Message-ID: <20200817114847.GL2994@atomide.com> (raw)
In-Reply-To: <CAHCN7x+fnyXb+UO3xPd0nKeZNAPhRsXd5kTCAHxvg6hSt8Bx-A@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200805 13:17]:
> I know this is an old thread. I am trying to revisit some of the
> other issues that came about with this, but is there any way we can
> get patch 2/2 applied? It might not do anything unless the bandgap
> sensor is enabled, but it at least gets us one step closer for those
> who choose to enable it. With 1GHz support now available, it would be
> nice to have the precautions to protect the processor from running too
> fast when its too hot.
Sure seems OK to me. Care to resend as I no longer have it in my inbox?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
"Russell King" <linux@armlinux.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"Adam Ford" <adam.ford@logicpd.com>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: omap3: Add cpu trips and cooling map for omap34/36 families
Date: Mon, 17 Aug 2020 14:48:47 +0300 [thread overview]
Message-ID: <20200817114847.GL2994@atomide.com> (raw)
In-Reply-To: <CAHCN7x+fnyXb+UO3xPd0nKeZNAPhRsXd5kTCAHxvg6hSt8Bx-A@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200805 13:17]:
> I know this is an old thread. I am trying to revisit some of the
> other issues that came about with this, but is there any way we can
> get patch 2/2 applied? It might not do anything unless the bandgap
> sensor is enabled, but it at least gets us one step closer for those
> who choose to enable it. With 1GHz support now available, it would be
> nice to have the precautions to protect the processor from running too
> fast when its too hot.
Sure seems OK to me. Care to resend as I no longer have it in my inbox?
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-17 11:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 22:05 [PATCH 1/2] configs: ARM: omap2plus: Enable OMAP3_THERMAL Adam Ford
2019-10-07 22:05 ` Adam Ford
2019-10-07 22:05 ` [PATCH 2/2] ARM: dts: omap3: Add cpu trips and cooling map for omap34/36 families Adam Ford
2019-10-07 22:05 ` Adam Ford
2020-08-05 13:17 ` Adam Ford
2020-08-05 13:17 ` Adam Ford
2020-08-17 11:48 ` Tony Lindgren [this message]
2020-08-17 11:48 ` Tony Lindgren
2019-10-22 16:22 ` [PATCH 1/2] configs: ARM: omap2plus: Enable OMAP3_THERMAL Tony Lindgren
2019-10-22 16:22 ` Tony Lindgren
2019-10-22 19:01 ` Adam Ford
2019-10-22 19:01 ` Adam Ford
2019-10-22 22:19 ` Tony Lindgren
2019-10-22 22:19 ` Tony Lindgren
2019-10-23 4:41 ` H. Nikolaus Schaller
2019-10-23 4:41 ` H. Nikolaus Schaller
2019-10-23 4:41 ` H. Nikolaus Schaller
2019-10-23 14:36 ` Tony Lindgren
2019-10-23 14:36 ` Tony Lindgren
2019-11-08 20:02 ` Adam Ford
2019-11-08 20:02 ` Adam Ford
2019-11-08 20:02 ` Adam Ford
2019-11-08 20:51 ` Tony Lindgren
2019-11-08 20:51 ` Tony Lindgren
2019-11-08 21:04 ` Adam Ford
2019-11-08 21:04 ` Adam Ford
2019-11-08 21:21 ` Tony Lindgren
2019-11-08 21:21 ` Tony Lindgren
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=20200817114847.GL2994@atomide.com \
--to=tony@atomide.com \
--cc=adam.ford@logicpd.com \
--cc=aford173@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.