All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw
Date: Mon, 26 Oct 2020 09:11:42 -0700	[thread overview]
Message-ID: <7hk0vdhsqp.fsf@baylibre.com> (raw)
In-Reply-To: <20201021162147.563655-1-jbrunet@baylibre.com>

Jerome Brunet <jbrunet@baylibre.com> writes:

> This patchset a call in CCF to get "struct clk*" from "struct clk_hw*"
>
> Changes since v1: [0]
> * Add a con_id string to help keep track of the consumer
> * Add devm variant:
>  - Following our discussion on V1, I choose to have the dev as
>    argument as most devm function do. However, as Stephen pointed out
>    we don't expect this to differ from the one linked to clk_hw. In
>    this case a warning is thrown.
> * Add a first usage of this in the amlogic clock driver.

Tested-by: Kevin Hilman <khilman@baylibre.com>

Tested this on a couple g12a based platforms.  This series also allows
me to build the g12 clock drivers as modules.

Kevin

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

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw
Date: Mon, 26 Oct 2020 09:11:42 -0700	[thread overview]
Message-ID: <7hk0vdhsqp.fsf@baylibre.com> (raw)
In-Reply-To: <20201021162147.563655-1-jbrunet@baylibre.com>

Jerome Brunet <jbrunet@baylibre.com> writes:

> This patchset a call in CCF to get "struct clk*" from "struct clk_hw*"
>
> Changes since v1: [0]
> * Add a con_id string to help keep track of the consumer
> * Add devm variant:
>  - Following our discussion on V1, I choose to have the dev as
>    argument as most devm function do. However, as Stephen pointed out
>    we don't expect this to differ from the one linked to clk_hw. In
>    this case a warning is thrown.
> * Add a first usage of this in the amlogic clock driver.

Tested-by: Kevin Hilman <khilman@baylibre.com>

Tested this on a couple g12a based platforms.  This series also allows
me to build the g12 clock drivers as modules.

Kevin

  parent reply	other threads:[~2020-10-26 16:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 16:21 [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw Jerome Brunet
2020-10-21 16:21 ` Jerome Brunet
2020-10-21 16:21 ` [PATCH v2 1/3] clk: avoid devm_clk_release name clash Jerome Brunet
2020-10-21 16:21   ` Jerome Brunet
2020-11-14 20:54   ` Stephen Boyd
2020-11-14 20:54     ` Stephen Boyd
2020-10-21 16:21 ` [PATCH v2 2/3] clk: add api to get clk consumer from clk_hw Jerome Brunet
2020-10-21 16:21   ` Jerome Brunet
2020-11-14 20:54   ` Stephen Boyd
2020-11-14 20:54     ` Stephen Boyd
2020-10-21 16:21 ` [PATCH v2 3/3] clk: meson: g12: drop use of __clk_lookup() Jerome Brunet
2020-10-21 16:21   ` Jerome Brunet
2020-11-14 20:54   ` Stephen Boyd
2020-11-14 20:54     ` Stephen Boyd
2020-10-26 16:11 ` Kevin Hilman [this message]
2020-10-26 16:11   ` [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw Kevin Hilman

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=7hk0vdhsqp.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.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 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.