All of lore.kernel.org
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] clk: add DT clock binding support
Date: Thu, 14 Jun 2012 23:32:53 -0500	[thread overview]
Message-ID: <4FDABAF5.3090201@gmail.com> (raw)
In-Reply-To: <20120615031747.GG31565@S2101-09.ap.freescale.net>

On 06/14/2012 10:17 PM, Shawn Guo wrote:
> On Tue, Jun 12, 2012 at 09:41:48AM -0500, Rob Herring wrote:
>> +struct clk *of_clk_get_from_provider(struct of_phandle_args *clkspec)
>> +{
>> +	struct of_clk_provider *provider;
>> +	struct clk *clk = NULL;
> 
> Both clk and clkdev treat NULL as a valid clock and return ERR_PTR for
> error case, while all the codes in this patch just return NULL for
> error and check (clk != NULL) for valid clock.

Because Grant hates ERR_PTR... :)

> 
> Should we force the consistent behavior between DT and non-DT on this?

Yes, I agree and will change it.

Rob

> 
>> +
>> +	/* Check if we have such a provider in our array */
>> +	mutex_lock(&of_clk_lock);
>> +	list_for_each_entry(provider, &of_clk_providers, link) {
>> +		if (provider->node == clkspec->np)
>> +			clk = provider->get(clkspec, provider->data);
>> +		if (clk)
>> +			break;
>> +	}
>> +	mutex_unlock(&of_clk_lock);
>> +
>> +	return clk;
>> +}
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>,
	mturquette@linaro.org, sboyd@codeaurora.org,
	skannan@codeaurora.org, s.hauer@pengutronix.de,
	Sascha Hauer <kernel@pengutronix.de>,
	Mike Turquette <mturquette@ti.com>
Subject: Re: [PATCH v3 1/4] clk: add DT clock binding support
Date: Thu, 14 Jun 2012 23:32:53 -0500	[thread overview]
Message-ID: <4FDABAF5.3090201@gmail.com> (raw)
In-Reply-To: <20120615031747.GG31565@S2101-09.ap.freescale.net>

On 06/14/2012 10:17 PM, Shawn Guo wrote:
> On Tue, Jun 12, 2012 at 09:41:48AM -0500, Rob Herring wrote:
>> +struct clk *of_clk_get_from_provider(struct of_phandle_args *clkspec)
>> +{
>> +	struct of_clk_provider *provider;
>> +	struct clk *clk = NULL;
> 
> Both clk and clkdev treat NULL as a valid clock and return ERR_PTR for
> error case, while all the codes in this patch just return NULL for
> error and check (clk != NULL) for valid clock.

Because Grant hates ERR_PTR... :)

> 
> Should we force the consistent behavior between DT and non-DT on this?

Yes, I agree and will change it.

Rob

> 
>> +
>> +	/* Check if we have such a provider in our array */
>> +	mutex_lock(&of_clk_lock);
>> +	list_for_each_entry(provider, &of_clk_providers, link) {
>> +		if (provider->node == clkspec->np)
>> +			clk = provider->get(clkspec, provider->data);
>> +		if (clk)
>> +			break;
>> +	}
>> +	mutex_unlock(&of_clk_lock);
>> +
>> +	return clk;
>> +}
> 

  reply	other threads:[~2012-06-15  4:32 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 14:41 [PATCH v3 0/4] DT clock bindings Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 1/4] clk: add DT clock binding support Rob Herring
2012-06-12 14:41   ` Rob Herring
2012-06-15  3:17   ` Shawn Guo
2012-06-15  3:17     ` Shawn Guo
2012-06-15  3:17     ` Shawn Guo
2012-06-15  4:32     ` Rob Herring [this message]
2012-06-15  4:32       ` Rob Herring
2012-07-01 22:13   ` [PATCH v6] " Rob Herring
2012-07-01 22:13     ` Rob Herring
2012-07-01 22:13     ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 2/4] clk: add DT fixed-clock " Rob Herring
2012-06-12 14:41   ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 3/4] dt: add clock binding doc to primecell bindings Rob Herring
2012-06-12 14:41   ` Rob Herring
2012-06-22 13:55   ` Ben Dooks
2012-06-22 14:23     ` Russell King - ARM Linux
2012-06-12 14:41 ` [PATCH v3 4/4] clk: add highbank clock support Rob Herring
2012-06-12 14:41   ` Rob Herring
2012-06-12 15:47 ` [PATCH v3 0/4] DT clock bindings Mike Turquette
2012-06-12 15:47   ` Mike Turquette
2012-06-12 16:23   ` Rob Herring
2012-06-12 16:23     ` Rob Herring
2012-06-14  8:49     ` Shawn Guo
2012-06-14  8:49       ` Shawn Guo
2012-06-14  8:49       ` Shawn Guo
2012-06-13 15:26 ` Peter De Schrijver
2012-06-13 15:26   ` Peter De Schrijver
2012-06-13 18:09   ` Rob Herring
2012-06-13 18:09     ` Rob Herring
2012-06-15  8:39 ` Shawn Guo
2012-06-15  8:39   ` Shawn Guo
2012-06-15  8:39   ` Shawn Guo
2012-06-15 15:40   ` Stephen Warren
2012-06-15 15:40     ` Stephen Warren
2012-06-15 21:07   ` Rob Herring
2012-06-15 21:07     ` Rob Herring
2012-06-21  7:27 ` Chris Ball
2012-06-21  7:27   ` Chris Ball
2012-06-21  7:30   ` [PATCH 01/02] clk: Refactor of_clk_* into a new clk-of.c Chris Ball
2012-06-21  7:30     ` Chris Ball
2012-06-21  7:32   ` [PATCH 02/02] clk: clk-of: Use alloc_bootmem() instead of kzalloc() Chris Ball
2012-06-21  7:32     ` Chris Ball
2012-06-21 12:18     ` Paul Mundt
2012-06-21 12:18       ` Paul Mundt
2012-06-21 15:00   ` [PATCH v3 0/4] DT clock bindings Rob Herring
2012-06-21 15:00     ` Rob Herring
2012-06-21 17:54     ` Mike Turquette
2012-06-21 17:54       ` Mike Turquette
2012-06-27 12:54       ` Rob Herring
2012-06-27 12:54         ` Rob Herring
2012-07-03  1:30         ` Turquette, Mike
2012-07-03  1:30           ` Turquette, Mike
2012-07-03  2:37           ` Rob Herring
2012-07-03  2:37             ` Rob Herring

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=4FDABAF5.3090201@gmail.com \
    --to=robherring2@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.