From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
michael.hennerich@analog.com, linux-iio@vger.kernel.org,
Lars-Peter.Clausen@analog.com, dan.carpenter@oracle.com
Subject: Re: [PATCH RESEND V2 3/4] iio: frequency: adf4350: Add support for clock consumer framework
Date: Sun, 09 Jun 2013 19:17:48 +0100 [thread overview]
Message-ID: <51B4C6CC.7070904@kernel.org> (raw)
In-Reply-To: <51B2F24F.8080605@kernel.org>
On 06/08/2013 09:58 AM, Jonathan Cameron wrote:
> On 06/06/2013 03:41 PM, Lars-Peter Clausen wrote:
>> On 06/05/2013 10:18 PM, Jonathan Cameron wrote:
>>> On 06/05/2013 07:07 PM, Lars-Peter Clausen wrote:
>>>> On 06/05/2013 07:43 PM, Jonathan Cameron wrote:
>>>>> On 06/05/2013 06:34 PM, Lars-Peter Clausen wrote:
>>>>>> On 06/05/2013 05:25 PM, Jonathan Cameron wrote:
>>>>>>> On 05/06/13 15:25, Lars-Peter Clausen wrote:
>>>>>>>> On 06/05/2013 09:32 AM, Michael Hennerich wrote:
>>>>>>>>> On 06/04/2013 07:44 PM, Jonathan Cameron wrote:
>>>>>>>>>> On 06/03/2013 02:30 PM, michael.hennerich@analog.com wrote:
>>>>>>>>>>> From: Michael Hennerich <michael.hennerich@analog.com>
>>>>>>>>>>>
>>>>>>>>>>> Preferably get clkin (PLL reference clock) from clock framework
>>>>>>>>>>>
>>>>>>>>>>> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
>>>>>>>>>> ERROR: "clk_round_rate" [drivers/iio/frequency/adf4350.ko] undefined!
>>>>>>>>>> make[1]: *** [__modpost] Error 1
>>>>>>>>>>
>>>>>>>>>> on my arm test build. Sorry, I was being lazy before and hadn't done
>>>>>>>>>> any test builds till I tried merging it. Backed out the merge of this
>>>>>>>>>> patch for now.
>>>>>>>>>>
>>>>>>>>>> clk.h does say that api is optional for machine classes. No idea what you
>>>>>>>>>> want to
>>>>>>>>>> do about this.
>>>>>>>>>
>>>>>>>>> The CLK API is optional in the driver - so I prefer to keep it like that and
>>>>>>>>> don't make
>>>>>>>>> the driver depend on COMMON_CLK.
>>>>>>>>>
>>>>>>>>> The simplest and probably the best workaround is to guard the CLK Round/Set
>>>>>>>>> code with
>>>>>>>>> #if defined(CONFIG_COMMON_CLK).
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>
>>>>>>>> This is not a bug in the driver. If the clk API is not implemented it is
>>>>>>>> stubbed out. It looks as if Jonathan is testing on a platform which
>>>>>>>> implements the clk API but not clk_round_rate() (None of the other clk_*
>>>>>>>> symbols are undefined).
>>>>>>>>
>>>>>>>> Jonathan on which platform are you testing this?
>>>>>>> arm specifically pxa27x eabi
>>>>>>>>
>>>>>>
>>>>>> No clk_round_rate() in arch/arm/mach-pxa/clock.c
>>>>> Hmm.. Indeed. So what does one do if one wants to use those functions?
>>>>
>>>> I think the pxa implementation of the clk API is just broken in this regard.
>>>> The clk API requires you to implement all the functions declared in
>>>> include/linux/clk.h
>>> Not according to the header it doesn't.
>>>
>>> /*
>>> * The remaining APIs are optional for machine class support.
>>> */
>>>
>>> Just above clk_round_rate
>>>
>>> Odd situation admittedly but the header certainly implies that these do
>>> not 'need' to be implemented.
>>
>> It should at least be stubbed out, otherwise this doesn't make too much sense.
>>
>> - Lars
>>
> So as not to step on any toes I've raised the issue on lkml and the arm kernel
> list.
>
> My personal feeling is that architectures should just implement a stub returning
> an error code to indicate it isn't available but we will see what
> others think.
>
A fix is on its way for my test platform so given that everyone acknowledges that
these functions are no longer optional, I've applied this patch to the togreg
branch of iio.git. Sorry for the delay. Will be interesting to see if there
any other subarchs that are missing this.
Jonathan
> Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-06-09 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 13:30 [PATCH RESEND V2 1/4] iio: frequency: ad4350: Fix bug / typo in mask michael.hennerich
2013-06-03 13:30 ` [PATCH RESEND V2 2/4] iio: frequency: adf4350: cast value to unsigned to make code checkers happy michael.hennerich
2013-06-04 18:03 ` Jonathan Cameron
2013-06-03 13:30 ` [PATCH RESEND V2 3/4] iio: frequency: adf4350: Add support for clock consumer framework michael.hennerich
2013-06-04 17:44 ` Jonathan Cameron
2013-06-05 7:32 ` Michael Hennerich
2013-06-05 14:25 ` Lars-Peter Clausen
2013-06-05 15:25 ` Jonathan Cameron
2013-06-05 17:34 ` Lars-Peter Clausen
2013-06-05 17:43 ` Jonathan Cameron
2013-06-05 18:07 ` Lars-Peter Clausen
2013-06-05 20:18 ` Jonathan Cameron
2013-06-06 14:41 ` Lars-Peter Clausen
2013-06-08 8:58 ` Jonathan Cameron
2013-06-09 18:17 ` Jonathan Cameron [this message]
2013-06-03 13:30 ` [PATCH RESEND V2 4/4] iio: frequency: adf4350: Add support for dt bindings michael.hennerich
2013-06-09 18:16 ` Jonathan Cameron
2013-06-04 13:57 ` [PATCH RESEND V2 1/4] iio: frequency: ad4350: Fix bug / typo in mask Lars-Peter Clausen
2013-06-04 17:36 ` Jonathan Cameron
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=51B4C6CC.7070904@kernel.org \
--to=jic23@kernel.org \
--cc=Lars-Peter.Clausen@analog.com \
--cc=dan.carpenter@oracle.com \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.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 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).