Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Kostya Porotchkin <kostap@marvell.com>
To:     Russell King - ARM Linux admin <linux@armlinux.org.uk>,
        Jon Nettleton <jon@solid-run.com>
CC:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "robh+dt@kernel.org" <robh+dt@kernel.org>,
        "sebastian.hesselbarth@gmail.com" <sebastian.hesselbarth@gmail.com>,
        "gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
        "andrew@lunn.ch" <andrew@lunn.ch>,
        "mw@semihalf.com" <mw@semihalf.com>,
        "jaz@semihalf.com" <jaz@semihalf.com>,
        Nadav Haklai <nadavh@marvell.com>,
        Stefan Chulski <stefanc@marvell.com>,
        "Ben Peled" <bpeled@marvell.com>
Subject: RE: [EXT] Re: [PATCH v2 01/12] fix: arm64: dts: replace wrong
 regulator on ap emmc
Thread-Topic: [EXT] Re: [PATCH v2 01/12] fix: arm64: dts: replace wrong
 regulator on ap emmc
Thread-Index: AQHW/7Zxt24oayXyI0uXyCrLQTNSLapSyIYAgAAzcpA=
Date:   Thu, 11 Feb 2021 13:57:25 +0000
Message-ID: <DM5PR18MB1452DFBCDCE970384339545BCA8C9@DM5PR18MB1452.namprd18.prod.outlook.com>
References: <20210210140949.32515-1-kostap@marvell.com>
 <20210210140949.32515-2-kostap@marvell.com>
 <20210211105222.GY1463@shell.armlinux.org.uk>
In-Reply-To: <20210211105222.GY1463@shell.armlinux.org.uk>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 328696c6-5d4a-4150-9b10-08d8ce94f68e
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Feb 2021 13:57:25.8068
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: l2LoM2ZRbGMSNSfZ1oDqfaS6XUV/hAN6v1yMFPJ/VEr7qfuw2+JO/aCCxMeBXQd8MTes+6ePDbm05YYAR1qD/Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR1801MB1930
X-OriginatorOrg: marvell.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.737
 definitions=2021-02-11_06:2021-02-10,2021-02-11 signatures=0
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> ----------------------------------------------------------------------
> On Wed, Feb 10, 2021 at 04:09:38PM +0200, kostap@marvell.com wrote:
> > From: Konstantin Porotchkin <kostap@marvell.com>
> >
> > Replace wrong regulator in AP0 eMMC definition on MacchiatoBIN board
> > with 3.3V regulator.
> > The MacchiatoBIN board has no 1.8V regulator connected to AP0 eMMC
> > (ap0_sdhci0) interface.
>=20
> There seems to be some variability between Macchiatobin versions accordin=
g
> to the schematics.
>=20
> The VDDO_H supply is connected to the eMMC VCCQ pins, and is also
> connected to the AP_VDDO_H pins. It is wired to the 1.8V regulator on rev=
 1.1
> schematics, but hard-wired to the 3.3V regulator on rev 1.3 schematics.
>=20
> This needs clarification from SolidRun before the patch can be accepted -=
 was
> VDDO_H ever wired to the 1.8V regulator on production hardware?
>=20
[KP] I will try to find a relevant contact in SolidRun for get this issue c=
larified.

Kosta
> --
> RMK's Patch system: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
> 3A__www.armlinux.org.uk_developer_patches_&d=3DDwIBAg&c=3DnKjWec2b6R0
> mOyPaz7xtfQ&r=3D-
> N9sN4p5NSr0JGQoQ_2UCOgAqajG99W1EbSOww0WU8o&m=3D7JAOlRdnL-
> 42trjLrz_DOgZhvVuW8Skolb3bL-wJ6lo&s=3D9IB3Lxht5IQHTINpyLfX-
> KC8AmqqHn0cCSSuQuTvfkE&e=3D
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!