From: Magnus Damm <magnus.damm@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
geert+renesas@glider.be, daniel.lezcano@linaro.org,
linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
tglx@linutronix.de
Subject: [PATCH 7/7] clocksource/drivers/sh_cmt: Document "cmt-48" as deprecated
Date: Thu, 18 Jul 2019 20:45:38 +0900 [thread overview]
Message-ID: <156345033835.5307.9206628986166423962.sendpatchset@octo> (raw)
In-Reply-To: <156345023791.5307.6113391102648394591.sendpatchset@octo>
From: Magnus Damm <damm+renesas@opensource.se>
Update the CMT driver to mark "renesas,cmt-48" as deprecated.
Instead of documenting a theoretical hardware device based on current software
support level, define DT bindings top-down based on available data sheet
information and make use of part numbers in the DT compat string.
In case of the only in-tree users r8a7740 and sh73a0 the compat strings
"renesas,r8a7740-cmt1" and "renesas,sh73a0-cmt1" may be used instead.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
drivers/clocksource/sh_cmt.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--- 0011/drivers/clocksource/sh_cmt.c
+++ work/drivers/clocksource/sh_cmt.c 2019-07-18 19:31:01.917491800 +0900
@@ -921,7 +921,11 @@ static const struct platform_device_id s
MODULE_DEVICE_TABLE(platform, sh_cmt_id_table);
static const struct of_device_id sh_cmt_of_table[] __maybe_unused = {
- { .compatible = "renesas,cmt-48", .data = &sh_cmt_info[SH_CMT_48BIT] },
+ {
+ /* deprecated, preserved for backward compatibility */
+ .compatible = "renesas,cmt-48",
+ .data = &sh_cmt_info[SH_CMT_48BIT]
+ },
{
/* deprecated, preserved for backward compatibility */
.compatible = "renesas,cmt-48-gen2",
next prev parent reply other threads:[~2019-07-18 11:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:43 [PATCH 0/7] renesas, cmt: DT Binding Documentation and Minor Driver Updates Magnus Damm
2019-07-18 11:44 ` [PATCH 1/7] dt-bindings: timer: renesas, cmt: Add CMT0234 to sh73a0 and r8a7740 Magnus Damm
2019-07-24 11:12 ` Simon Horman
2019-07-18 11:44 ` [PATCH 2/7] dt-bindings: timer: renesas, cmt: Update CMT1 on " Magnus Damm
2019-07-24 11:12 ` Simon Horman
2019-07-18 11:44 ` [PATCH 3/7] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a7792 Magnus Damm
2019-07-24 11:13 ` Simon Horman
2019-07-18 11:44 ` [PATCH 4/7] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a77995 Magnus Damm
2019-07-24 11:13 ` Simon Horman
2019-07-18 11:45 ` [PATCH 5/7] dt-bindings: timer: renesas, cmt: Update R-Car Gen3 CMT1 usage Magnus Damm
2019-07-24 11:13 ` Simon Horman
2019-07-18 11:45 ` [PATCH 6/7] clocksource/drivers/sh_cmt: r8a7740 and sh73a0 SoC-specific match Magnus Damm
2019-07-24 11:12 ` Simon Horman
2019-08-20 12:34 ` Magnus Damm
2019-08-20 15:22 ` Simon Horman
2019-07-18 11:45 ` Magnus Damm [this message]
2019-07-24 11:13 ` [PATCH 7/7] clocksource/drivers/sh_cmt: Document "cmt-48" as deprecated Simon Horman
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=156345033835.5307.9206628986166423962.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).