From: Jaehoon Chung <jh80.chung@samsung.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Szyprowski, Marek" <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH v2 06/14] mmc: dw_mmc: simplify optional reset handling
Date: Tue, 21 Mar 2017 21:12:20 +0900 [thread overview]
Message-ID: <22bbae56-e019-8be3-ffcc-ffcbe8d6ec53@samsung.com> (raw)
In-Reply-To: <CAPDyKFr-08ontZTfraOEAOROcb9pqFQkqzV4zMRA4OdsxXrvtQ@mail.gmail.com>
Hi All,
On 03/21/2017 03:10 AM, Ulf Hansson wrote:
> On 20 March 2017 at 12:00, Philipp Zabel <p.zabel@pengutronix.de> wrote:
>> On Mon, 2017-03-20 at 11:49 +0100, Andrzej Hajda wrote:
>>> On 20.03.2017 11:27, Philipp Zabel wrote:
>> [...]
>>>> diff --git a/include/linux/reset.h b/include/linux/reset.h
>>>> index 86b4ed75359e8..c905ff1c21ec6 100644
>>>> --- a/include/linux/reset.h
>>>> +++ b/include/linux/reset.h
>>>> @@ -74,14 +74,14 @@ static inline struct reset_control *__of_reset_control_get(
>>>> const char *id, int index, bool shared,
>>>> bool optional)
>>>> {
>>>> - return ERR_PTR(-ENOTSUPP);
>>>> + return optional ? NULL : ERR_PTR(-ENOTSUPP);
>>>> }
>>>>
>>>> static inline struct reset_control *__devm_reset_control_get(
>>>> struct device *dev, const char *id,
>>>> int index, bool shared, bool optional)
>>>> {
>>>> - return ERR_PTR(-ENOTSUPP);
>>>> + return optional ? NULL : ERR_PTR(-ENOTSUPP);
>>>> }
>>>>
>>>> #endif /* CONFIG_RESET_CONTROLLER */
>>>> ---------->8----------
>>>
>>> In dw_mmc.c file there are also unconditional calls to
>>> reset_control_assert, with disabled RESET_CONTROLLER it will cause
>>> unexpected WARNs.
>>> Anyway if you change reset API as above I think you should remove all
>>> warns from reset stubs, because NULL reset is valid, but these warns are
>>> there for reason - contradiction.
>>
>> You are right, I have to let go of those, too.
>
>
> Until fixed, I have dropped the three changes from my next branch
> related to this. Please re-post when fixed.
I missed this patch. If resend the patch, i will check.
Best Regards,
Jaehoon Chung
>
> Kind regards
> Uffe
>
>>
>> regards
>> Philipp
>>
>
>
>
prev parent reply other threads:[~2017-03-21 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170320092255eucas1p1459c023fd9b479c8e5323a6ac97dbf58@eucas1p1.samsung.com>
2017-03-15 11:31 ` [PATCH v2 06/14] mmc: dw_mmc: simplify optional reset handling Philipp Zabel
2017-03-16 14:46 ` Ulf Hansson
2017-03-20 9:22 ` Andrzej Hajda
2017-03-20 9:53 ` Philipp Zabel
2017-03-20 10:03 ` Andrzej Hajda
2017-03-20 10:27 ` Philipp Zabel
2017-03-20 10:49 ` Andrzej Hajda
2017-03-20 11:00 ` Philipp Zabel
2017-03-20 18:09 ` Ulf Hansson
2017-03-20 18:10 ` Ulf Hansson
2017-03-21 12:12 ` Jaehoon Chung [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=22bbae56-e019-8be3-ffcc-ffcbe8d6ec53@samsung.com \
--to=jh80.chung@samsung.com \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=ulf.hansson@linaro.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