From: Niklas Cassel <cassel@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
imx@lists.linux.dev, dlemoal@kernel.org, maz@kernel.org,
tglx@linutronix.de, jdmason@kudzu.us
Subject: Re: [PATCH v7 3/6] PCI: endpoint: Add pci_epf_align_addr() helper for address alignment
Date: Fri, 15 Nov 2024 18:35:39 +0100 [thread overview]
Message-ID: <ZzeGa-aWlv6bV3fv@ryzen> (raw)
In-Reply-To: <Zzd6Kp1mliKGW2m0@lizhi-Precision-Tower-5810>
On Fri, Nov 15, 2024 at 11:43:22AM -0500, Frank Li wrote:
> On Fri, Nov 15, 2024 at 10:53:07AM +0100, Niklas Cassel wrote:
> > On Thu, Nov 14, 2024 at 05:52:39PM -0500, Frank Li wrote:
> > > +static inline int pci_epf_align_addr_lo_hi(struct pci_epf *epf, enum pci_barno bar,
> > > + u32 low, u32 high, u64 *base, size_t *off)
> > > +{
> > > + u64 addr = high;
> > > +
> > > + addr <<= 32;
> > > + addr |= low;
> > > +
> > > + return pci_epf_align_addr(epf, bar, addr, base, off);
> > > +}
> >
> > I'm not sure if this function deserves to live :)
> > Can't the caller just do this before calling pci_epf_align_addr() ?
>
> Ideally, kernel should have macro to combine 32bit macro to a 64bit, but
> I have not found it.
>
> It is quite easy to make error or warning by simple
> (high << 32 | low)
>
> It needs ((u64) high << 32 | low) at least. I just want to avoid everyone
> to struggle simple issue.
>
> And msi_msg use lo and hi. pci_function_test actually just demostrate how
> to use doorbell. if other function driver use doorbell in future, avoid
> "(u64) high << 32 | low" copy to everywhere.
Keeping the helper is fine with me, but it probably should be renamed
to include _ib_ or _inbound_ in the function name, similar to the comment
for pci_epf_align_addr().
Kind regards,
Niklas
next prev parent reply other threads:[~2024-11-15 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 22:52 [PATCH v7 0/6] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Frank Li
2024-11-14 22:52 ` [PATCH v7 1/6] PCI: endpoint: Add pci_epc_get_fn() API for customizable filtering Frank Li
2024-11-14 22:52 ` [PATCH v7 2/6] PCI: endpoint: Add RC-to-EP doorbell support using platform MSI controller Frank Li
2024-11-14 22:52 ` [PATCH v7 3/6] PCI: endpoint: Add pci_epf_align_addr() helper for address alignment Frank Li
2024-11-15 9:53 ` Niklas Cassel
2024-11-15 16:43 ` Frank Li
2024-11-15 17:35 ` Niklas Cassel [this message]
2024-11-15 10:07 ` Niklas Cassel
2024-11-14 22:52 ` [PATCH v7 4/6] PCI: endpoint: pci-epf-test: Add doorbell test support Frank Li
2024-11-14 22:52 ` [PATCH v7 5/6] misc: pci_endpoint_test: Add doorbell test case Frank Li
2024-11-14 22:52 ` [PATCH v7 6/6] tools: PCI: Add 'B' option for test doorbell Frank Li
2024-11-15 9:43 ` [PATCH v7 0/6] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Niklas Cassel
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=ZzeGa-aWlv6bV3fv@ryzen \
--to=cassel@kernel.org \
--cc=Frank.li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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