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
Date: Thu, 11 Feb 2021 13:57:25 +0000 [thread overview]
Message-ID: <DM5PR18MB1452DFBCDCE970384339545BCA8C9@DM5PR18MB1452.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210211105222.GY1463@shell.armlinux.org.uk>
> ----------------------------------------------------------------------
> 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.
>
> There seems to be some variability between Macchiatobin versions according
> to the schematics.
>
> 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.
>
> This needs clarification from SolidRun before the patch can be accepted - was
> VDDO_H ever wired to the 1.8V regulator on production hardware?
>
[KP] I will try to find a relevant contact in SolidRun for get this issue clarified.
Kosta
> --
> RMK's Patch system: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.armlinux.org.uk_developer_patches_&d=DwIBAg&c=nKjWec2b6R0
> mOyPaz7xtfQ&r=-
> N9sN4p5NSr0JGQoQ_2UCOgAqajG99W1EbSOww0WU8o&m=7JAOlRdnL-
> 42trjLrz_DOgZhvVuW8Skolb3bL-wJ6lo&s=9IB3Lxht5IQHTINpyLfX-
> KC8AmqqHn0cCSSuQuTvfkE&e=
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: Kostya Porotchkin <kostap@marvell.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Jon Nettleton <jon@solid-run.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"jaz@semihalf.com" <jaz@semihalf.com>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nadav Haklai <nadavh@marvell.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Stefan Chulski <stefanc@marvell.com>,
"mw@semihalf.com" <mw@semihalf.com>,
Ben Peled <bpeled@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>
Subject: RE: [EXT] Re: [PATCH v2 01/12] fix: arm64: dts: replace wrong regulator on ap emmc
Date: Thu, 11 Feb 2021 13:57:25 +0000 [thread overview]
Message-ID: <DM5PR18MB1452DFBCDCE970384339545BCA8C9@DM5PR18MB1452.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210211105222.GY1463@shell.armlinux.org.uk>
> ----------------------------------------------------------------------
> 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.
>
> There seems to be some variability between Macchiatobin versions according
> to the schematics.
>
> 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.
>
> This needs clarification from SolidRun before the patch can be accepted - was
> VDDO_H ever wired to the 1.8V regulator on production hardware?
>
[KP] I will try to find a relevant contact in SolidRun for get this issue clarified.
Kosta
> --
> RMK's Patch system: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.armlinux.org.uk_developer_patches_&d=DwIBAg&c=nKjWec2b6R0
> mOyPaz7xtfQ&r=-
> N9sN4p5NSr0JGQoQ_2UCOgAqajG99W1EbSOww0WU8o&m=7JAOlRdnL-
> 42trjLrz_DOgZhvVuW8Skolb3bL-wJ6lo&s=9IB3Lxht5IQHTINpyLfX-
> KC8AmqqHn0cCSSuQuTvfkE&e=
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
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:[~2021-02-11 14:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 14:09 [PATCH v2 00/12] Device tree fixes for Armada family kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 01/12] fix: arm64: dts: replace wrong regulator on ap emmc kostap
2021-02-10 14:09 ` kostap
2021-02-11 10:52 ` Russell King - ARM Linux admin
2021-02-11 10:52 ` Russell King - ARM Linux admin
2021-02-11 13:57 ` Kostya Porotchkin [this message]
2021-02-11 13:57 ` [EXT] " Kostya Porotchkin
2021-02-11 14:02 ` Russell King - ARM Linux admin
2021-02-11 14:02 ` Russell King - ARM Linux admin
2021-02-10 14:09 ` [PATCH v2 02/12] dts: mvebu: Update A8K AP806/AP807 SDHCI settings kostap
2021-02-10 14:09 ` kostap
2021-02-11 10:42 ` Russell King - ARM Linux admin
2021-02-11 10:42 ` Russell King - ARM Linux admin
2021-02-10 14:09 ` [PATCH v2 03/12] dts: mvebu: Add pin control definitions for SDIO interafce kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 04/12] fix: dts: a8k: Add CP eMMC regulator and update device parameters kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 05/12] arm64: dts: marvell: armada-3720-db: add comphy references kostap
2021-02-10 14:09 ` kostap
2021-02-11 23:31 ` Pali Rohár
2021-02-11 23:31 ` Pali Rohár
2021-02-10 14:09 ` [PATCH v2 06/12] arm64: dts: marvell: armada-3270-espressobin: " kostap
2021-02-10 14:09 ` kostap
2021-02-11 23:28 ` Pali Rohár
2021-02-11 23:28 ` Pali Rohár
2021-02-10 14:09 ` [PATCH v2 07/12] fix: ARM64: dts: cp110: Switch to 8-bit ECC NAND setting kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 08/12] arm64: dts: marvell: armada-3720-db: add eeprom description kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 09/12] dts: a3700: enable dma coherence kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 10/12] dts: marvell: add 2 eeprom properties to A8K DB device tree kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 11/12] dts: marvell: add 2 eeprom properties to A7K " kostap
2021-02-10 14:09 ` kostap
2021-02-10 14:09 ` [PATCH v2 12/12] arm64: dts: fix the Armada 8040 DB AP SDHCI bus width kostap
2021-02-10 14:09 ` kostap
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=DM5PR18MB1452DFBCDCE970384339545BCA8C9@DM5PR18MB1452.namprd18.prod.outlook.com \
--to=kostap@marvell.com \
--cc=andrew@lunn.ch \
--cc=bpeled@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=jon@solid-run.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stefanc@marvell.com \
/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.