From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Brian Norris <briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Stephen Barber <smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Caesar Wang <wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Subject: Re: [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators
Date: Wed, 22 Mar 2017 13:00:03 +0100 [thread overview]
Message-ID: <2038128.kuAi12yfFv@phil> (raw)
In-Reply-To: <20170320235344.126298-4-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Am Montag, 20. März 2017, 16:53:43 CET schrieb Brian Norris:
> Used for Gru/Kevin only, as they're the only ones which have a described
> CPU regulator. Also, I'm not sure we've validated this table non-Gru
> boards.
>
> At the same time, partially describe PWM regulators for Gru, so cpufreq
> doesn't think it can crank up the clock speed without changing the
> voltage. However, we don't yet have the DT bindings to fully describe
> the Over Voltage Protection (OVP) circuits on these boards. Without that
> description, we might end up changing the voltage too much, too fast.
>
> Add the pwm-regulator descriptions and associate the CPU OPPs, but leave
> them disabled.
>
> Signed-off-by: Brian Norris <briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
applied for 4.12 with Enric's Tested-tag after some small reordering of nodes/
properties.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators
Date: Wed, 22 Mar 2017 13:00:03 +0100 [thread overview]
Message-ID: <2038128.kuAi12yfFv@phil> (raw)
In-Reply-To: <20170320235344.126298-4-briannorris@chromium.org>
Am Montag, 20. M?rz 2017, 16:53:43 CET schrieb Brian Norris:
> Used for Gru/Kevin only, as they're the only ones which have a described
> CPU regulator. Also, I'm not sure we've validated this table non-Gru
> boards.
>
> At the same time, partially describe PWM regulators for Gru, so cpufreq
> doesn't think it can crank up the clock speed without changing the
> voltage. However, we don't yet have the DT bindings to fully describe
> the Over Voltage Protection (OVP) circuits on these boards. Without that
> description, we might end up changing the voltage too much, too fast.
>
> Add the pwm-regulator descriptions and associate the CPU OPPs, but leave
> them disabled.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied for 4.12 with Enric's Tested-tag after some small reordering of nodes/
properties.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Stephen Barber <smbarber@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>
Subject: Re: [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators
Date: Wed, 22 Mar 2017 13:00:03 +0100 [thread overview]
Message-ID: <2038128.kuAi12yfFv@phil> (raw)
In-Reply-To: <20170320235344.126298-4-briannorris@chromium.org>
Am Montag, 20. März 2017, 16:53:43 CET schrieb Brian Norris:
> Used for Gru/Kevin only, as they're the only ones which have a described
> CPU regulator. Also, I'm not sure we've validated this table non-Gru
> boards.
>
> At the same time, partially describe PWM regulators for Gru, so cpufreq
> doesn't think it can crank up the clock speed without changing the
> voltage. However, we don't yet have the DT bindings to fully describe
> the Over Voltage Protection (OVP) circuits on these boards. Without that
> description, we might end up changing the voltage too much, too fast.
>
> Add the pwm-regulator descriptions and associate the CPU OPPs, but leave
> them disabled.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied for 4.12 with Enric's Tested-tag after some small reordering of nodes/
properties.
Heiko
next prev parent reply other threads:[~2017-03-22 12:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:53 [PATCH v3 0/4] arm64: dts: rockchip: support Google Kevin Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` [PATCH v3 1/4] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` Brian Norris
[not found] ` <20170320235344.126298-2-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-22 9:01 ` Heiko Stuebner
2017-03-22 9:01 ` Heiko Stuebner
2017-03-22 9:01 ` Heiko Stuebner
2017-03-22 17:56 ` Brian Norris
2017-03-22 17:56 ` Brian Norris
[not found] ` <20170320235344.126298-1-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-20 23:53 ` [PATCH v3 2/4] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-21 11:02 ` Enric Balletbo Serra
2017-03-21 11:02 ` Enric Balletbo Serra
2017-03-21 11:02 ` Enric Balletbo Serra
2017-03-22 11:59 ` Heiko Stuebner
2017-03-22 11:59 ` Heiko Stuebner
2017-03-22 11:59 ` Heiko Stuebner
2017-03-22 17:57 ` Brian Norris
2017-03-22 17:57 ` Brian Norris
2017-03-22 17:57 ` Brian Norris
2017-03-20 23:53 ` [PATCH v3 4/4] arm64: dts: rockchip: add regulator info for Kevin digitizer Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` Brian Norris
[not found] ` <20170320235344.126298-5-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-22 8:26 ` Heiko Stuebner
2017-03-22 8:26 ` Heiko Stuebner
2017-03-22 8:26 ` Heiko Stuebner
2017-03-22 18:14 ` Brian Norris
2017-03-22 18:14 ` Brian Norris
2017-03-22 18:14 ` Brian Norris
[not found] ` <20170322181441.GC98450-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-03-22 23:57 ` Heiko Stuebner
2017-03-22 23:57 ` Heiko Stuebner
2017-03-22 23:57 ` Heiko Stuebner
2017-03-20 23:53 ` [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators Brian Norris
2017-03-20 23:53 ` Brian Norris
2017-03-20 23:53 ` Brian Norris
[not found] ` <20170320235344.126298-4-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-21 11:04 ` Enric Balletbo Serra
2017-03-21 11:04 ` Enric Balletbo Serra
2017-03-21 11:04 ` Enric Balletbo Serra
2017-03-22 12:00 ` Heiko Stuebner [this message]
2017-03-22 12:00 ` Heiko Stuebner
2017-03-22 12:00 ` Heiko Stuebner
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=2038128.kuAi12yfFv@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.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.