From: Jerome Brunet <jbrunet@baylibre.com>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: narmstrong@baylibre.com, sboyd@kernel.org, khilman@baylibre.com,
Alexandre Mergnat <amergnat@baylibre.com>,
linux-kernel@vger.kernel.org, baylibre-upstreaming@groups.io,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] clk: meson: gxbb-aoclk: migrate to the new parent description method
Date: Thu, 25 Jul 2019 16:41:15 +0200 [thread overview]
Message-ID: <1ja7d2xjlg.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20190722095053.14104-3-amergnat@baylibre.com>
On Mon 22 Jul 2019 at 11:50, Alexandre Mergnat <amergnat@baylibre.com> wrote:
> @@ -208,8 +216,10 @@ static struct clk_regmap ao_cts_cec = {
> * Until CCF gets fixed, adding this fake parent that won't
> * ever be registered should work around the problem
> */
> - .parent_names = (const char *[]){ "fixme",
> - "ao_cts_rtc_oscin" },
> + .parent_data = (const struct clk_parent_data []) {
> + { .fw_name = "fixme", },
Hum, that would work I suppose but I'd prefer if used .name for this
work around. Remember to throw an '.index = -1' as well
> + { .hw = &ao_cts_rtc_oscin.hw },
> + },
> .num_parents = 2,
> .flags = CLK_SET_RATE_PARENT,
> },
_______________________________________________
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:[~2019-07-25 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 9:50 [PATCH 0/4] clk: meson: ao: use the new parent description method Alexandre Mergnat
2019-07-22 9:50 ` [PATCH 1/4] clk: meson: g12a-aoclk: migrate to " Alexandre Mergnat
2019-07-22 9:50 ` [PATCH 2/4] clk: meson: gxbb-aoclk: " Alexandre Mergnat
2019-07-25 14:41 ` Jerome Brunet [this message]
2019-07-22 9:50 ` [PATCH 3/4] clk: meson: axg-aoclk: " Alexandre Mergnat
2019-07-22 9:50 ` [PATCH 4/4] clk: meson: remove ao input bypass clocks Alexandre Mergnat
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=1ja7d2xjlg.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=amergnat@baylibre.com \
--cc=baylibre-upstreaming@groups.io \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--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).