From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
<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>,
<Eugen.Hristev@microchip.com>, <Manohar.Puri@microchip.com>
Subject: Re: [PATCH v8 1/3] dt-bindings: clock: lan966x: Add binding includes for lan966x SoC clock IDs
Date: Mon, 18 Oct 2021 13:55:20 +0200 [thread overview]
Message-ID: <b236a54b-3291-b361-52e4-fa0ba6d38d0c@microchip.com> (raw)
In-Reply-To: <20211008082635.31774-2-kavyasree.kotagiri@microchip.com>
On 08/10/2021 at 10:26, Kavyasree Kotagiri wrote:
> 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>
If mine is missing:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> 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
>
--
Nicolas Ferre
next prev parent reply other threads:[~2021-10-18 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 8:26 [PATCH v8 0/3] Add driver for lan966x Generic Clock Controller Kavyasree Kotagiri
2021-10-08 8:26 ` [PATCH v8 1/3] dt-bindings: clock: lan966x: Add binding includes for lan966x SoC clock IDs Kavyasree Kotagiri
2021-10-18 11:55 ` Nicolas Ferre [this message]
2021-10-08 8:26 ` [PATCH v8 2/3] dt-bindings: clock: lan966x: Add LAN966X Clock Controller Kavyasree Kotagiri
2021-10-18 11:55 ` Nicolas Ferre
2021-10-08 8:26 ` [PATCH v8 3/3] clk: lan966x: Add lan966x SoC clock driver Kavyasree Kotagiri
2021-10-18 20:09 ` Horatiu Vultur
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=b236a54b-3291-b361-52e4-fa0ba6d38d0c@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).