From: Rob Herring <robh@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 4/4] dt-bindings: pci: layerscape-pci: define AER/PME interrupts
Date: Mon, 13 Dec 2021 13:18:17 -0600 [thread overview]
Message-ID: <YbececugsiFdOh0H@robh.at.kernel.org> (raw)
In-Reply-To: <20211202004636.5276-5-leoyang.li@nxp.com>
On Wed, 01 Dec 2021 18:46:36 -0600, Li Yang wrote:
> Different platforms using this controller are using different numbers of
> interrupt lines and the routing of events to these interrupt lines are
> different too. So instead of trying to define names for these interrupt
> lines, we define the more specific AER/PME events that are routed to
> these interrupt lines.
>
> For platforms which only has a single interrupt line for miscellaneous
> controller events, we can keep using the original "intr" name for
> backward compatibility.
>
> Also change the example from ls1021a to ls2088a for better representation.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> ---
> .../bindings/pci/layerscape-pci.txt | 40 +++++++++++--------
> 1 file changed, 24 insertions(+), 16 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-12-13 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 0:46 [PATCH v2 0/4] layerscape-pci binding updates Li Yang
2021-12-02 0:46 ` [PATCH v2 1/4] dt-bindings: pci: layerscape-pci: Add a optional property big-endian Li Yang
2021-12-02 0:46 ` [PATCH v2 2/4] dt-bindings: pci: layerscape-pci: Update the description of SCFG property Li Yang
2021-12-02 0:46 ` [PATCH v2 3/4] dt-bindings: pci: layerscape-pci: Add EP mode compatible strings for ls1028a Li Yang
2021-12-02 0:46 ` [PATCH v2 4/4] dt-bindings: pci: layerscape-pci: define AER/PME interrupts Li Yang
2021-12-13 19:18 ` Rob Herring [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=YbececugsiFdOh0H@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@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 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.