From: "Pali Rohár" <pali@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: P2020: Add law_trgt_if property to PCIe DT nodes
Date: Thu, 5 May 2022 17:47:15 +0200 [thread overview]
Message-ID: <20220505154715.xujvyjvewsj6jcw7@pali> (raw)
In-Reply-To: <CAL_JsqLKjd3zPssbTo=mBfoa6nV144k9TamStk-jO3QbunmSAw@mail.gmail.com>
On Thursday 05 May 2022 10:40:09 Rob Herring wrote:
> On Wed, May 4, 2022 at 1:09 PM Pali Rohár <pali@kernel.org> wrote:
> >
> > DT law_trgt_if property defines Local Access Window Target Interface.
>
> Documentation?
I was not able to find it :-( So the only documentation for me was the
source code and decoding how it works and how it is used.
> fsl,law-trgt-if would be the preferred form.
>
> > Local Access Window Target Interface is used for identifying individual
> > peripheral and mapping its memory to CPU. Interface id is defined by
> > hardware itself.
>
> Normally, we avoid instance indices like this, but if it is more than
> just documentation convention maybe that's fine.
>
> Rob
It is id defined by HW. Software needs to know how to pair DT node with
address range defined in "ranges" to the correct HW PCIe controller.
next prev parent reply other threads:[~2022-05-05 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 18:08 [PATCH] powerpc/85xx: P2020: Add law_trgt_if property to PCIe DT nodes Pali Rohár
2022-05-05 15:40 ` Rob Herring
2022-05-05 15:47 ` Pali Rohár [this message]
2022-07-29 13:02 ` Michael Ellerman
2022-07-29 13:46 ` Rob Herring
2022-08-01 3:38 ` Michael Ellerman
2022-08-01 7:55 ` Pali Rohár
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=20220505154715.xujvyjvewsj6jcw7@pali \
--to=pali@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox