mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>, <afd@ti.com>,
	<j-keerthy@ti.com>, <krzysztof.kozlowski+dt@linaro.org>,
	<s-anna@ti.com>, <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<j-choudhary@ti.com>
Subject: [PATCH 0/3] RNG clock property cleanup
Date: Tue, 1 Nov 2022 03:02:34 +0530	[thread overview]
Message-ID: <20221031213237.52275-1-j-choudhary@ti.com> (raw)

This series removes the clock property from the rng node of
K3 devices for TI SoCs as that clock is not dedicated to RNG
module and it cannot be controlled by the rng driver.

DT binding fix:
<https://lore.kernel.org/all/20220901171041.32056-1-afd@ti.com/>

Jayesh Choudhary (3):
  arm64: dts: ti: k3-am65-main: drop RNG clock
  arm64: dts: ti: k3-j721e-main: drop RNG clock
  arm64: dts: ti: k3-am64-main: drop RNG clock

 arch/arm64/boot/dts/ti/k3-am64-main.dtsi  | 1 -
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi  | 1 -
 arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 1 -
 3 files changed, 3 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-10-31 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 21:32 Jayesh Choudhary [this message]
2022-10-31 21:32 ` [PATCH 1/3] arm64: dts: ti: k3-am65-main: drop RNG clock Jayesh Choudhary
2022-11-02 15:17   ` Nishanth Menon
2022-11-02 17:04     ` Andrew Davis
2022-11-02 19:44       ` Nishanth Menon
2022-11-04 18:23         ` Jayesh Choudhary
2022-10-31 21:32 ` [PATCH 2/3] arm64: dts: ti: k3-j721e-main: " Jayesh Choudhary
2022-10-31 21:32 ` [PATCH 3/3] arm64: dts: ti: k3-am64-main: " Jayesh Choudhary

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=20221031213237.52275-1-j-choudhary@ti.com \
    --to=j-choudhary@ti.com \
    --cc=afd@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=vigneshr@ti.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

all inboxes | Powered by JetHome®