devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-clk@vger.kernel.org, eugen.hristev@microchip.com,
	robh+dt@kernel.org, sboyd@kernel.org,
	nicolas.ferre@microchip.com, mturquette@baylibre.com,
	kavyasree.kotagiri@microchip.com, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] dt-bindings: clock: lan966x: Extend includes with clock gates
Date: Tue, 26 Oct 2021 22:09:05 -0500	[thread overview]
Message-ID: <YXjC0SXHpS0WJUnl@robh.at.kernel.org> (raw)
In-Reply-To: <20211019084449.1411060-3-horatiu.vultur@microchip.com>

On Tue, 19 Oct 2021 10:44:48 +0200, Horatiu Vultur wrote:
> On lan966x it is allow to control the clock to some peripherals like
> USB. So extend the include file with these clocks.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  include/dt-bindings/clock/microchip,lan966x.h | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-10-27  3:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  8:44 [RFC PATCH 0/3] Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-19  8:44 ` [RFC PATCH 1/3] dt-bindings: clock: lan966x: Extend for clock gate support Horatiu Vultur
2021-10-27  3:08   ` Rob Herring
2021-10-29 12:06     ` Horatiu Vultur
2021-10-19  8:44 ` [RFC PATCH 2/3] dt-bindings: clock: lan966x: Extend includes with clock gates Horatiu Vultur
2021-10-27  3:09   ` Rob Herring [this message]
2021-10-19  8:44 ` [RFC PATCH 3/3] clk: lan966x: Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-29  6:41   ` Stephen Boyd
2021-10-29  9:35     ` Horatiu Vultur
2021-10-29 23:32       ` Stephen Boyd
2021-10-31  9:03         ` 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=YXjC0SXHpS0WJUnl@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eugen.hristev@microchip.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --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 \
    /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).