linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [Query] : PCIe - Endpoint Function
Date: Fri, 11 Oct 2019 08:35:07 +0100	[thread overview]
Message-ID: <CA+V-a8tFB=giGvcLNhfTaaQ-R8svXijcoQ_QUdRMX3Hb4Ur95Q@mail.gmail.com> (raw)
In-Reply-To: <b91c3f6e-cef5-c06d-4282-84c24d616533@ti.com>

Hi Kishon,

On Thu, Oct 10, 2019 at 12:32 PM Kishon Vijay Abraham I <kishon@ti.com> wrote:
>
> Hi Prabhakar,
>
> On 10/10/19 4:57 PM, Lad, Prabhakar wrote:
> > Hello,
> >
> > I am currently working on adding pcie-endpoint support for a
> > controller, this controller doesn't support outbound- inbound address
> > translations, it has 1-1 mapping between the CPU and PCI addresses,
> > the current endpoint framework is based on  outbound-inbound
> > translations, what is the best approach to add this support, or is
> > there any WIP already for it ?
>
> How will the endpoint access host buffer without outbound ATU? I assume the PCI
> address reserved for endpoint is not the full 32-bit or 64-bit address space?
> In that case, the endpoint cannot directly access the host buffer (unless the
> host already knows the address space of the endpoint and gives the endpoint an
> address in its OB address space).
>
for the address translation to happen on the endpoint I have to
program the local cpu address prior to start of link,
Yes the host somehow has to know the address space of endpoint and
pass it to the endpoint.

Cheers,
--Prabhakar Lad

  reply	other threads:[~2019-10-11  7:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 11:27 [Query] : PCIe - Endpoint Function Lad, Prabhakar
2019-10-10 11:32 ` Kishon Vijay Abraham I
2019-10-11  7:35   ` Lad, Prabhakar [this message]
2019-10-11 13:37     ` Lad, Prabhakar
2019-10-15  7:52       ` Kishon Vijay Abraham I
2019-10-22  6:06         ` Lad, Prabhakar
2019-10-29 10:24           ` Lad, Prabhakar
2019-10-29 10:53             ` Kishon Vijay Abraham I
2019-10-29 14:55               ` Lad, Prabhakar

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='CA+V-a8tFB=giGvcLNhfTaaQ-R8svXijcoQ_QUdRMX3Hb4Ur95Q@mail.gmail.com' \
    --to=prabhakar.csengg@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-pci@vger.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;
as well as URLs for NNTP newsgroup(s).