[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuJt9SF9Y2UsA4Jc@sirena.org.uk>
Date: Thu, 28 Jul 2022 12:07:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Zhiyong Tao <zhiyong.tao@...iatek.com>
Cc: lee.jones@...aro.org, robh+dt@...nel.org, matthias.bgg@...il.com,
lgirdwood@...il.com, eddie.huang@...iatek.com,
a.zummo@...ertech.it, alexandre.belloni@...tlin.com,
fshao@...omium.org, sen.chu@...iatek.com, hui.liu@...iatek.com,
allen-kh.cheng@...iatek.com, hsin-hsiung.wang@...iatek.com,
sean.wang@...iatek.com, macpaul.lin@...iatek.com,
wen.su@...iatek.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-rtc@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
zhiyong tao <zhiyong.tao@...iatk.com>
Subject: Re: [PATCH v2] pmic: add mt6366 regulator document
On Thu, Jul 28, 2022 at 02:27:49PM +0800, Zhiyong Tao wrote:
> + properties:
> + regulator-name:
> + pattern: "^v(dram1|core|coresshub|proc11|proc12|gpu|s2|modem|s1)$"
regulator-name should be free form text for the system integrator to
describe the use of the supply on their board, no constraints should be
placed on it by the regulator.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists