From: Josh Wu <josh.wu@atmel.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: <g.liakhovetski@gmx.de>, <m.chehab@samsung.com>,
<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [media] ov2640: add support for async device registration
Date: Wed, 26 Mar 2014 14:20:42 +0800 [thread overview]
Message-ID: <533271BA.5000007@atmel.com> (raw)
In-Reply-To: <532AFED3.5030103@samsung.com>
Hi, Sylwester
On 3/20/2014 10:44 PM, Sylwester Nawrocki wrote:
> Hi Josh,
>
> On 19/03/14 10:17, Josh Wu wrote:
>> On 3/15/2014 5:17 AM, Sylwester Nawrocki wrote:
>>>> On 03/14/2014 11:12 AM, Josh Wu wrote:
>>>>>> + clk = v4l2_clk_get(&client->dev, "mclk");
>>>>>> + if (IS_ERR(clk))
>>>>>> + return -EPROBE_DEFER;
>>>> You should instead make it:
>>>>
>>>> return PTR_ERR(clk);
>>>>
>>>> But you will need this patch for that to work:
>>>> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/clk/clk.c?id=a34cd4666f3da84228a82f70c94b8d9b692034ea
>>>>
>>>>
>>>> With this patch there is no need to overwrite any returned error
>>>> value with EPROBE_DEFER.
>> Thanks for the information. I will use this in v2 version.
> Oops, I missed somehow that it's v4l2_clk_get(), rather than
> clk_get(). So it seems it will not work when you return PTR_ERR(clk),
> since v4l2_clk_get() returns -ENODEV when clock is not found.
right, I missed that. So this version is still valid one. The v2 that I
already sent should be dropped.
> I think we should modify v4l2_clk_get() so it returns EPROBE_DEFER
> rather than ENODEV on error. I anticipate v4l2_clk_get() might be
> using clk_get() internally in future, and the v4l2 clk look up
> will be used as a fallback only. So sensor drivers should just
> do something like:
>
> clk = v4l2_clk_get(...);
> if (IS_ERR(clk))
> return PTR_ERR(clk);
I noticed that there are some driver like ov772x, ov9640 and etc, are
not supported the async probe yet.
If we return the EPROBE_DEFER for all v4l2_clk_get(), that will cause
the no-async probe function work incorrectly.
So IMO we can do your above suggestion after all sensors support async
probe.
Thanks.
>
> --
> Regards,
> Sylwester
Best Regards,
Josh Wu
prev parent reply other threads:[~2014-03-26 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 10:12 [PATCH] [media] ov2640: add support for async device registration Josh Wu
2014-03-14 21:17 ` Sylwester Nawrocki
2014-03-19 9:17 ` Josh Wu
2014-03-20 14:44 ` Sylwester Nawrocki
2014-03-26 6:20 ` Josh Wu [this message]
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=533271BA.5000007@atmel.com \
--to=josh.wu@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=s.nawrocki@samsung.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.