From: Helge Deller <deller@gmx.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v1 1/1] parisc: Add ioread64_lo_hi() and iowrite64_lo_hi()
Date: Mon, 7 Feb 2022 16:34:39 +0100 [thread overview]
Message-ID: <d0074e49-35c9-99a6-436f-0fdffb0314d8@gmx.de> (raw)
In-Reply-To: <20220207151639.75086-1-andriy.shevchenko@linux.intel.com>
On 2/7/22 16:16, Andy Shevchenko wrote:
> It's a followup to the previous commit f15309d7ad5d ("parisc: Add
> ioread64_hi_lo() and iowrite64_hi_lo()") which does only half of
> the job. Add the rest, so we won't get a new kernel test robot
> reports.
>
> Fixes: f15309d7ad5d ("parisc: Add ioread64_hi_lo() and iowrite64_hi_lo()")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
applied to the parisc for-next tree.
Thanks!
Helge
> ---
> arch/parisc/lib/iomap.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/parisc/lib/iomap.c b/arch/parisc/lib/iomap.c
> index 367f6397bda7..860385058085 100644
> --- a/arch/parisc/lib/iomap.c
> +++ b/arch/parisc/lib/iomap.c
> @@ -346,6 +346,16 @@ u64 ioread64be(const void __iomem *addr)
> return *((u64 *)addr);
> }
>
> +u64 ioread64_lo_hi(const void __iomem *addr)
> +{
> + u32 low, high;
> +
> + low = ioread32(addr);
> + high = ioread32(addr + sizeof(u32));
> +
> + return low + ((u64)high << 32);
> +}
> +
> u64 ioread64_hi_lo(const void __iomem *addr)
> {
> u32 low, high;
> @@ -419,6 +429,12 @@ void iowrite64be(u64 datum, void __iomem *addr)
> }
> }
>
> +void iowrite64_lo_hi(u64 val, void __iomem *addr)
> +{
> + iowrite32(val, addr);
> + iowrite32(val >> 32, addr + sizeof(u32));
> +}
> +
> void iowrite64_hi_lo(u64 val, void __iomem *addr)
> {
> iowrite32(val >> 32, addr + sizeof(u32));
> @@ -530,6 +546,7 @@ EXPORT_SYMBOL(ioread32);
> EXPORT_SYMBOL(ioread32be);
> EXPORT_SYMBOL(ioread64);
> EXPORT_SYMBOL(ioread64be);
> +EXPORT_SYMBOL(ioread64_lo_hi);
> EXPORT_SYMBOL(ioread64_hi_lo);
> EXPORT_SYMBOL(iowrite8);
> EXPORT_SYMBOL(iowrite16);
> @@ -538,6 +555,7 @@ EXPORT_SYMBOL(iowrite32);
> EXPORT_SYMBOL(iowrite32be);
> EXPORT_SYMBOL(iowrite64);
> EXPORT_SYMBOL(iowrite64be);
> +EXPORT_SYMBOL(iowrite64_lo_hi);
> EXPORT_SYMBOL(iowrite64_hi_lo);
> EXPORT_SYMBOL(ioread8_rep);
> EXPORT_SYMBOL(ioread16_rep);
>
prev parent reply other threads:[~2022-02-07 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 15:16 Andy Shevchenko
2022-02-07 15:34 ` Helge Deller [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=d0074e49-35c9-99a6-436f-0fdffb0314d8@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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
all inboxes | Powered by JetHome®