devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <linux-kernel@vger.kernel.org>, <monstr@monstr.eu>,
	<michal.simek@xilinx.com>, <git@xilinx.com>
Cc: Andrew Davis <afd@ti.com>,
	Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Harini Katakam <harini.katakam@amd.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Manikanta Guntupalli <manikanta.guntupalli@amd.com>,
	Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] arm64: zynqmp: Align fixed-clock nodes for kv260
Date: Thu, 30 Nov 2023 10:59:14 +0100	[thread overview]
Message-ID: <cover.1701338352.git.michal.simek@amd.com> (raw)

Hi,

these two patches are moving clock nodes out of bus because they don't have
reg property and also align node names.

Thanks,
Michal


Michal Simek (2):
  arm64: zynqmp: Move fixed clock to / for kv260
  arm64: zynqmp: Fix clock node name in kv260 cards

 .../boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso | 40 +++++++++---------
 .../boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso | 42 +++++++++----------
 2 files changed, 41 insertions(+), 41 deletions(-)

-- 
2.36.1


             reply	other threads:[~2023-11-30  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  9:59 Michal Simek [this message]
2023-11-30  9:59 ` [PATCH 1/2] arm64: zynqmp: Move fixed clock to / for kv260 Michal Simek
2023-11-30  9:59 ` [PATCH 2/2] arm64: zynqmp: Fix clock node name in kv260 cards Michal Simek
2023-12-13 15:46 ` [PATCH 0/2] arm64: zynqmp: Align fixed-clock nodes for kv260 Michal Simek

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=cover.1701338352.git.michal.simek@amd.com \
    --to=michal.simek@amd.com \
    --cc=afd@ti.com \
    --cc=ashok.reddy.soma@xilinx.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=git@xilinx.com \
    --cc=harini.katakam@amd.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manikanta.guntupalli@amd.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=robh+dt@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).