From: Adam Ford <aford173@gmail.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
"Adam Ford" <adam.ford@logicpd.com>, "Nishanth Menon" <nm@ti.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Grazvydas Ignotas" <notasas@gmail.com>
Subject: Re: [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family
Date: Wed, 30 Oct 2019 07:00:40 -0500 [thread overview]
Message-ID: <CAHCN7xL5sqLzaJ9b0721iAUeEb_pKB4QaeXfF94TZLQ7ZaS+bg@mail.gmail.com> (raw)
In-Reply-To: <C469028D-959D-4BD1-9226-C0190A197CE5@goldelico.com>
On Wed, Oct 30, 2019 at 3:40 AM H. Nikolaus Schaller <hns@goldelico.com> wrote:
>
> Hi Adam,
> what is the status of this RFC/PATCH?
I've submitted a formal 2-part patch [1] and [2], but Tony is
concerned about power consumption. As of right now, I don't have
cycles to work on it. My employer is about to release two new SOM's,
and I'm writing up some documentation on some of the older ones to
help some of the developers working on the new ones make their job go
quicker.
[1] - https://patchwork.kernel.org/patch/11178561/
[2] - https://patchwork.kernel.org/patch/11178563/
I requested if we could apply them as-is with 'status=disabled' for
now until the bus is fixed, but I think there was some push-back.
I'm trying to get to it. I am hoping to find a little time this weekend.
adam
>
> BR and thanks,
> Nikolaus
>
prev parent reply other threads:[~2019-10-30 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 15:37 [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family Adam Ford
2019-09-13 15:37 ` [RFC v2 2/2] ARM: omap3: Consolidate thermal references to common omap3 Adam Ford
2019-09-14 9:25 ` H. Nikolaus Schaller
2019-09-14 13:47 ` Adam Ford
2019-09-14 9:20 ` [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family H. Nikolaus Schaller
2019-09-14 13:42 ` Adam Ford
2019-09-14 14:38 ` H. Nikolaus Schaller
2019-09-14 16:12 ` Adam Ford
2019-10-07 15:11 ` Adam Ford
2019-10-07 15:44 ` H. Nikolaus Schaller
2019-10-07 17:25 ` Adam Ford
2019-10-30 8:39 ` H. Nikolaus Schaller
2019-10-30 12:00 ` Adam Ford [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=CAHCN7xL5sqLzaJ9b0721iAUeEb_pKB4QaeXfF94TZLQ7ZaS+bg@mail.gmail.com \
--to=aford173@gmail.com \
--cc=adam.ford@logicpd.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=notasas@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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 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.