From: dongas86@gmail.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/2] soc/imx: Add GPCv2 power gating driver
Date: Thu, 30 Mar 2017 15:04:51 +0800 [thread overview]
Message-ID: <20170330070451.GA29432@b29396-OptiPlex-7040> (raw)
In-Reply-To: <20170330065836.GD19596@b29396-OptiPlex-7040>
On Thu, Mar 30, 2017 at 02:58:36PM +0800, Dong Aisheng wrote:
> On Mon, Mar 27, 2017 at 11:42:15AM -0700, Andrey Smirnov wrote:
> > On Thu, Mar 23, 2017 at 11:24 PM, Dong Aisheng <dongas86@gmail.com> wrote:
> > > On Tue, Mar 21, 2017 at 07:50:04AM -0700, Andrey Smirnov wrote:
> > >> Add code allowing for control of various power domains managed by GPCv2
> > >> IP block found in i.MX7 series of SoCs. Power domains covered by this
> > >> patch are:
> > >>
> > >> - PCIE PHY
> > >> - MIPI PHY
> > >> - USB HSIC PHY
> > >> - USB OTG1/2 PHY
> > >>
> > >
> > > You probably may need drop USB OTG which is not claimed in current RM.
> > > See the PGC definition in 5.5.10 GPC Memory Map section.
> > >
> > > Each PGC (CPU type, MIX type, PU type) will occupy 64 Bytes address space,
> > > the specific base address of each PGC are listed as below.
> > > ? 0x800 ~ 0x83F : PGC for A7 core0
> > > ? 0x840 ~ 0x87F: PGC for A7 core1
> > > ? 0x880 ~ 0x8BF: PGC for A7 SCU
> > > ? 0xA00 ~ 0xA3F: PGC for fastmix/megamix
> > > ? 0xC00 ~ 0xC3F: PGC for MIPI PHY
> > > ? 0xC40 ~ 0xC7F: PGC for PCIE_PHY
> > > ? 0xC80 ~ 0xCBF: Reserved
> > > ? 0xCC0 ~ 0xCFF: Reserved
> > > ? 0xD00 ~ 0xD3F: PGC for USB HSIC PHY
> > >
> > > And in 5.4 Power Management Unit (PMU) chapter,
> > > you will find the USB OTG phy power is directly supplied by
> > > VDD_USB_OTG1_3P3_IN/VDD_USB_OTG2_3P3_IN.
> > >
> > > http://www.nxp.com/assets/documents/data/en/reference-manuals/IMX7DRM.pdf
> > >
> > > I understand that there's also some USB OTG code exist in NXP internal
> > > tree, but that's legacy for early doc implementation and may be deprecated.
> > > so i assume it should be gone.
> > >
> > > Hopefully i will double confirm with our IC designer tomorrow.
> > >
> >
> > USB OTG domains are absent from that list, true, but they are
> > mentioned all of the place further in that section in register map
> > documentation, which makes it difficult to tell which part of the
> > datasheet is not up to date.
> >
> > I'm going to drop those power domains for now, since I don't have a
> > use-case for them and it would also allow me to get rid of the chunk
> > of code you thought was messy. However it would be nice to get an
> > updated version of RM where all of that is straightened out.
> >
>
> I checked with our IC designer and he confirmed the USB OTG is removed
> and not supported in GPC. SW should not control it, instead, its power
> domain is handled by hardware automatically.
>
> Currently there's true some incorrectness in GPC chapter, i already
> reported the issue to the designer, but still no timeline when i
> can get a updated version.
>
> But i think it's fine if you're going to only support PCIE/MIPI/USB HSIC
> PHY power domain. I suppose those bits are correct in RM.
>
BTW, would you please CC my company email next time?
aisheng.dong at nxp.com
Then i can see them in time to help the review.
Regards
Dong Aisheng
prev parent reply other threads:[~2017-03-30 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 14:50 [PATCH v7 0/2] GPCv2 power gating driver Andrey Smirnov
2017-03-21 14:50 ` [PATCH v7 1/2] dt-bindings: Add " Andrey Smirnov
2017-03-24 6:32 ` Dong Aisheng
2017-03-27 18:42 ` Andrey Smirnov
2017-03-30 7:15 ` Dong Aisheng
2017-03-21 14:50 ` [PATCH v7 2/2] soc/imx: " Andrey Smirnov
2017-03-24 6:24 ` Dong Aisheng
2017-03-23 14:35 ` Lucas Stach
2017-03-30 7:51 ` Dong Aisheng
2017-03-29 16:08 ` Lucas Stach
2017-04-01 4:10 ` Dong Aisheng
2017-03-31 12:28 ` Lucas Stach
2017-04-11 3:22 ` Dong Aisheng
2017-03-27 18:42 ` Andrey Smirnov
2017-03-30 6:58 ` Dong Aisheng
2017-03-30 7:04 ` Dong Aisheng [this message]
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=20170330070451.GA29432@b29396-OptiPlex-7040 \
--to=dongas86@gmail.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