From: Damien Le Moal <dlemoal@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Jingoo Han" <jingoohan1@gmail.com>,
linux-pci@vger.kernel.org,
"Rick Wertenbroek" <rick.wertenbroek@gmail.com>,
"Niklas Cassel" <cassel@kernel.org>
Subject: Re: [PATCH v2] PCI: endpoint: Improve pci_epc_ops::align_addr() interface
Date: Thu, 17 Oct 2024 09:37:16 +0900 [thread overview]
Message-ID: <3d586e07-ac13-42cb-988b-eb24a48491f6@kernel.org> (raw)
In-Reply-To: <20241016165930.djlddcgx7uhrpowd@thinkpad>
On 10/17/24 01:59, Manivannan Sadhasivam wrote:
> On Tue, Oct 15, 2024 at 06:07:12PM +0900, Damien Le Moal wrote:
>> The PCI endpoint controller operation interface for the align_addr()
>> operation uses the phys_addr_t type for the PCI address argument and
>> return a value using this type. This is not ideal as PCI addresses are
>> bus addresses, not regular memory physical addresses. Replace the use of
>> phys_addr_t for this operation with the generic u64 type. To be
>> consistent with this change the Designware driver implementation of this
>> operation (function dw_pcie_ep_align_addr()) as well as the type of PCI
>> address fields of struct pci_epc_map are also changed.
>>
>> Fixes: e98c99e2ccad ("PCI: endpoint: Introduce pci_epc_mem_map()/unmap()")
>> Fixes: cb6b7158fdf5 ("PCI: dwc: endpoint: Implement the pci_epc_ops::align_addr() operation")
>> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
>
> I thought of applying it, but then decided to squash it with the offending
> patches.
Fine with me. Thanks !
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-10-17 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:07 [PATCH v2] PCI: endpoint: Improve pci_epc_ops::align_addr() interface Damien Le Moal
2024-10-15 9:20 ` Niklas Cassel
2024-10-16 16:30 ` Manivannan Sadhasivam
2024-10-16 16:59 ` Manivannan Sadhasivam
2024-10-17 0:37 ` Damien Le Moal [this message]
2024-10-17 0:46 ` Damien Le Moal
2024-11-02 11:09 ` Krzysztof Wilczyński
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=3d586e07-ac13-42cb-988b-eb24a48491f6@kernel.org \
--to=dlemoal@kernel.org \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=corbet@lwn.net \
--cc=jingoohan1@gmail.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rick.wertenbroek@gmail.com \
--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