linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Christoph Fritz <chf.fritz@googlemail.com>,
	Richard Zhu <hongxing.zhu@nxp.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Shawn Guo <shawnguo@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH] PCI: imx6: Add support for MX6SX LDO PCIE domain regulator
Date: Mon, 13 Jun 2016 12:41:37 +0200	[thread overview]
Message-ID: <1465814497.2313.7.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5Bix1Bgrsbn2K_1sh7ee=dxRccU1zk2fJei-WU4vvpCgg@mail.gmail.com>

Hi Fabio,

Am Sonntag, den 12.06.2016, 10:51 -0300 schrieb Fabio Estevam:
> Hi Christoph,
> 
> On Wed, Jun 8, 2016 at 6:35 AM, Christoph Fritz
> <chf.fritz@googlemail.com> wrote:
> 
> > There was a discussion doing the handling of the regulator inside the PM
> > backend:
> 
> Thanks for pointing me to this discussion.
> 
> >
> >> On Mon, 2016-02-15 at 07:24 +0000, Richard Zhu wrote:
> >> > As Lucas discussed with me before,  the GPC regulator operations should[n't] be touched in
> >> > Imx pcie driver at all.  These bits operations should be encapsulate into the PM system,
> >> >  for example, the regulator driver.
> >
> > On Thu, 2016-02-18 at 12:59 +0100, Christoph Fritz wrote:
> >> Ok, for an initial version, I'll just leave the regulator in my
> >> devicetree enabled. For further enhancements I suppose
> >> arch/arm/mach-imx/gpc.c needs to get touched?
> >>
> > @Richard and @Lucas: Any further hints on this?
> 
> Yes, would appreciate some hints or examples as to how to properly
> handle the PCI LDO regulator on mx6sx.
> 
It should be handled the same way as the PU domain regulator on mx6q.
This means the regulator is a supply of the PCIe PHY power domain and
should be en-/disabled through the GPC driver.

I already posted a series to rework the GPC driver to allow adding new
power domains easily, but it was rejected by Shawn on formal grounds, as
it's mostly a single big patch to do the rework. I don't have time to
split this up further at the moment, as this is really non-trivial, but
maybe Shawn is willing to take it if someone does a proper review of the
patch.

With this series applied it should be easy to add the required power
domains and regulator handling for mx6sx.

Regards,
Lucas


  reply	other threads:[~2016-06-13 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08  0:07 [PATCH] PCI: imx6: Add support for MX6SX LDO PCIE domain regulator Fabio Estevam
2016-06-08  9:35 ` Christoph Fritz
2016-06-12 13:51   ` Fabio Estevam
2016-06-13 10:41     ` Lucas Stach [this message]
2016-06-14  3:18       ` Fabio Estevam
2016-06-14  8:37         ` Lucas Stach

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=1465814497.2313.7.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=bhelgaas@google.com \
    --cc=chf.fritz@googlemail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).