LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
To: <robh+dt@kernel.org>, <mturquette@baylibre.com>, <sboyd@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-clk@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
<nicolas.ferre@microchip.com>, <Eugen.Hristev@microchip.com>,
<Kavyasree.Kotagiri@microchip.com>, <Manohar.Puri@microchip.com>
Subject: [PATCH v10 1/3] dt-bindings: clock: lan966x: Add binding includes for lan966x SoC clock IDs
Date: Wed, 3 Nov 2021 11:49:33 +0530 [thread overview]
Message-ID: <20211103061935.25677-2-kavyasree.kotagiri@microchip.com> (raw)
In-Reply-To: <20211103061935.25677-1-kavyasree.kotagiri@microchip.com>
LAN966X supports 14 clock outputs for its peripherals.
This include file is introduced to use identifiers for clocks.
Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
---
v9 -> v10:
- No changes.
v8 -> v9:
- Added Acked-by: Nicolas Ferre.
v7 -> v8:
- No changes.
v6 -> v7:
- No changes.
v5 -> v6:
- Added Acked-by.
v4 -> v5:
- No changes.
v3 -> v4:
- No changes.
v2 -> v3:
- No changes.
v1 -> v2:
- Updated license.
include/dt-bindings/clock/microchip,lan966x.h | 28 +++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 include/dt-bindings/clock/microchip,lan966x.h
diff --git a/include/dt-bindings/clock/microchip,lan966x.h b/include/dt-bindings/clock/microchip,lan966x.h
new file mode 100644
index 000000000000..fe36ed6d8b5f
--- /dev/null
+++ b/include/dt-bindings/clock/microchip,lan966x.h
@@ -0,0 +1,28 @@
+/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
+/*
+ * Copyright (c) 2021 Microchip Inc.
+ *
+ * Author: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
+ */
+
+#ifndef _DT_BINDINGS_CLK_LAN966X_H
+#define _DT_BINDINGS_CLK_LAN966X_H
+
+#define GCK_ID_QSPI0 0
+#define GCK_ID_QSPI1 1
+#define GCK_ID_QSPI2 2
+#define GCK_ID_SDMMC0 3
+#define GCK_ID_PI 4
+#define GCK_ID_MCAN0 5
+#define GCK_ID_MCAN1 6
+#define GCK_ID_FLEXCOM0 7
+#define GCK_ID_FLEXCOM1 8
+#define GCK_ID_FLEXCOM2 9
+#define GCK_ID_FLEXCOM3 10
+#define GCK_ID_FLEXCOM4 11
+#define GCK_ID_TIMER 12
+#define GCK_ID_USB_REFCLK 13
+
+#define N_CLOCKS 14
+
+#endif
--
2.17.1
next prev parent reply other threads:[~2021-11-03 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 6:19 [PATCH v10 0/3] Add driver for lan966x Generic Clock Controller Kavyasree Kotagiri
2021-11-03 6:19 ` Kavyasree Kotagiri [this message]
2021-11-03 6:19 ` [PATCH v10 2/3] dt-bindings: clock: lan966x: Add LAN966X " Kavyasree Kotagiri
2021-11-03 6:19 ` [PATCH v10 3/3] clk: lan966x: Add lan966x SoC clock driver Kavyasree Kotagiri
2021-11-08 5:12 ` [PATCH v10 0/3] Add driver for lan966x Generic Clock Controller Kavyasree.Kotagiri
2021-11-26 5:09 ` Kavyasree.Kotagiri
2021-12-08 10:10 ` Nicolas Ferre
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=20211103061935.25677-2-kavyasree.kotagiri@microchip.com \
--to=kavyasree.kotagiri@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--subject='Re: [PATCH v10 1/3] dt-bindings: clock: lan966x: Add binding includes for lan966x SoC clock IDs' \
/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
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).