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: Tue, 14 Jun 2016 10:37:21 +0200	[thread overview]
Message-ID: <1465893441.29321.7.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5A2SRPi=-_WJY87GYoY7vQ+e0vyQcNK8FL4fqxuOaHRqg@mail.gmail.com>

Hi Fabio,

Am Dienstag, den 14.06.2016, 00:18 -0300 schrieb Fabio Estevam:
> Hi Lucas,
> 
> On Mon, Jun 13, 2016 at 7:41 AM, Lucas Stach <l.stach@pengutronix.de> wrote:
> 
> > 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
> 
> Could you please point me to this series?
> 
Here you go:

https://patchwork.kernel.org/patch/8599181/
https://patchwork.kernel.org/patch/8599251/
https://patchwork.kernel.org/patch/8599241/

Regards,
Lucas


      reply	other threads:[~2016-06-14  8:37 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
2016-06-14  3:18       ` Fabio Estevam
2016-06-14  8:37         ` Lucas Stach [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=1465893441.29321.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).