From: Nicolas Boichat <drinkcat@chromium.org>
To: Yongqiang Niu <yongqiang.niu@mediatek.com>
Cc: CK Hu <ck.hu@mediatek.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Devicetree List <devicetree@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
lkml <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Daniel Vetter <daniel@ffwll.ch>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3, 1/8] soc: mediatek: mmsys: create mmsys folder
Date: Thu, 31 Dec 2020 09:21:45 +0800 [thread overview]
Message-ID: <CANMq1KCRBz-rY6y3nHp8yh_QSohkmaYS=DqNDSPzvwmq-a09DQ@mail.gmail.com> (raw)
In-Reply-To: <1609144630-14721-2-git-send-email-yongqiang.niu@mediatek.com>
On Mon, Dec 28, 2020 at 4:38 PM Yongqiang Niu
<yongqiang.niu@mediatek.com> wrote:
>
> the mmsys will more and more complicated after support
> more and more SoCs, add an independent folder will be
> more clear
>
> Signed-off-by: Yongqiang Niu <yongqiang.niu@mediatek.com>
> ---
> drivers/soc/mediatek/Makefile | 2 +-
> drivers/soc/mediatek/mmsys/Makefile | 2 +
> drivers/soc/mediatek/mmsys/mtk-mmsys.c | 380 +++++++++++++++++++++++++++++++++
> drivers/soc/mediatek/mtk-mmsys.c | 380 ---------------------------------
I wonder why this doesn't get detected as a rename?
> 4 files changed, 383 insertions(+), 381 deletions(-)
> create mode 100644 drivers/soc/mediatek/mmsys/Makefile
> create mode 100644 drivers/soc/mediatek/mmsys/mtk-mmsys.c
> delete mode 100644 drivers/soc/mediatek/mtk-mmsys.c
>
> diff --git a/drivers/soc/mediatek/Makefile b/drivers/soc/mediatek/Makefile
> index 01f9f87..b5987ca 100644
> --- a/drivers/soc/mediatek/Makefile
> +++ b/drivers/soc/mediatek/Makefile
> @@ -3,4 +3,4 @@ obj-$(CONFIG_MTK_CMDQ) += mtk-cmdq-helper.o
> obj-$(CONFIG_MTK_INFRACFG) += mtk-infracfg.o
> obj-$(CONFIG_MTK_PMIC_WRAP) += mtk-pmic-wrap.o
> obj-$(CONFIG_MTK_SCPSYS) += mtk-scpsys.o
> -obj-$(CONFIG_MTK_MMSYS) += mtk-mmsys.o
> +obj-$(CONFIG_MTK_MMSYS) += mmsys/
> diff --git a/drivers/soc/mediatek/mmsys/Makefile b/drivers/soc/mediatek/mmsys/Makefile
> new file mode 100644
> index 0000000..5d976d7
> --- /dev/null
> +++ b/drivers/soc/mediatek/mmsys/Makefile
> @@ -0,0 +1,2 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +obj-$(CONFIG_MTK_MMSYS) += mtk-mmsys.o
> \ No newline at end of file
Nit: newline at end of file please.
next prev parent reply other threads:[~2020-12-31 1:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 8:37 soc: mediatek: Prepare MMSYS for DDP routing using function call Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 1/8] soc: mediatek: mmsys: create mmsys folder Yongqiang Niu
2020-12-31 1:21 ` Nicolas Boichat [this message]
2021-01-04 3:08 ` Yongqiang Niu
2021-01-04 5:57 ` Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 2/8] soc: mediatek: mmsys: Use function call for setting the routing registers Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 3/8] soc: mediatek: mmsys: add mt8183 " Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 4/8] soc: mediatek: mmsys: add component OVL_2L2 Yongqiang Niu
2020-12-29 15:23 ` Chun-Kuang Hu
2021-03-22 15:05 ` Chun-Kuang Hu
2020-12-28 8:37 ` [PATCH v3, 5/8] soc: mediatek: mmsys: add component POSTMASK Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 6/8] soc: mediatek: mmsys: add component RDMA4 Yongqiang Niu
2020-12-29 15:24 ` Chun-Kuang Hu
2020-12-28 8:37 ` [PATCH v3, 7/8] soc: mediatek: mmsys: Use function call for setting mmsys ovl mout register Yongqiang Niu
2020-12-28 16:38 ` Chun-Kuang Hu
2020-12-29 0:52 ` Yongqiang Niu
2020-12-29 1:34 ` Yongqiang Niu
2020-12-28 8:37 ` [PATCH v3, 8/8] soc: mediatek: mmsys: add mt8192 mmsys support Yongqiang Niu
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='CANMq1KCRBz-rY6y3nHp8yh_QSohkmaYS=DqNDSPzvwmq-a09DQ@mail.gmail.com' \
--to=drinkcat@chromium.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=yongqiang.niu@mediatek.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;
as well as URLs for NNTP newsgroup(s).