From: Lars-Peter Clausen <lars@metafoo.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"William Breathitt Gray" <vilhelm.gray@gmail.com>
Cc: kernel@pengutronix.de,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Patrick Havelange <patrick.havelange@essensium.com>,
Kamel Bouhara <kamel.bouhara@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Syed Nayyar Waris <syednwaris@gmail.com>,
Oleksij Rempel <linux@rempel-privat.de>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
David Lechner <david@lechnology.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Ahmad Fatoum <a.fatoum@pengutronix.de>,
"Felipe Balbi (Intel)" <balbi@kernel.org>,
Raymond Tan <raymond.tan@intel.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH v2 00/23] counter: cleanups and device lifetime fixes
Date: Mon, 27 Dec 2021 13:25:25 +0100 [thread overview]
Message-ID: <c8f6446e-748b-5845-ae60-5d6b8f3e8d39@metafoo.de> (raw)
In-Reply-To: <20211227094526.698714-1-u.kleine-koenig@pengutronix.de>
On 12/27/21 10:45 AM, Uwe Kleine-König wrote:
> [...]
>
> - I wonder why counter is a bus and not a class device type. There is
> no driver that would ever bind a counter device, is there? So
> /sys/bus/counter/driver is always empty.
>
There used to be a time when GKH said that we do not want new driver
classes. And all new subsystems should use bus since bus is a superset
of class. This restriction has been eased since then.
But it was around when the IIO subsystem was merged and since the
counter subsystem originated from the IIO subsystem I assume it just
copied this.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-27 12:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 9:45 [PATCH v2 00/23] counter: cleanups and device lifetime fixes Uwe Kleine-König
2021-12-27 9:45 ` [PATCH v2 03/23] counter: microchip-tcb-capture: Drop unused platform_set_drvdata() Uwe Kleine-König
2021-12-28 17:38 ` Jonathan Cameron
2021-12-29 6:44 ` William Breathitt Gray
2021-12-27 9:45 ` [PATCH v2 07/23] counter: microchip-tcb-capture: Convert to counter_priv() wrapper Uwe Kleine-König
2021-12-28 18:05 ` Jonathan Cameron
2021-12-29 7:35 ` William Breathitt Gray
2021-12-27 9:45 ` [PATCH v2 11/23] counter: stm32-lptimer-cnt: " Uwe Kleine-König
2021-12-28 18:08 ` Jonathan Cameron
2021-12-29 7:48 ` William Breathitt Gray
2021-12-27 9:45 ` [PATCH v2 12/23] counter: stm32-timer-cnt: " Uwe Kleine-König
2021-12-28 18:08 ` Jonathan Cameron
2021-12-29 7:48 ` William Breathitt Gray
2021-12-27 9:45 ` [PATCH v2 20/23] counter: stm32-timer-cnt: Convert to new counter registration Uwe Kleine-König
2021-12-28 18:25 ` Jonathan Cameron
2021-12-29 8:37 ` William Breathitt Gray
2021-12-27 9:45 ` [PATCH v2 21/23] counter: stm32-lptimer-cnt: " Uwe Kleine-König
2021-12-28 18:26 ` Jonathan Cameron
2021-12-29 8:39 ` William Breathitt Gray
2021-12-27 12:25 ` Lars-Peter Clausen [this message]
2021-12-28 17:35 ` [PATCH v2 00/23] counter: cleanups and device lifetime fixes Jonathan Cameron
2021-12-29 8:49 ` 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=c8f6446e-748b-5845-ae60-5d6b8f3e8d39@metafoo.de \
--to=lars@metafoo.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=balbi@kernel.org \
--cc=benjamin.gaignard@st.com \
--cc=corbet@lwn.net \
--cc=david@lechnology.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=kamel.bouhara@bootlin.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@rempel-privat.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrick.havelange@essensium.com \
--cc=raymond.tan@intel.com \
--cc=syednwaris@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vilhelm.gray@gmail.com \
/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