All of lore.kernel.org
 help / color / mirror / Atom feed
From: JeffyChen <jeffy.chen@rock-chips.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, bhelgaas@google.com,
	linux-pm@vger.kernel.org, tony@atomide.com,
	shawn.lin@rock-chips.com, briannorris@chromium.org,
	dianders@chromium.org, devicetree@vger.kernel.org,
	linux-pci@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [RFC PATCH v12 1/5] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq
Date: Wed, 27 Dec 2017 09:36:37 +0800	[thread overview]
Message-ID: <5A42F925.5090806@rock-chips.com> (raw)
In-Reply-To: <3268448.IvXk7OJtIY@aspire.rjw.lan>

Hi Rafael and Rob,

Thanks for your reply.

On 12/27/2017 08:43 AM, Rafael J. Wysocki wrote:
> On Wednesday, December 27, 2017 12:35:52 AM CET Rob Herring wrote:
>> >On Tue, Dec 26, 2017 at 10:36:42AM +0800, Jeffy Chen wrote:
>>> > >We are going to handle PCIe WAKE# pin for PCI devices in the pci core,
>>> > >so add definitions of the optional PCIe WAKE# pin for PCI devices.
>>> > >
>>> > >Also add an definition of the optional PCI interrupt pin for PCI
>>> > >devices to distinguish it from the PCIe WAKE# pin.
>> >
>> >By v13 you should drop "RFC". RFC implies not ready for merging.
> Which very much still is the case AFAICS.
>
maybe i should split this series, and send dt-binding patch and the pci 
irq parsing patch along without RFC ?

> Thanks,
> Rafael
>
>
>
>

  reply	other threads:[~2017-12-27  1:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26  2:36 [RFC PATCH v12 0/5] PCI: rockchip: Move PCIe WAKE# handling into pci core Jeffy Chen
2017-12-26  2:36 ` Jeffy Chen
2017-12-26  2:36 ` Jeffy Chen
2017-12-26  2:36 ` Jeffy Chen
2017-12-26  2:36 ` [RFC PATCH v12 1/5] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq Jeffy Chen
2017-12-26 23:35   ` Rob Herring
2017-12-27  0:43     ` Rafael J. Wysocki
2017-12-27  0:43       ` Rafael J. Wysocki
2017-12-27  1:36       ` JeffyChen [this message]
     [not found] ` <20171226023646.17722-1-jeffy.chen-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-12-26  2:36   ` [RFC PATCH v12 2/5] of/irq: Adjust of_pci_irq parsing for multiple interrupts Jeffy Chen
2017-12-26  2:36     ` Jeffy Chen
2017-12-26 15:48     ` Rob Herring
2017-12-27  1:03       ` JeffyChen
2017-12-26  2:36 ` [RFC PATCH v12 3/5] mwifiex: Disable wakeup irq handling for pcie Jeffy Chen
2017-12-26  2:36 ` [RFC PATCH v12 4/5] PCI / PM: Add support for the PCIe WAKE# signal for OF Jeffy Chen
2017-12-26  2:36   ` Jeffy Chen
2017-12-26 23:56   ` Rob Herring
2017-12-26 23:56     ` Rob Herring
2017-12-27  1:32     ` JeffyChen
2017-12-27  1:32       ` JeffyChen
2017-12-27 15:30       ` Rob Herring
2017-12-27 15:30         ` Rob Herring
2017-12-28  0:32         ` Rafael J. Wysocki
2017-12-28  0:32           ` Rafael J. Wysocki
2017-12-28  8:47         ` Andy Shevchenko
2017-12-28  8:47           ` Andy Shevchenko
2017-12-26  2:36 ` [RFC PATCH v12 5/5] arm64: dts: rockchip: Move PCIe WAKE# irq to pcie port for Gru Jeffy Chen
2017-12-26  2:36   ` Jeffy Chen
     [not found]   ` <20171226023646.17722-6-jeffy.chen-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-12-29 17:55     ` Tony Lindgren
2017-12-29 17:55       ` Tony Lindgren
2017-12-29 17:55       ` Tony Lindgren
2017-12-30  0:10       ` Rafael J. Wysocki
2017-12-30  0:10         ` Rafael J. Wysocki
2017-12-27  0:44 ` [RFC PATCH v12 0/5] PCI: rockchip: Move PCIe WAKE# handling into pci core Rafael J. Wysocki
2017-12-27  0:44   ` Rafael J. Wysocki
2017-12-27  0:44   ` Rafael J. Wysocki
2017-12-27  0:44   ` Rafael J. Wysocki
2017-12-27  0:44   ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2017-12-26  2:08 Jeffy Chen
2017-12-26  2:08 ` [RFC PATCH v12 1/5] dt-bindings: PCI: Add definition of PCIe WAKE# irq and PCI irq Jeffy Chen
2017-12-29 17:57   ` Tony Lindgren
2017-12-29 23:50     ` Rafael J. Wysocki
2017-12-30  0:31       ` Rafael J. Wysocki
2018-01-03 19:54         ` Tony Lindgren
2018-01-03 19:53       ` Tony Lindgren

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=5A42F925.5090806@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=bhelgaas@google.com \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=tony@atomide.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.