From: Lucas Stach <l.stach@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: barebox@lists.infradead.org, Peter Mamonov <pmamonov@gmail.com>
Subject: Re: [PATCH v2] MIPS: add virt_to_phys() and phys_to_virt()
Date: Fri, 11 Aug 2017 15:59:27 +0200 [thread overview]
Message-ID: <1502459967.21055.32.camel@pengutronix.de> (raw)
In-Reply-To: <20170811135525.19034-1-linux@rempel-privat.de>
Am Freitag, den 11.08.2017, 15:55 +0200 schrieb Oleksij Rempel:
> From: Antony Pavlov <antonynpavlov@gmail.com>
>
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> Signed-off-by: Peter Mamonov <pmamonov@gmail.com>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> ---
> changes.
> v2:
> - make use of use CPHYSADDR and CKSEG0ADDR
>
> arch/mips/include/asm/io.h | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/arch/mips/include/asm/io.h b/arch/mips/include/asm/io.h
> index 4bee5913a..d4eb623c3 100644
> --- a/arch/mips/include/asm/io.h
> +++ b/arch/mips/include/asm/io.h
> @@ -12,11 +12,46 @@
>
> #include <linux/compiler.h>
> #include <asm/types.h>
> +#include <asm/addrspace.h>
> #include <asm/byteorder.h>
>
> void dma_flush_range(unsigned long, unsigned long);
> void dma_inv_range(unsigned long, unsigned long);
>
> +/*
> + * virt_to_phys - map virtual addresses to physical
> + * @address: address to remap
> + *
> + * The returned physical address is the physical (CPU) mapping for
> + * the memory address given. It is only valid to use this function on
> + * addresses directly mapped or allocated via kmalloc.
The last sentence in this...
> + * This function does not give bus mappings for DMA transfers. In
> + * almost all conceivable cases a device driver should not be using
> + * this function
> + */
> +static inline unsigned long virt_to_phys(const void *address)
> +{
> + return (unsigned long)CPHYSADDR(address);
> +}
> +
> +/*
> + * phys_to_virt - map physical address to virtual
> + * @address: address to remap
> + *
> + * The returned virtual address is a current CPU mapping for
> + * the memory address given. It is only valid to use this function on
> + * addresses that have a kernel mapping
... and this paragraph have no meaning Barebox at all.
> + * This function does not handle bus mappings for DMA transfers. In
> + * almost all conceivable cases a device driver should not be using
> + * this function
> + */
> +static inline void *phys_to_virt(unsigned long address)
> +{
> + return (void *)CKSEG0ADDR(address);
> +}
> +
> #define IO_SPACE_LIMIT 0
>
> /*****************************************************************************/
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-08-11 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:55 Oleksij Rempel
2017-08-11 13:59 ` Lucas Stach [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=1502459967.21055.32.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.de \
--cc=pmamonov@gmail.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