[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200717144056.GB3301@Mani-XPS-13-9360>
Date: Fri, 17 Jul 2020 20:10:57 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Amit Tomer <amittomer25@...il.com>
Cc: Andre Przywara <andre.przywara@....com>,
Andreas Färber <afaerber@...e.de>,
Rob Herring <robh+dt@...nel.org>, cristian.ciocaltea@...il.com,
linux-kernel@...r.kernel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-actions@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 10/10] arm64: dts: actions: Add uSD support for
Cubieboard7
On Mon, Jul 13, 2020 at 02:38:55PM +0530, Amit Tomer wrote:
> Hi,
>
> > Fixed regulators are used to nicely model the regulators which aren't tied to
> > any PMIC. But for some cases we use them to represent supplies when there is
> > no support for the specific PMIC present in the kernel and they are turned
> > on/configured by the bootloader (this is what happening here).
> >
> > And there is no use of declaring fixed regulators when there is no consumer.
> > Even if you don't define these, the corresponding supplies in the board will
> > always be in the same state configured by the bootloader. So I'd suggest you
> > to remove this for now.
>
> Checked the schematics and regulator name is the same for both eMMC and uSD
Okay, fine.
> Shall we keep uSD regulator sd_vcc to be consistent across ACTIONS platform?
>
No. As I said before it depends on the individual board schematics.
Thanks,
Mani
> > Since I don't have the schematics to check, please make sure you name the
> > regulators as mentioned in the schematics (this could vary from board to board,
> > so don't just copy from others).
> >
>
> Sure, point noted.
>
> Thanks
> -Amit.
Powered by blists - more mailing lists