From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Adam Ford" <aford173@gmail.com>,
"André Roth" <neolynx@gmail.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Enric Balletbo i Serra" <eballetbo@gmail.com>,
"Javier Martinez Canillas" <javier@dowhile0.org>,
"Roger Quadros" <rogerq@ti.com>,
"Teresa Remmet" <t.remmet@phytec.de>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" if run in multi_regulator mode
Date: Mon, 16 Sep 2019 09:24:49 -0700 [thread overview]
Message-ID: <20190916162449.GB52127@atomide.com> (raw)
In-Reply-To: <1c803be8060fb99b7d92e2f5cde3c0e1962fbe2b.1568224033.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [190911 17:48]:
> In preparation for using the multi_regulator capability of
> this driver for handling the ABB LDO for OPP1G of the omap36xx
> we have to take care that the (legacy) vdd-supply name is
> cpu0-supply = <&vcc>;
>
> To do this we add another field to the SoC description table which
> optionally can specify a list of regulator names.
>
> For omap36xx we define "cpu0-supply" and "vbb-supply".
>
> The default remains "vdd-supply" and "vbb-supply".
Acked-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org, letux-kernel@openphoenux.org,
linux-pm@vger.kernel.org,
"Enric Balletbo i Serra" <eballetbo@gmail.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"André Roth" <neolynx@gmail.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
kernel@pyra-handheld.com, "Teresa Remmet" <t.remmet@phytec.de>,
"Javier Martinez Canillas" <javier@dowhile0.org>,
linux-omap@vger.kernel.org, "Adam Ford" <aford173@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Roger Quadros" <rogerq@ti.com>
Subject: Re: [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" if run in multi_regulator mode
Date: Mon, 16 Sep 2019 09:24:49 -0700 [thread overview]
Message-ID: <20190916162449.GB52127@atomide.com> (raw)
In-Reply-To: <1c803be8060fb99b7d92e2f5cde3c0e1962fbe2b.1568224033.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [190911 17:48]:
> In preparation for using the multi_regulator capability of
> this driver for handling the ABB LDO for OPP1G of the omap36xx
> we have to take care that the (legacy) vdd-supply name is
> cpu0-supply = <&vcc>;
>
> To do this we add another field to the SoC description table which
> optionally can specify a list of regulator names.
>
> For omap36xx we define "cpu0-supply" and "vbb-supply".
>
> The default remains "vdd-supply" and "vbb-supply".
Acked-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
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:[~2019-09-16 16:24 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:47 [PATCH v3 0/8] OMAP3: convert opp-v1 to opp-v2 and read speed binned / 720MHz grade bits H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 1/8] cpufreq: ti-cpufreq: add support for omap34xx and omap36xx H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 19:05 ` Adam Ford
2019-09-11 19:05 ` Adam Ford
2019-09-11 19:05 ` Adam Ford
2019-09-11 17:47 ` [PATCH v3 2/8] ARM: dts: omap34xx & omap36xx: replace opp-v1 tables by opp-v2 for H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 3/8] DTS: bindings: omap: update bindings documentation H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 4/8] ARM: dts: omap3: bulk convert compatible to be explicitly ti,omap3430 or ti,omap3630 or ti,am3517 H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 4/8] ARM: dts: omap3: bulk convert compatible to be explicitly ti, omap3430 or ti, omap3630 or ti, am3517 H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" if run in multi_regulator mode H. Nikolaus Schaller
2019-09-11 17:47 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" " H. Nikolaus Schaller
2019-09-16 16:24 ` Tony Lindgren [this message]
2019-09-16 16:24 ` Tony Lindgren
2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" " Rob Herring
2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" " Rob Herring
2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" " Rob Herring
2019-09-11 17:47 ` [PATCH v3 6/8] ARM: dts: omap36xx: using OPP1G needs to control the abb_ldo H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-13 21:13 ` Adam Ford
2019-09-13 21:13 ` Adam Ford
2019-09-14 9:30 ` H. Nikolaus Schaller
2019-09-14 9:30 ` H. Nikolaus Schaller
2019-09-16 16:25 ` Tony Lindgren
2019-09-16 16:25 ` Tony Lindgren
2019-09-11 17:47 ` [PATCH v3 7/8] cpufreq: ti-cpufreq: Add support for AM3517 H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-16 16:26 ` Tony Lindgren
2019-09-16 16:26 ` Tony Lindgren
2019-09-11 17:47 ` [PATCH v3 8/8] ARM: dts: Add OPP-V2 table " H. Nikolaus Schaller
2019-09-11 17:47 ` H. Nikolaus Schaller
2019-09-16 16:26 ` Tony Lindgren
2019-09-16 16:26 ` Tony Lindgren
2019-09-16 16:28 ` [PATCH v3 0/8] OMAP3: convert opp-v1 to opp-v2 and read speed binned / 720MHz grade bits Tony Lindgren
2019-09-16 16:28 ` Tony Lindgren
2019-09-17 14:35 ` H. Nikolaus Schaller
2019-09-17 14:35 ` H. Nikolaus Schaller
2019-10-02 5:47 ` H. Nikolaus Schaller
2019-10-02 5:47 ` H. Nikolaus Schaller
2019-10-02 5:47 ` H. Nikolaus Schaller
2019-10-02 9:00 ` Viresh Kumar
2019-10-02 9:00 ` Viresh Kumar
2019-10-02 9:00 ` Viresh Kumar
2019-10-10 10:45 ` Viresh Kumar
2019-10-10 10:45 ` Viresh Kumar
2019-11-08 20:08 ` Adam Ford
2019-11-08 20:08 ` Adam Ford
2019-11-09 6:12 ` H. Nikolaus Schaller
2019-11-09 6:12 ` H. Nikolaus Schaller
2019-11-09 6:12 ` H. Nikolaus Schaller
2019-11-09 10:02 ` Adam Ford
2019-11-09 10:02 ` Adam Ford
2019-11-09 10:02 ` Adam Ford
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=20190916162449.GB52127@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@gmail.com \
--cc=hns@goldelico.com \
--cc=javier@dowhile0.org \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neolynx@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=t.remmet@phytec.de \
--cc=viresh.kumar@linaro.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.