From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] ARM: dts: dra7: Add vbb-supply to cpu and additional voltages
Date: Thu, 21 Dec 2017 07:51:08 -0800 [thread overview]
Message-ID: <20171221155108.GW3875@atomide.com> (raw)
In-Reply-To: <82512a74-023d-5000-7c8d-e3a681503032@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [171221 15:42]:
> On 12/21/2017 09:15 AM, Tony Lindgren wrote:
> > * Dave Gerlach <d-gerlach@ti.com> [171219 15:27]:
> >> Add a vbb-supply phandle to the cpus node and also add an additional
> >> triplet of voltages for each OPP in the operating-points-v2 table to
> >> make use of the multi regulator support in the OPP core and provide the
> >> vbb regulator for use by the ti-opp-supply driver.
> >
> > Sounds like these depend on the ti-opp-supply being available first?
> >
>
> Yes that would be best, but the ti-opp-supply patches are already in linux-next.
OK applying into omap-for-v4.16/dt then thanks.
Regards,
Tony
next prev parent reply other threads:[~2017-12-21 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:24 [PATCH 0/8] ARM: dts: dra7: Add ti-opp-supply nodes and enable 1.5 GHz Dave Gerlach
2017-12-19 15:24 ` [PATCH 1/8] ARM: dts: dra7: Add vbb-supply to cpu and additional voltages Dave Gerlach
2017-12-21 15:15 ` Tony Lindgren
2017-12-21 15:40 ` Dave Gerlach
2017-12-21 15:51 ` Tony Lindgren [this message]
2017-12-19 15:24 ` [PATCH 2/8] ARM: dts: dra7: Add MPU OPP supply node Dave Gerlach
2017-12-19 15:24 ` [PATCH 3/8] ARM: dts: dra7: Enable 1.5 GHz operation for the CPU Dave Gerlach
2017-12-19 15:24 ` [PATCH 4/8] ARM: dts: am57xx-beagle-x15-common: Add cpu0 vdd supply Dave Gerlach
2017-12-19 15:24 ` [PATCH 5/8] ARM: dts: dra7-evm: " Dave Gerlach
2017-12-19 15:24 ` [PATCH 6/8] ARM: dts: dra72-evm-tps65917: " Dave Gerlach
2017-12-19 15:24 ` [PATCH 7/8] ARM: dts: am571x-idk: " Dave Gerlach
2017-12-19 15:24 ` [PATCH 8/8] ARM: dts: am572x-idk: " Dave Gerlach
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=20171221155108.GW3875@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).