From: Abel Vesa <abel.vesa@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/3] soc: imx: Refactor BLK CTRL driver
Date: Fri, 21 Jan 2022 13:22:35 +0200 [thread overview]
Message-ID: <20220121112238.47281-1-abel.vesa@nxp.com> (raw)
This splits the SoC specific parts into separate drivers for i.MX8MM and
i.MX8MN. Should be more readable and easier to maintain.
As for the i.MX8MP BLK CTRL driver (sent by Lucas here:
https://lore.kernel.org/linux-arm-kernel/20220119134027.2931945-7-l.stach@pengutronix.de/raw)
It can remain as a separate driver until we figure out what is the
overlap and how can we make it use the generic part.
This patchset doesn't rely on the above-mentioned patch and does not
impact it in any way.
Abel Vesa (3):
soc: imx: make i.MX8MM BLK CTRL a separate driver
soc: imx: make i.MX8MN BLK CTRL a separate driver
soc: imx: Rename generic BLK CTRL driver to suggest future usability
drivers/soc/imx/Kconfig | 14 +
drivers/soc/imx/Makefile | 4 +-
drivers/soc/imx/imx-blk-ctrl.c | 322 ++++++++++++++++
drivers/soc/imx/imx-blk-ctrl.h | 72 ++++
drivers/soc/imx/imx8m-blk-ctrl.c | 617 ------------------------------
drivers/soc/imx/imx8mm-blk-ctrl.c | 173 +++++++++
drivers/soc/imx/imx8mn-blk-ctrl.c | 101 +++++
7 files changed, 685 insertions(+), 618 deletions(-)
create mode 100644 drivers/soc/imx/imx-blk-ctrl.c
create mode 100644 drivers/soc/imx/imx-blk-ctrl.h
delete mode 100644 drivers/soc/imx/imx8m-blk-ctrl.c
create mode 100644 drivers/soc/imx/imx8mm-blk-ctrl.c
create mode 100644 drivers/soc/imx/imx8mn-blk-ctrl.c
--
2.31.1
next reply other threads:[~2022-01-21 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 11:22 Abel Vesa [this message]
2022-01-21 11:22 ` [RFC 1/3] soc: imx: make i.MX8MM BLK CTRL a separate driver Abel Vesa
2022-01-21 11:22 ` [RFC 2/3] soc: imx: make i.MX8MN " Abel Vesa
2022-01-21 11:22 ` [RFC 3/3] soc: imx: Rename generic BLK CTRL driver to suggest future usability Abel Vesa
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=20220121112238.47281-1-abel.vesa@nxp.com \
--to=abel.vesa@nxp.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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
Powered by JetHome