From: Alexander Kochetkov <al.kochet@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-clk@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
linux-rockchip@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Heiko Stuebner <heiko@sntech.de>,
Elaine Zhang <zhangqing@rock-chips.com>
Subject: Re: [PATCH 1/2] clk: rename clk_core_get_boundaries() to clk_hw_get_boundaries() and expose
Date: Fri, 29 Dec 2017 11:52:38 +0300 [thread overview]
Message-ID: <C7AA677C-664F-4305-B74D-B13F3FF0A199@gmail.com> (raw)
In-Reply-To: <20171229001417.GC7997@codeaurora.org>
> 29 дек. 2017 г., в 3:14, Stephen Boyd <sboyd@codeaurora.org> написал(а):
>
> I'm asking if the rate is capped on the consumer side with
> clk_set_max_rate() or if it's capped on the clk provider side to
> express a hardware constraint.
I do that using clk_set_max_rate() at provider size inside clk-rk3188.c.
>
> Sounds like there are some things to be figured out here still. I
> can take a closer look next week. Maybe Heiko will respond before
> then.
I will be very grateful for the ideas. I can continue to work on this next
week too.
Happy New Year and Merry Christmas!
Regards,
Alexander.
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kochetkov <al.kochet@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-clk@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
linux-rockchip@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Heiko Stuebner <heiko@sntech.de>,
Elaine Zhang <zhangqing@rock-chips.com>
Subject: Re: [PATCH 1/2] clk: rename clk_core_get_boundaries() to clk_hw_get_boundaries() and expose
Date: Fri, 29 Dec 2017 11:52:38 +0300 [thread overview]
Message-ID: <C7AA677C-664F-4305-B74D-B13F3FF0A199@gmail.com> (raw)
In-Reply-To: <20171229001417.GC7997@codeaurora.org>
> 29 =D0=B4=D0=B5=D0=BA. 2017 =D0=B3., =D0=B2 3:14, Stephen Boyd =
<sboyd@codeaurora.org> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):=
>=20
> I'm asking if the rate is capped on the consumer side with
> clk_set_max_rate() or if it's capped on the clk provider side to
> express a hardware constraint.
I do that using clk_set_max_rate() at provider size inside clk-rk3188.c.
>=20
> Sounds like there are some things to be figured out here still. I
> can take a closer look next week. Maybe Heiko will respond before
> then.
I will be very grateful for the ideas. I can continue to work on this =
next
week too.
Happy New Year and Merry Christmas!
Regards,
Alexander.
WARNING: multiple messages have this Message-ID (diff)
From: al.kochet@gmail.com (Alexander Kochetkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: rename clk_core_get_boundaries() to clk_hw_get_boundaries() and expose
Date: Fri, 29 Dec 2017 11:52:38 +0300 [thread overview]
Message-ID: <C7AA677C-664F-4305-B74D-B13F3FF0A199@gmail.com> (raw)
In-Reply-To: <20171229001417.GC7997@codeaurora.org>
> 29 ???. 2017 ?., ? 3:14, Stephen Boyd <sboyd@codeaurora.org> ???????(?):
>
> I'm asking if the rate is capped on the consumer side with
> clk_set_max_rate() or if it's capped on the clk provider side to
> express a hardware constraint.
I do that using clk_set_max_rate() at provider size inside clk-rk3188.c.
>
> Sounds like there are some things to be figured out here still. I
> can take a closer look next week. Maybe Heiko will respond before
> then.
I will be very grateful for the ideas. I can continue to work on this next
week too.
Happy New Year and Merry Christmas!
Regards,
Alexander.
next prev parent reply other threads:[~2017-12-29 8:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 16:04 [PATCH 0/2] Fix clock rate in the rockchip_fractional_approximation() Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
2017-12-21 16:04 ` [PATCH 1/2] clk: rename clk_core_get_boundaries() to clk_hw_get_boundaries() and expose Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
2017-12-21 20:07 ` Stephen Boyd
2017-12-21 20:07 ` Stephen Boyd
2017-12-25 9:38 ` Alexander Kochetkov
2017-12-25 9:38 ` Alexander Kochetkov
2017-12-25 9:38 ` Alexander Kochetkov
2017-12-27 1:06 ` Stephen Boyd
2017-12-27 1:06 ` Stephen Boyd
2017-12-28 12:41 ` Alexander Kochetkov
2017-12-28 12:41 ` Alexander Kochetkov
2017-12-28 12:41 ` Alexander Kochetkov
2017-12-29 0:14 ` Stephen Boyd
2017-12-29 0:14 ` Stephen Boyd
2017-12-29 8:52 ` Alexander Kochetkov [this message]
2017-12-29 8:52 ` Alexander Kochetkov
2017-12-29 8:52 ` Alexander Kochetkov
2017-12-21 16:04 ` [PATCH 2/2] clk: rockchip: limit clock rate in the rockchip_fractional_approximation() Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
2017-12-21 16:04 ` Alexander Kochetkov
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=C7AA677C-664F-4305-B74D-B13F3FF0A199@gmail.com \
--to=al.kochet@gmail.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=zhangqing@rock-chips.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.