From: Philipp Zabel <p.zabel@pengutronix.de>
To: Peter Rosin <peda@axentia.se>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jonathan Corbet <corbet@lwn.net>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Colin Ian King <colin.king@canonical.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
kernel@pengutronix.de
Subject: Re: [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes
Date: Mon, 24 Apr 2017 16:59:29 +0200 [thread overview]
Message-ID: <1493045969.2446.47.camel@pengutronix.de> (raw)
In-Reply-To: <6fb34ea5-edc8-c7aa-1d49-f6ce1d33a2d4@axentia.se>
On Mon, 2017-04-24 at 16:36 +0200, Peter Rosin wrote:
[...]
> > How about an atomic use_count on the mux_control, a bool shared that is
> > only set by the first consumer, and controls whether selecting locks?
>
> That has the drawback that it is hard to restore the mux-control in a safe
> way so that exclusive consumers are allowed after the last shared consumer
> puts the mux away.
True.
> Agreed, it's a corner case, but I had this very similar
> patch going through the compiler when I got this mail. Does it work as well
> as what you suggested?
Yes, this patch works just as well.
regards
Philipp
next prev parent reply other threads:[~2017-04-24 14:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 8:36 [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes Peter Rosin
[not found] ` <1493022995-16917-1-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2017-04-24 8:36 ` [PATCH v14 01/11] devres: trivial whitespace fix Peter Rosin
2017-04-24 8:36 ` [PATCH v14 04/11] mux: gpio: add mux controller driver for gpio based multiplexers Peter Rosin
2017-04-24 8:36 ` [PATCH v14 02/11] dt-bindings: document devicetree bindings for mux-controllers and gpio-mux Peter Rosin
2017-04-24 8:36 ` [PATCH v14 03/11] mux: minimal mux subsystem Peter Rosin
2017-04-24 8:36 ` [PATCH v14 05/11] iio: inkern: api for manipulating ext_info of iio channels Peter Rosin
2017-04-24 8:36 ` [PATCH v14 06/11] dt-bindings: iio: io-channel-mux: document io-channel-mux bindings Peter Rosin
2017-04-24 8:36 ` [PATCH v14 07/11] iio: multiplexer: new iio category and iio-mux driver Peter Rosin
2017-04-24 8:36 ` [PATCH v14 08/11] dt-bindings: i2c: i2c-mux: document general purpose i2c-mux bindings Peter Rosin
2017-04-24 8:36 ` [PATCH v14 09/11] i2c: i2c-mux-gpmux: new driver Peter Rosin
2017-04-24 8:36 ` [PATCH v14 10/11] dt-bindings: mux-adg792a: document devicetree bindings for ADG792A/G mux Peter Rosin
2017-04-24 8:36 ` [PATCH v14 11/11] mux: adg792a: add mux controller driver for ADG792A/G Peter Rosin
2017-04-24 10:52 ` [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes Philipp Zabel
[not found] ` <1493031179.2446.9.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-24 11:37 ` Peter Rosin
2017-04-24 12:38 ` Philipp Zabel
2017-04-24 14:10 ` Philipp Zabel
[not found] ` <1493043046.2446.37.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-24 14:36 ` Peter Rosin
2017-04-24 14:59 ` Philipp Zabel [this message]
[not found] ` <1493045969.2446.47.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-25 14:16 ` Peter Rosin
2017-04-25 14:55 ` Peter Rosin
[not found] ` <e53bbf82-793f-b22f-2e9b-4bd377446351-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2017-04-25 16:32 ` Philipp Zabel
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=1493045969.2446.47.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul.gortmaker@windriver.com \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).