From: Jonathan Cameron <jic23@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Milo.Kim@ti.com, Naveen Krishna Chatradhi <ch.naveen@samsung.com>,
Lee Jones <lee.jones@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Russ.Dill@ti.com, alexandre.belloni@free-electrons.com,
oleksandr.kozaruk@ti.com, B38611@freescale.com,
johannes.thumshirn@men.de, sre@debian.org,
Sachin Kamat <sachin.kamat@linaro.org>,
linux-iio <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: Nothing in ADC should be a bool CONFIG
Date: Thu, 24 Apr 2014 05:37:46 +0100 [thread overview]
Message-ID: <5358951A.3080507@kernel.org> (raw)
In-Reply-To: <CAD=FV=Ws7R0+nJagXswnqowxFvrxh6vTmKM_jwz8mnGbKr_aSg@mail.gmail.com>
On 23/04/14 22:54, Doug Anderson wrote:
> Jonathan,
>
> On Wed, Apr 23, 2014 at 1:54 PM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 22/04/14 01:03, Doug Anderson wrote:
>>>
>>> The whole IIO subsystem can be moved to a module. If you make it a
>>> module then stuff marked as "Y" in the adc directory simply won't be
>>> linked in properly.
>>>
>>> The two configs that were wrong were EXYNOS_ADC and LP8788_ADC. I
>>> know for a fact that EXYNOS_ADC will work as a module (though it
>>> appears to crash when you unload it--that needs to be addressed
>>> separately).
>>
>> I'd really like to see this pinned down before taking this patch.
>> I can see you argument that the current approach is clearly wrong,
>> but swapping one issue for another is not an approach I'd particularly
>> like to take...
>>
>> I can't immediately spot the cause of the crash, but there are certainly
>> some interesting order issues in this driver. Not enabling the vdd
>> regulator until after the userspace interfaces are exposed (by the
>> iio_device_register call) is interesting for a start.
>>
>> The remove doesn't run in the reverse of the probe order (see clocks
>> vs regulators for example.)
>>
>> Gah, my reviewing for one clearly missed some things in this driver.
>
> OK, fair enough. I took a quick look and couldn't spot anything
> either. I've requested that Samsung dig into these problems. If they
> are unable to I will take a crack at it as time permits. ;)
>
Cool and good luck (either way ;)
> Thanks!
>
> -Doug
> --
> 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:[~2014-04-24 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 0:03 [PATCH] iio: adc: Nothing in ADC should be a bool CONFIG Doug Anderson
2014-04-23 20:54 ` Jonathan Cameron
2014-04-23 21:54 ` Doug Anderson
2014-04-24 4:37 ` Jonathan Cameron [this message]
2014-04-24 20:23 ` Doug Anderson
2014-04-26 10:30 ` 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=5358951A.3080507@kernel.org \
--to=jic23@kernel.org \
--cc=B38611@freescale.com \
--cc=Milo.Kim@ti.com \
--cc=Russ.Dill@ti.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=ch.naveen@samsung.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.thumshirn@men.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr.kozaruk@ti.com \
--cc=sachin.kamat@linaro.org \
--cc=sre@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox