linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC] implement gpio_pci_platform_pm to put pci device into D3cold
Date: Mon, 13 Jun 2016 18:11:22 +0100	[thread overview]
Message-ID: <20160613171122.GA29837@red-moon> (raw)
In-Reply-To: <20160612203245.66fbd54a@xhacker>

Hi Jisheng,

On Sun, Jun 12, 2016 at 08:32:45PM +0800, Jisheng Zhang wrote:
> Dear all,
> 
> I want to solve one problem: we have pcie in a DT based arm64 system,
> now we want to put the device into D3cold when runtime suspended. The
> pcie device could be power down by operating one gpio pin, this is the
> D3cold the platform could support. 
> 
> My solution is to register a gpio_pci_platform_pm with
> pci_set_platform_pm() but the key is how to setup a mapping between
> pci_dev and gpio through DT
> 
> I think this is a general case, could you please kindly give some
> suggestions?

You would like to define an "equivalent" of what exists today
in ACPI (ie ACPI methods like _PSx) through generic DT bindings,
correct ?

It is hard to say what can be really generalized and how without
having first an implementation (so that we can see how this would
map to other systems), if you have some code to share even if it
is an RFC that would help quite a bit.

Question: when you say "I think this is a general case" I wonder,
are you referring to specific drivers in the mainline ?

Thanks,
Lorenzo

      reply	other threads:[~2016-06-13 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-12 12:32 [RFC] implement gpio_pci_platform_pm to put pci device into D3cold Jisheng Zhang
2016-06-13 17:11 ` Lorenzo Pieralisi [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=20160613171122.GA29837@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=helgaas@kernel.org \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=will.deacon@arm.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 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).