From: Randy Dunlap <rdunlap@infradead.org>
To: Alexander Stein <alexanders83@web.de>, Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Linus Walleij (linus.walleij@linaro.org)"
<linus.walleij@linaro.org>
Subject: Re: linux-next: Tree for Jun 27 (pinctrl && !CONFIG_OF)
Date: Tue, 28 Jun 2016 01:25:07 -0700 [thread overview]
Message-ID: <57723463.8070402@infradead.org> (raw)
In-Reply-To: <2044946.aGLaEK2W6I@ws-stein>
On 06/28/16 00:00, Alexander Stein wrote:
> On Monday 27 June 2016 23:36:29, Arnd Bergmann wrote:
>> On Monday, June 27, 2016 11:15:25 AM CEST Randy Dunlap wrote:
>>> On 06/26/16 23:39, Stephen Rothwell wrote:
>>>> Hi all,
>>>
>>>> Changes since 20160624:
>>> on i386, when CONFIG_OF is not enabled ...
>>> but OF_GPIO is enabled due to this in drivers/gpio/Kconfig:
>>>
>>> config OF_GPIO
>>>
>>> def_bool y
>>> depends on OF || COMPILE_TEST
>>>
>>> (above from commit 1e4a80640338924b9f9fd7a121ac31d08134410a
>>> from Alexander Stein <alexanders83@web.de>)
>>>
>>>
>>> ../drivers/pinctrl/bcm/pinctrl-iproc-gpio.c:381:20: error:
>>> 'pinconf_generic_dt_node_to_map_pin' undeclared here (not in a function)
>>> ../drivers/pinctrl/bcm/pinctrl-cygnus-mux.c:739:20: error:
>>> 'pinconf_generic_dt_node_to_map_group' undeclared here (not in a
>>> function) ../drivers/pinctrl/bcm/pinctrl-nsp-gpio.c:365:20: error:
>>> 'pinconf_generic_dt_node_to_map_pin' undeclared here (not in a function)
>>>
>>> because that function is only present when CONFIG_OF is enabled.
>>>
>>>
>>> Also, why does that commit (1e4a80640338924b9f9fd7a121ac31d08134410a)
>>> not have any other S-O-B lines in it? like whoever merged it?
>>
>> (adding Linus Walleij and Alexander Stein to Cc)
>>
>> Unfortunately, the changelog also doesn't say what triggered that
>> change. I guess there was a driver that did 'select OF_GPIO'
>> and had a dependency on COMPILE_TEST, though I don't see any
>> driver doing that in linux-next.
>
> It was the first change of the changes done in my branch
> https://github.com/AlexanderStein/linux/tree/gpio-compile-test
> in order to compile test as much gpio drivers as possible. Yet, pinctrl
> drivers were out of my scope.
>
>> I think the commit should just be reverted, it clearly breaks
>> stuff, and whatever needs it can be fixed in a better way.
>
> Why not depend PINCTRL_IPROC_GPIO on CONFIG_OF as Randy stated
> pinconf_generic_dt_node_to_map_pin and friends are only present if CONFIG_OF
> is enabled. Depending on OF_GPIO only is enough under the assumption a) you
> made below.
> Also what about providing dummy implementation for those missing function in
> case CONFIG_OF is disabled, my preference as more code can be compile tested.
IMO we shouldn't have to make function stubs just for COMPILE_TEST.
>> Specifically, we have three ways that the OF_GPIO symbol
>> is used:
>>
>> a) it is implicitly enabled when both GPIOLIB and OF are turned on
>
> or if COMPILE_TEST is enabled
>
> I think a problem in this and possibly other cases is that COMPILE_TEST
> loosens the Kconfig dependencies to some degree. How to proceed? Allow compile
> testing drivers only if some optional settings are enabled?
--
~Randy
next prev parent reply other threads:[~2016-06-28 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 6:39 linux-next: Tree for Jun 27 Stephen Rothwell
2016-06-27 18:15 ` linux-next: Tree for Jun 27 (pinctrl && !CONFIG_OF) Randy Dunlap
2016-06-27 21:36 ` Arnd Bergmann
2016-06-28 7:00 ` Alexander Stein
2016-06-28 8:25 ` Randy Dunlap [this message]
2016-06-28 8:37 ` Arnd Bergmann
2016-06-29 5:54 ` Alexander Stein
2016-07-04 9:46 ` Linus Walleij
2016-07-04 16:12 ` Randy Dunlap
2016-07-05 6:48 ` Linus Walleij
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=57723463.8070402@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexanders83@web.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 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.