From: Lee Jones <lee@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] mfd: tmio: remove obsolete io accessors
Date: Fri, 9 Feb 2024 07:54:49 +0000 [thread overview]
Message-ID: <20240209075449.GD689448@google.com> (raw)
In-Reply-To: <20240209015817.14627-10-wsa+renesas@sang-engineering.com>
On Fri, 09 Feb 2024, Wolfram Sang wrote:
> Since commit 568494db6809 ("mtd: remove tmio_nand driver") and commit
> aceae7848624 ("fbdev: remove tmiofb driver"), these accessors have no
> users anymore. Remove them.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> include/linux/mfd/tmio.h | 25 -------------------------
> 1 file changed, 25 deletions(-)
Acked-by: Lee Jones <lee@kernel.org>
> diff --git a/include/linux/mfd/tmio.h b/include/linux/mfd/tmio.h
> index bc53323293a3..4223315d2b2a 100644
> --- a/include/linux/mfd/tmio.h
> +++ b/include/linux/mfd/tmio.h
> @@ -10,31 +10,6 @@
> #include <linux/platform_device.h>
> #include <linux/pm_runtime.h>
>
> -#define tmio_ioread8(addr) readb(addr)
> -#define tmio_ioread16(addr) readw(addr)
> -#define tmio_ioread16_rep(r, b, l) readsw(r, b, l)
> -#define tmio_ioread32(addr) \
> - (((u32)readw((addr))) | (((u32)readw((addr) + 2)) << 16))
> -
> -#define tmio_iowrite8(val, addr) writeb((val), (addr))
> -#define tmio_iowrite16(val, addr) writew((val), (addr))
> -#define tmio_iowrite16_rep(r, b, l) writesw(r, b, l)
> -#define tmio_iowrite32(val, addr) \
> - do { \
> - writew((val), (addr)); \
> - writew((val) >> 16, (addr) + 2); \
> - } while (0)
> -
> -#define sd_config_write8(base, shift, reg, val) \
> - tmio_iowrite8((val), (base) + ((reg) << (shift)))
> -#define sd_config_write16(base, shift, reg, val) \
> - tmio_iowrite16((val), (base) + ((reg) << (shift)))
> -#define sd_config_write32(base, shift, reg, val) \
> - do { \
> - tmio_iowrite16((val), (base) + ((reg) << (shift))); \
> - tmio_iowrite16((val) >> 16, (base) + ((reg + 2) << (shift))); \
> - } while (0)
> -
> /* tmio MMC platform flags */
> /*
> * Some controllers can support a 2-byte block size when the bus width
> --
> 2.43.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-02-09 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 1:58 [PATCH 0/6] mfd: tmio: simplify header and move to platform_data Wolfram Sang
2024-02-09 1:58 ` [PATCH 1/6] mfd: tmio: remove obsolete platform_data Wolfram Sang
2024-02-09 7:54 ` Lee Jones
2024-02-09 1:58 ` [PATCH 2/6] mfd: tmio: remove obsolete io accessors Wolfram Sang
2024-02-09 7:54 ` Lee Jones [this message]
2024-02-09 1:58 ` [PATCH 3/6] mmc: tmio/sdhi: fix includes Wolfram Sang
2024-02-09 1:58 ` [PATCH 4/6] mfd: tmio: update include files Wolfram Sang
2024-02-09 7:55 ` Lee Jones
2024-02-09 1:58 ` [PATCH 5/6] mfd: tmio: sanitize comments Wolfram Sang
2024-02-09 7:56 ` Lee Jones
2024-02-09 1:58 ` [PATCH 6/6] mfd: tmio: move header to platform_data Wolfram Sang
2024-02-09 7:56 ` Lee Jones
2024-02-13 20:52 ` John Paul Adrian Glaubitz
2024-02-09 7:58 ` [PATCH 0/6] mfd: tmio: simplify header and move " Lee Jones
2024-02-09 10:02 ` Wolfram Sang
2024-02-09 11:34 ` Ulf Hansson
2024-02-09 13:28 ` Lee Jones
2024-02-12 11:17 ` Ulf Hansson
2024-02-12 12:12 ` Wolfram Sang
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=20240209075449.GD689448@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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