From: Maxime Ripard <mripard@kernel.org>
To: Paul Kocialkowski <paulk@sys-base.io>
Cc: linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Paul Kocialkowski" <contact@paulk.fr>
Subject: Re: [PATCH] pinctrl: sunxi: Use minimal debouncing period as default
Date: Wed, 20 Nov 2024 09:01:53 +0100 [thread overview]
Message-ID: <20241120-wild-stimulating-prawn-ffefb7@houat> (raw)
In-Reply-To: <ZzzdT0wr0u1ApVgV@collins>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
On Tue, Nov 19, 2024 at 07:47:43PM +0100, Paul Kocialkowski wrote:
> > > In any case I don't think it makes sense for the platform code to impose
> > > what a reasonable period for interrupts is (especially with such a large
> > > period as default).
> >
> > So you don't think it makes sense for the platform code to impose a
> > reasonable period, so you want to impose a (more, obviously) reasonable
> > period?
>
> Yes absolutely. Anything that brings us closer to "you get what is really
> happening with the hardware". The sunxi controller doesn't allow disabling
> debouncing entirely, so the next best thing is to have it with the smallest
> period.
That's an opinion, not a fact.
> > If anything, the status quo doesn't impose anything, it just rolls with
> > the hardware default. Yours would impose one though.
>
> The result is that it puts a strong limitation and breaks many use cases by
> default. I don't think we have to accept whatever register default was chosen
> by hardware engineers as the most sensible default choice and pretend that this
> is not a policy decision.
You're making it much worse than it is. It doesn't "break many use
cases" it broke one, by default, with a supported way to unbreak it, in
12 years.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-11-20 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 14:08 [PATCH] pinctrl: sunxi: Use minimal debouncing period as default Paul Kocialkowski
2024-11-19 14:43 ` Maxime Ripard
2024-11-19 15:00 ` Paul Kocialkowski
2024-11-19 15:43 ` Maxime Ripard
2024-11-19 18:47 ` Paul Kocialkowski
2024-11-20 8:01 ` Maxime Ripard [this message]
2024-11-20 10:05 ` Paul Kocialkowski
2024-11-29 15:37 ` Maxime Ripard
2024-11-30 10:34 ` Paul Kocialkowski
2024-12-02 11:03 ` Maxime Ripard
2024-12-03 10:58 ` Paul Kocialkowski
2024-12-17 13:39 ` Linus Walleij
2025-01-07 11:53 ` Paul Kocialkowski
2024-12-17 13:41 ` Linus Walleij
2024-12-17 13:58 ` Maxime Ripard
2025-01-07 11:55 ` Paul Kocialkowski
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=20241120-wild-stimulating-prawn-ffefb7@houat \
--to=mripard@kernel.org \
--cc=contact@paulk.fr \
--cc=jernej.skrabec@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=paulk@sys-base.io \
--cc=samuel@sholland.org \
--cc=ukleinek@kernel.org \
--cc=wens@csie.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.