From: <dan.j.williams@intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>, <linux-coco@lists.linux.dev>,
<linux-pci@vger.kernel.org>, <dan.j.williams@intel.com>
Cc: <yilun.xu@intel.com>, <yilun.xu@linux.intel.com>,
<baolu.lu@linux.intel.com>, <zhenzhong.duan@intel.com>,
<aneesh.kumar@kernel.org>, <bhelgaas@google.com>, <aik@amd.com>,
<linux-kernel@vger.kernel.org>, <amerilainen@nvidia.com>,
<ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v2] PCI/IDE: Add Address Association Register setup for downstream MMIO
Date: Fri, 10 Oct 2025 12:35:47 -0700 [thread overview]
Message-ID: <68e96013eef19_19928100aa@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20251006034538.2240772-1-yilun.xu@linux.intel.com>
Xu Yilun wrote:
> Add Address Association Register setup for downstream MMIO
>
> The address ranges for RP side Address Association Registers should
> cover memory addresses for all PFs/VFs/downstream devices of the DSM
> device. A simple solution is to get the aggregated memory range and
> prefetchable-memory range from directly connected downstream port
> (either an RP or a switch port) and set into 2 Address Association
> Register blocks.
>
> Just like RID association, address associations will be set by default
> if hardware sets 'Number of Address Association Register Blocks' in the
> 'Selective IDE Stream Capability Register' to a non-zero value.
> Alternatively, TSM drivers can opt-out of the settings by zero'ing out
> the probed region.
>
> If the directly connected downstream port provides both memory range
> and prefetchable-memory range but the platform only provides 1 Address
> Association Register block then setup the former first. This follows the
> PCI bridge specification precedent where memory is mandatory and
> prefetchable-memory is optional. Priortize the mandatory one. If the
> platform can't fit into the default setup, TSM drivers can always change
> the setting before setup. E.g. zero'ing out the memory range so that
> prefetchable-memory range could be setup.
>
> The Address Association Register setup for Endpoint Side is still
> uncertain so isn't supported in this patch.
This looks good Yilun. I will append it to the end of the v7 posting of
the PCI/TSM base series.
I will likely split the resource_assigned() introduction to its own
patch with a Link: to the rationale provided by Ilpo, and perform some
other small fixups. Like I notice I defined the rid registers as rid_X
and the address association registers as assocX, so I'll drop the "_".
prev parent reply other threads:[~2025-10-10 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 3:45 [PATCH v2] PCI/IDE: Add Address Association Register setup for downstream MMIO Xu Yilun
2025-10-10 19:35 ` dan.j.williams [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=68e96013eef19_19928100aa@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=aik@amd.com \
--cc=amerilainen@nvidia.com \
--cc=aneesh.kumar@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.com \
--cc=zhenzhong.duan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox