All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, knaerzche@gmail.com,
	mturquette@baylibre.com,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH clk-fixes v1 2/2] clk: composite: Use rate_ops.determine_rate when also a mux is available
Date: Mon, 18 Oct 2021 13:01:11 -0700	[thread overview]
Message-ID: <163458727129.1767887.7945772309296747310@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20211016105022.303413-3-martin.blumenstingl@googlemail.com>

Quoting Martin Blumenstingl (2021-10-16 03:50:22)
> Update clk_composite_determine_rate() to use rate_ops.determine_rate
> when available in combination with a mux. So far clk_divider_ops provide
> both, .round_rate and .determine_rate. Removing the former would make
> clk-composite fail silently for example on Rockchip platforms (which
> heavily use composite clocks).
> Add support for using rate_ops.determine_rate when either
> rate_ops.round_rate is not available or both (.round_rate and
> .determine_rate) are provided.
> 
> Suggested-by: Alex Bee <knaerzche@gmail.com>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---

Applied to clk-next

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, knaerzche@gmail.com,
	mturquette@baylibre.com,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH clk-fixes v1 2/2] clk: composite: Use rate_ops.determine_rate when also a mux is available
Date: Mon, 18 Oct 2021 13:01:11 -0700	[thread overview]
Message-ID: <163458727129.1767887.7945772309296747310@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20211016105022.303413-3-martin.blumenstingl@googlemail.com>

Quoting Martin Blumenstingl (2021-10-16 03:50:22)
> Update clk_composite_determine_rate() to use rate_ops.determine_rate
> when available in combination with a mux. So far clk_divider_ops provide
> both, .round_rate and .determine_rate. Removing the former would make
> clk-composite fail silently for example on Rockchip platforms (which
> heavily use composite clocks).
> Add support for using rate_ops.determine_rate when either
> rate_ops.round_rate is not available or both (.round_rate and
> .determine_rate) are provided.
> 
> Suggested-by: Alex Bee <knaerzche@gmail.com>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---

Applied to clk-next

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-18 20:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 10:50 [PATCH clk-fixes v1 0/2] Fix clk-composite to support .determine_rate Martin Blumenstingl
2021-10-16 10:50 ` Martin Blumenstingl
2021-10-16 10:50 ` [PATCH clk-fixes v1 1/2] clk: composite: Also consider .determine_rate for rate + mux composites Martin Blumenstingl
2021-10-16 10:50   ` Martin Blumenstingl
2021-10-18 20:01   ` Stephen Boyd
2021-10-18 20:01     ` Stephen Boyd
2021-10-27 22:47     ` Alex Bee
2021-10-27 22:47       ` Alex Bee
2021-10-29  6:43       ` Stephen Boyd
2021-10-29  6:43         ` Stephen Boyd
2021-10-16 10:50 ` [PATCH clk-fixes v1 2/2] clk: composite: Use rate_ops.determine_rate when also a mux is available Martin Blumenstingl
2021-10-16 10:50   ` Martin Blumenstingl
2021-10-18 20:01   ` Stephen Boyd [this message]
2021-10-18 20:01     ` Stephen Boyd
2021-10-16 11:50 ` [PATCH clk-fixes v1 0/2] Fix clk-composite to support .determine_rate Alex Bee
2021-10-16 11:50   ` Alex Bee
2021-10-17 16:15   ` Chen-Yu Tsai
2021-10-17 16:15     ` Chen-Yu Tsai

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=163458727129.1767887.7945772309296747310@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=knaerzche@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=mturquette@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.