From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Olof Johansson <olof@lixom.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Doug Anderson <dianders@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: Make CROS_EC_PROTO a user selectable option
Date: Tue, 18 Aug 2015 15:02:26 +0200 [thread overview]
Message-ID: <55D32CE2.3050605@osg.samsung.com> (raw)
In-Reply-To: <1525696.gQFOjPpKHL@amdc1976>
Hello Bartlomiej,
Thanks a lot for your feedback.
On 08/18/2015 02:40 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Tuesday, August 18, 2015 09:15:06 AM Javier Martinez Canillas wrote:
>> The boolean CROS_EC_PROTO symbol is selected by MFD_CROS_EC but that can
>> cause Kconfig circular dependencies so is better to change the select to
>
> Could you please give a reference to the problem or error message
> that you're getting (I was not following the previous discussion).
>
Yes, the original Kconfig warning message was:
warning: (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies (X86 || ARM)
Paul fixed on [0] by making MFD_CROS_EC depends on X86 || ARM but that
is not really true since the driver could be used in other platforms so
I tried to instead fix it by removing unneeded dependencies in [1] but
one of the patches was nacked by Geert [2] who mentioned the issue about
mixing select and "depends on".
>> a depends on. But in order to be able to change that, the CROS_EC_PROTO
>> symbol has to be one that can be selected by the user.
>
> Looking at the code behind the config option it seems that it is just
> a helper library and should not be made user-visible. Why can't
Yeah, I in fact used as a reference the DRM/KMS helpers (DRM_KMS_HELPER)
that is selected by drivers instead of depending on it.
> the issue be fixed the other way (make other config options select
> CROS_EC_PROTO consistently)?
>
That is another option indeed. I thought that the use of select was
discouraged and that it was preferable to use "depends on" even when
the Kconfig symbol is a boolean to enable support for some helpers.
But I don't really have a strong opinion on either approach tbh.
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
[0]: https://lkml.org/lkml/2015/6/20/219
[1]: https://lkml.org/lkml/2015/6/24/689
[2]: https://lkml.org/lkml/2015/8/17/103
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-08-18 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 7:15 [PATCH] platform/chrome: Make CROS_EC_PROTO a user selectable option Javier Martinez Canillas
2015-08-18 12:40 ` Bartlomiej Zolnierkiewicz
2015-08-18 13:02 ` Javier Martinez Canillas [this message]
2015-08-18 13:36 ` Bartlomiej Zolnierkiewicz
2015-08-18 13:44 ` Javier Martinez Canillas
2015-08-18 13:54 ` Geert Uytterhoeven
2015-08-18 14:05 ` Javier Martinez Canillas
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=55D32CE2.3050605@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=geert@linux-m68k.org \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sjoerd.simons@collabora.co.uk \
/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.