From: Frank Li <Frank.li@nxp.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/6] dt-bindings: PCI: dwc: Add 'msg' register region
Date: Mon, 5 Feb 2024 12:43:49 -0500 [thread overview]
Message-ID: <ZcEeVc1y/V7jPay2@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <eg7wrjp5ebz43g37fvebr44nwkoh4rptbtyu76nalbmgbbnqke@4zugpgwesyqd>
On Sat, Feb 03, 2024 at 01:44:31AM +0300, Serge Semin wrote:
> On Fri, Feb 02, 2024 at 10:11:27AM -0500, Frank Li wrote:
> > Add an outbound iATU-capable memory-region which will be used to send PCIe
> > message (such as PME_Turn_Off) to peripheral. So all platforms can use
> > common method to send out PME_Turn_Off message by using one outbound iATU.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> > index 022055edbf9e6..25a5420a9ce1e 100644
> > --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> > +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> > @@ -101,6 +101,10 @@ properties:
>
> > Outbound iATU-capable memory-region which will be used to access
> > the peripheral PCIe devices configuration space.
> > const: config
> > + - description:
> > + Outbound iATU-capable memory-region which will be used to send
> > + PCIe message (such as PME_Turn_Off) to peripheral.
> > + const: msg
>
> Note there is a good chance Rob won't like this change. AFAIR he
> already expressed a concern regarding having the "config" reg-name
> describing a memory space within the outbound iATU memory which is
> normally defined by the "ranges" property. Adding a new reg-entry with
> similar semantics I guess won't receive warm welcome.
>
> -Serge(y)
Okay, Anyone from device-tree give comments about this?
@rob, krzysztof kozlowski
Frank
>
>
> > - description:
> > Vendor-specific CSR names. Consider using the generic names above
> > for new bindings.
> >
> > --
> > 2.34.1
> >
> >
next prev parent reply other threads:[~2024-02-05 17:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:11 [PATCH v3 0/6] PCI: dwc: Add common pme_turn_off message by using outbound iATU Frank Li
2024-02-02 15:11 ` [PATCH v3 1/6] PCI: Add INTx Mechanism Messages macros Frank Li
2024-02-02 15:11 ` [PATCH v3 2/6] PCI: dwc: Consolidate args of dw_pcie_prog_outbound_atu() into a structure Frank Li
2024-02-02 15:11 ` [PATCH v3 3/6] PCI: dwc: Add outbound MSG TLPs support Frank Li
2024-02-02 15:11 ` [PATCH v3 4/6] PCI: Add PCIE_MSG_CODE_PME_TURN_OFF message macro Frank Li
2024-02-02 15:11 ` [PATCH v3 5/6] dt-bindings: PCI: dwc: Add 'msg' register region Frank Li
2024-02-02 22:44 ` Serge Semin
2024-02-05 17:43 ` Frank Li [this message]
2024-02-05 18:30 ` Rob Herring
2024-02-05 19:13 ` Frank Li
2024-02-06 22:47 ` Frank Li
2024-02-07 12:37 ` Serge Semin
2024-02-07 16:02 ` Frank Li
2024-02-09 9:52 ` Serge Semin
2024-02-12 22:24 ` Frank Li
2024-02-13 21:54 ` Frank Li
2024-02-14 6:14 ` Manivannan Sadhasivam
2024-02-14 19:54 ` Frank Li
2024-02-28 16:03 ` Rob Herring
2024-02-28 16:23 ` Frank Li
2024-02-29 0:39 ` Rob Herring
2024-02-29 11:26 ` Serge Semin
2024-02-29 15:44 ` Frank Li
2024-03-01 11:35 ` Serge Semin
2024-03-01 16:08 ` Rob Herring
2024-03-04 18:48 ` Serge Semin
2024-03-07 22:28 ` Frank Li
2024-02-02 15:11 ` [PATCH v3 6/6] PCI: dwc: Add common send PME_Turn_Off message method Frank Li
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=ZcEeVc1y/V7jPay2@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@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