From: William Breathitt Gray <vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
mail-APzI5cXaD1zVlRWJc41N0YvC60bnQu0Y@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] Change ISA_BUS_API dependency to selection
Date: Thu, 28 Dec 2017 23:25:41 -0500 [thread overview]
Message-ID: <20171229042541.GA321@sophia> (raw)
In-Reply-To: <4339f82b-5f37-fb8d-2725-d45747608c2e-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
On Thu, Dec 28, 2017 at 09:03:22AM -0800, Guenter Roeck wrote:
>On 12/28/2017 08:01 AM, William Breathitt Gray wrote:
>> The ISA_BUS_API Kconfig option enables the compilation of the ISA bus
>> driver. The ISA bus driver does not perform any hardware interaction,
>> and is instead just a thin layer of software abstraction to eliminate
>> boilerplate code common to ISA-style device drivers. Since ISA_BUS_API
>> has no dependencies and does not jeopardize the integrity of the system
>> when enabled, drivers should select it when the ISA bus driver
>> functionality is needed.
>>
>> Originally, when the ISA_BUS_API Kconfig option was introduced, it
>> served a dual-purpose of masking drivers ISA-style devices not commonly
>> found for desktop systems, such as the PC/104 device drivers. This
>> secondary semantic was inappropriate for the ISA_BUS_API option, and
>> proper masking of these device drivers is now accomplished via dedicated
>> Kconfig options such as CONFIG_PC104.
>>
>> Linus, please pickup this entire patchset through your GPIO subsystem
>> tree; a recursive dependency error is present if these patches are
>> cherry-picked (see https://lkml.org/lkml/2017/12/26/235), so they should
>> be merged together in the same tree.
>>
>> Maciej, this patchset resolves the recursive dependency issue you
>> encountered, so now you should be able to submit your Winbond GPIO
>> driver with the ISA_BUS_API selection as desired.
>>
>> William Breathitt Gray (3):
>> iio: Change ISA_BUS_API dependency to selection
>> watchdog: Change ISA_BUS_API dependency to selection
>> gpio: Change ISA_BUS_API dependency to selection
>>
>> drivers/gpio/Kconfig | 14 +++++++++-----
>> drivers/iio/adc/Kconfig | 3 ++-
>> drivers/iio/counter/Kconfig | 3 ++-
>> drivers/iio/dac/Kconfig | 3 ++-
>> drivers/watchdog/Kconfig | 3 ++-
>> 5 files changed, 17 insertions(+), 9 deletions(-)
>>
>But why keep "config ISA_BUS" ? Its only purpose is to select ISA_BUS_API.
I intend to have CONFIG_ISA_BUS now serve purely as a mask for true ISA
device drivers (e.g. CIO_DAC within this patchset). The legacy
CONFIG_ISA has a X86_32 dependency which prevents its use for X86_64
builds -- and unfortunately existing drivers depending on CONFIG_ISA
expect the X86_32 arch, thus making the task of decoupling that arch
dependency difficult. I'm hoping CONFIG_ISA_BUS can therefore supersede
the legacy CONFIG_ISA because an ISA bus can physically exist on a
non-X86_32 system.
However, there is no longer a need to select ISA_BUS_API, so that should
be removed, as well as the help text updated to match the changes. I'll
make these updates and submit a version 2 of this patchset some time
tomorrow then.
William Breathitt Gray
>
>Guenter
WARNING: multiple messages have this Message-ID (diff)
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linus.walleij@linaro.org, mail@maciej.szmigiero.name,
linux-gpio@vger.kernel.org, linux-iio@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Change ISA_BUS_API dependency to selection
Date: Thu, 28 Dec 2017 23:25:41 -0500 [thread overview]
Message-ID: <20171229042541.GA321@sophia> (raw)
In-Reply-To: <4339f82b-5f37-fb8d-2725-d45747608c2e@roeck-us.net>
On Thu, Dec 28, 2017 at 09:03:22AM -0800, Guenter Roeck wrote:
>On 12/28/2017 08:01 AM, William Breathitt Gray wrote:
>> The ISA_BUS_API Kconfig option enables the compilation of the ISA bus
>> driver. The ISA bus driver does not perform any hardware interaction,
>> and is instead just a thin layer of software abstraction to eliminate
>> boilerplate code common to ISA-style device drivers. Since ISA_BUS_API
>> has no dependencies and does not jeopardize the integrity of the system
>> when enabled, drivers should select it when the ISA bus driver
>> functionality is needed.
>>
>> Originally, when the ISA_BUS_API Kconfig option was introduced, it
>> served a dual-purpose of masking drivers ISA-style devices not commonly
>> found for desktop systems, such as the PC/104 device drivers. This
>> secondary semantic was inappropriate for the ISA_BUS_API option, and
>> proper masking of these device drivers is now accomplished via dedicated
>> Kconfig options such as CONFIG_PC104.
>>
>> Linus, please pickup this entire patchset through your GPIO subsystem
>> tree; a recursive dependency error is present if these patches are
>> cherry-picked (see https://lkml.org/lkml/2017/12/26/235), so they should
>> be merged together in the same tree.
>>
>> Maciej, this patchset resolves the recursive dependency issue you
>> encountered, so now you should be able to submit your Winbond GPIO
>> driver with the ISA_BUS_API selection as desired.
>>
>> William Breathitt Gray (3):
>> iio: Change ISA_BUS_API dependency to selection
>> watchdog: Change ISA_BUS_API dependency to selection
>> gpio: Change ISA_BUS_API dependency to selection
>>
>> drivers/gpio/Kconfig | 14 +++++++++-----
>> drivers/iio/adc/Kconfig | 3 ++-
>> drivers/iio/counter/Kconfig | 3 ++-
>> drivers/iio/dac/Kconfig | 3 ++-
>> drivers/watchdog/Kconfig | 3 ++-
>> 5 files changed, 17 insertions(+), 9 deletions(-)
>>
>But why keep "config ISA_BUS" ? Its only purpose is to select ISA_BUS_API.
I intend to have CONFIG_ISA_BUS now serve purely as a mask for true ISA
device drivers (e.g. CIO_DAC within this patchset). The legacy
CONFIG_ISA has a X86_32 dependency which prevents its use for X86_64
builds -- and unfortunately existing drivers depending on CONFIG_ISA
expect the X86_32 arch, thus making the task of decoupling that arch
dependency difficult. I'm hoping CONFIG_ISA_BUS can therefore supersede
the legacy CONFIG_ISA because an ISA bus can physically exist on a
non-X86_32 system.
However, there is no longer a need to select ISA_BUS_API, so that should
be removed, as well as the help text updated to match the changes. I'll
make these updates and submit a version 2 of this patchset some time
tomorrow then.
William Breathitt Gray
>
>Guenter
next prev parent reply other threads:[~2017-12-29 4:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 16:01 [PATCH 0/3] Change ISA_BUS_API dependency to selection William Breathitt Gray
2017-12-28 16:01 ` William Breathitt Gray
[not found] ` <cover.1514475654.git.vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-28 16:01 ` [PATCH 1/3] iio: " William Breathitt Gray
2017-12-28 16:01 ` William Breathitt Gray
2017-12-28 17:03 ` [PATCH 0/3] " Guenter Roeck
2017-12-28 17:03 ` Guenter Roeck
[not found] ` <4339f82b-5f37-fb8d-2725-d45747608c2e-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-12-29 4:25 ` William Breathitt Gray [this message]
2017-12-29 4:25 ` William Breathitt Gray
2017-12-28 16:02 ` [PATCH 2/3] watchdog: " William Breathitt Gray
2017-12-28 18:37 ` Guenter Roeck
2017-12-28 16:02 ` [PATCH 3/3] gpio: " William Breathitt Gray
2018-01-02 9:18 ` Linus Walleij
2018-01-02 9:19 ` Linus Walleij
2017-12-28 22:53 ` [PATCH 0/3] " Maciej S. Szmigiero
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=20171229042541.GA321@sophia \
--to=vilhelm.gray-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mail-APzI5cXaD1zVlRWJc41N0YvC60bnQu0Y@public.gmane.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.