[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5282acd1-3c7a-4948-83f2-2829910ab841@sirena.org.uk>
Date: Tue, 12 Sep 2023 15:03:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Zev Weiss <zev@...ilderbeest.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Naresh Solanki <naresh.solanki@...ements.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output
On Sun, Sep 10, 2023 at 01:50:37PM -0700, Zev Weiss wrote:
> On Mon, Sep 04, 2023 at 05:24:31AM PDT, Mark Brown wrote:
> > It's a clear on read interrupt.
> Sure, analogous behavior in hardware is reasonably common, but that doesn't
> strike me as a very compelling reason to design the kernel<->userspace
> interface to mimic it -- providing nicer interfaces than the raw hardware is
> one of the main reasons for having an OS in the first place, after all.
If it were something other than the userspace consumer I'd be a bit more
concerned but that's all sharp edges and direct access in a very
controlled system. In any case clear on write is the obvious
alternative approach.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists