From: Matthias Brugger <matthias.bgg@gmail.com>
To: Evan Benn <evanbenn@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Stanley Chu <stanley.chu@mediatek.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
linux-arm-kernel@lists.infradead.org,
Stanley Chu <stanley.chu@mediatek.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Fabien Parent <fparent@baylibre.com>,
linux-mediatek@lists.infradead.org,
Alexey Klimov <alexey.klimov@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King <linux@armlinux.org.uk>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/2] drivers/clocksource/mediatek: Split mediatek drivers into 2 files
Date: Mon, 29 Mar 2021 17:33:00 +0200 [thread overview]
Message-ID: <1f4dd7b1-3bb5-51eb-f980-e2ba41f43823@gmail.com> (raw)
In-Reply-To: <20210318160414.1.Ia2a09ce93b47eac45308205820db0938d47604df@changeid>
On 18/03/2021 06:04, Evan Benn wrote:
> mtk_gpt and mtk_syst drivers for mt6577 and mt6765 devices were not
> sharing any code. So split them into separate files.
>
> Signed-off-by: Evan Benn <evanbenn@chromium.org>
> ---
>
> arch/arm/mach-mediatek/Kconfig | 3 +-
> arch/arm64/Kconfig.platforms | 3 +-
> drivers/clocksource/Kconfig | 13 +-
> drivers/clocksource/Makefile | 3 +-
> ...mer-mediatek.c => timer-mediatek-mt6577.c} | 100 -------------
> drivers/clocksource/timer-mediatek-mt6765.c | 135 ++++++++++++++++++
> 6 files changed, 151 insertions(+), 106 deletions(-)
> rename drivers/clocksource/{timer-mediatek.c => timer-mediatek-mt6577.c} (69%)
> create mode 100644 drivers/clocksource/timer-mediatek-mt6765.c
>
[...]
> diff --git a/drivers/clocksource/timer-mediatek-mt6765.c b/drivers/clocksource/timer-mediatek-mt6765.c
> new file mode 100644
> index 000000000000..b4f22f226feb
> --- /dev/null
> +++ b/drivers/clocksource/timer-mediatek-mt6765.c
> @@ -0,0 +1,135 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Mediatek SoCs General-Purpose Timer handling.
> + *
> + * Copyright (C) 2014 Matthias Brugger
> + *
> + * Matthias Brugger <matthias.bgg@gmail.com>
The mt6765 was written by Stanley, I think we should reflcet that. Please see:
e3af677607d9 ("clocksource/drivers/timer-mediatek: Add support for system timer")
Regards,
Matthias
prev parent reply other threads:[~2021-03-29 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 5:04 [PATCH 1/2] drivers/clocksource/mediatek: Split mediatek drivers into 2 files Evan Benn
2021-03-18 5:04 ` [PATCH 2/2] drivers/clocksource/mediatek: Ack and disable interrupts on shutdown Evan Benn
2021-03-18 23:46 ` Evan Benn
2021-03-22 11:19 ` [PATCH 1/2] drivers/clocksource/mediatek: Split mediatek drivers into 2 files Daniel Lezcano
2021-03-24 0:53 ` Evan Benn
2021-03-29 15:33 ` Matthias Brugger [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=1f4dd7b1-3bb5-51eb-f980-e2ba41f43823@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=alexey.klimov@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=evanbenn@chromium.org \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=stanley.chu@mediatek.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yingjoe.chen@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).