From: Stephen Boyd <sboyd@kernel.org>
To: Naman Trivedi Manojbhai <naman.trivedimanojbhai@amd.com>,
abel.vesa@linaro.org, angelogioacchino.delregno@collabora.com,
krzysztof.kozlowski@linaro.org, michal.simek@amd.com,
mturquette@baylibre.com, robh@kernel.org
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Naman Trivedi Manojbhai <naman.trivedimanojbhai@amd.com>
Subject: Re: [PATCH] drivers: clk: zynqmp: remove clock name dependency
Date: Wed, 03 Jan 2024 17:00:06 -0800 [thread overview]
Message-ID: <55fd522918aa41f386e01432248933da.sboyd@kernel.org> (raw)
In-Reply-To: <20240103072017.1646007-1-naman.trivedimanojbhai@amd.com>
Quoting Naman Trivedi Manojbhai (2024-01-02 23:20:17)
> Currently, from zynqmp_get_parent_list() function the clock driver
> references the clock by name instead of its reference from device tree.
> This causes problem when the clock name in the device tree is changed.
>
> Remove hard dependency of clock name and update the logic to use clock
> reference from device tree instead of clock name.
Please use struct clk_parent_data instead.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-04 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 7:20 [PATCH] drivers: clk: zynqmp: remove clock name dependency Naman Trivedi Manojbhai
2024-01-03 10:03 ` Michal Simek
2024-01-03 22:28 ` kernel test robot
2024-01-04 1:00 ` Stephen Boyd [this message]
2024-01-09 11:24 ` Trivedi Manojbhai, Naman
2024-01-29 16:48 ` Trivedi Manojbhai, Naman
2024-01-22 12:05 ` Trivedi Manojbhai, Naman
2024-03-07 6:06 ` Trivedi Manojbhai, Naman
2024-03-27 5:47 ` Trivedi Manojbhai, Naman
2024-01-04 1:41 ` kernel test robot
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=55fd522918aa41f386e01432248933da.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=naman.trivedimanojbhai@amd.com \
--cc=robh@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).