linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: William Breathitt Gray <wbg@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, andy.shevchenko@gmail.com,
	William Breathitt Gray <william.gray@linaro.org>
Subject: Re: [PATCH 1/3] counter: i8254: Introduce the Intel 8254 interface library module
Date: Tue, 20 Jun 2023 17:03:53 +0300	[thread overview]
Message-ID: <32ddaa7b-53a8-d61f-d526-b545bd561337@linux.intel.com> (raw)
In-Reply-To: <ZIHpGUWZ8wE7tkJP@ishi>

Hi

On 6/8/23 17:43, William Breathitt Gray wrote:
> On Sun, Apr 16, 2023 at 01:36:53PM -0400, William Breathitt Gray wrote:
>> Exposes consumer library functions providing support for interfaces
>> compatible with the venerable Intel 8254 Programmable Interval Timer
>> (PIT).
>>
>> The Intel 8254 PIT first appeared in the early 1980s and was used
>> initially in IBM PC compatibles. The popularity of the original Intel
>> 825x family of chips led to many subsequent variants and clones of the
>> interface in various chips and integrated circuits. Although still
>> popular, interfaces compatible with the Intel 8254 PIT are nowdays
>> typically found embedded in larger VLSI processing chips and FPGA
>> components rather than as discrete ICs.
>>
>> A CONFIG_I8254 Kconfig option is introduced by this patch. Modules
>> wanting access to these i8254 library functions should select this
>> Kconfig option, and import the I8254 symbol namespace.
>>
>> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
> 
> I've queued this patch to the counter-next branch of my Counter tree.
> 
> Jonathan, Bart, I've created an immutable branch with just this patch
> for you to pull which should allow you each to merge the other patch in
> this patchset for your respective tree.
> 
I noticed this patch cause in linux-next "Counter support" submenu to 
disappear and its menu entries are listed directly in "Device Drivers" menu.

Then I wonder why the CONFIG_I8254 has the help text defined since 
drivers should select it.

Or was the idea something like below?

diff --git a/drivers/counter/Kconfig b/drivers/counter/Kconfig
index bca21df51168..80631b5b0fc6 100644
--- a/drivers/counter/Kconfig
+++ b/drivers/counter/Kconfig
@@ -10,9 +10,10 @@ menuconfig COUNTER
           interface. You only need to enable this, if you also want to 
enable
           one or more of the counter device drivers below.

+if COUNTER
+
  config I8254
-       tristate
-       select COUNTER
+       tristate "i8254 interface library"
         select REGMAP
         help
           Enables support for the i8254 interface library functions. 
The i8254
@@ -25,8 +26,6 @@ config I8254

           If built as a module its name will be i8254.

-if COUNTER
-
  config 104_QUAD_8
         tristate "ACCES 104-QUAD-8 driver"
         depends on (PC104 && X86) || COMPILE_TEST

  reply	other threads:[~2023-06-20 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 17:36 [PATCH 0/3] Add Intel 8254 Counter support William Breathitt Gray
2023-04-16 17:36 ` [PATCH 1/3] counter: i8254: Introduce the Intel 8254 interface library module William Breathitt Gray
2023-06-08 14:43   ` William Breathitt Gray
2023-06-20 14:03     ` Jarkko Nikula [this message]
2023-06-12  5:14       ` William Breathitt Gray
2023-04-16 17:36 ` [PATCH 2/3] gpio: 104-dio-48e: Add Counter/Timer support William Breathitt Gray
2023-05-17 14:35   ` Bartosz Golaszewski
2023-05-20 19:28   ` Linus Walleij
2023-05-22 16:44     ` William Breathitt Gray
2023-04-16 17:36 ` [PATCH 3/3] iio: addac: stx104: Add 8254 " William Breathitt Gray
2023-05-20  9:53 ` [PATCH 0/3] Add Intel 8254 Counter support andy.shevchenko
2023-05-22 16:20   ` William Breathitt Gray

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=32ddaa7b-53a8-d61f-d526-b545bd561337@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wbg@kernel.org \
    --cc=william.gray@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;
as well as URLs for NNTP newsgroup(s).