linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: "Thomas Richard" <thomas.richard@bootlin.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Tony Lindgren" <tony@atomide.com>,
	"Haojian Zhuang" <haojian.zhuang@linaro.org>,
	"Vignesh R" <vigneshr@ti.com>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Janusz Krzysztofik" <jmkrzyszt@gmail.com>,
	"Andi Shyti" <andi.shyti@kernel.org>,
	"Vinod Koul" <vkoul@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-pci@vger.kernel.org, gregory.clement@bootlin.com,
	theo.lebrun@bootlin.com, thomas.petazzoni@bootlin.com,
	u-kumar1@ti.com
Subject: Re: [PATCH v4 04/18] mux: add mux_chip_resume() function
Date: Tue, 3 Sep 2024 15:17:14 +0200	[thread overview]
Message-ID: <dd42f526-6da7-87f8-ad4c-bf18af41c665@axentia.se> (raw)
In-Reply-To: <20240102-j7200-pcie-s2r-v4-4-6f1f53390c85@bootlin.com>

Hi!

Sorry for being unresponsive.

2024-03-04 at 16:35, Thomas Richard wrote:
> The mux_chip_resume() function restores a mux_chip using the cached state
> of each mux.
> 
> Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
> ---
>  drivers/mux/core.c         | 29 +++++++++++++++++++++++++++++
>  include/linux/mux/driver.h |  1 +
>  2 files changed, 30 insertions(+)
> 
> diff --git a/drivers/mux/core.c b/drivers/mux/core.c
> index 775816112932..0742aa2a7c73 100644
> --- a/drivers/mux/core.c
> +++ b/drivers/mux/core.c
> @@ -215,6 +215,35 @@ void mux_chip_free(struct mux_chip *mux_chip)
>  }
>  EXPORT_SYMBOL_GPL(mux_chip_free);
>  
> +/**
> + * mux_chip_resume() - restores the mux-chip state
> + * @mux_chip: The mux-chip to resume.
> + *
> + * Restores the mux-chip state.
> + *
> + * Return: Zero on success or a negative errno on error.
> + */
> +int mux_chip_resume(struct mux_chip *mux_chip)
> +{
> +	int ret, i;
> +
> +	for (i = 0; i < mux_chip->controllers; ++i) {
> +		struct mux_control *mux = &mux_chip->mux[i];
> +
> +		if (mux->cached_state == MUX_CACHE_UNKNOWN)
> +			continue;
> +
> +		ret = mux_control_set(mux, mux->cached_state);

mux_control_set() is an internal helper. It is called from
__mux_control_select() and mux_control_deselect() (and on init...)

In all those cases, there is no race to reach the mux_control_set()
function, by means of the mux->lock semaphore (or the mux not being
"published" yet).

I fail to see how resume is safe when mux->lock is ignored?

Cheers,
Peter

> +		if (ret < 0) {
> +			dev_err(&mux_chip->dev, "unable to restore state\n");
> +			return ret;
> +		}
> +	}
> +
> +	return 0;
> +}
> +EXPORT_SYMBOL_GPL(mux_chip_resume);
> +
>  static void devm_mux_chip_release(struct device *dev, void *res)
>  {
>  	struct mux_chip *mux_chip = *(struct mux_chip **)res;
> diff --git a/include/linux/mux/driver.h b/include/linux/mux/driver.h
> index 18824064f8c0..2a7e5ec5d540 100644
> --- a/include/linux/mux/driver.h
> +++ b/include/linux/mux/driver.h
> @@ -88,6 +88,7 @@ struct mux_chip *mux_chip_alloc(struct device *dev,
>  int mux_chip_register(struct mux_chip *mux_chip);
>  void mux_chip_unregister(struct mux_chip *mux_chip);
>  void mux_chip_free(struct mux_chip *mux_chip);
> +int mux_chip_resume(struct mux_chip *mux_chip);
>  
>  struct mux_chip *devm_mux_chip_alloc(struct device *dev,
>  				     unsigned int controllers,
> 

  reply	other threads:[~2024-09-03 13:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 15:35 [PATCH v4 00/18] Add suspend to ram support for PCIe on J7200 Thomas Richard
2024-03-04 15:35 ` [PATCH v4 01/18] gpio: pca953x: move suspend()/resume() to suspend_noirq()/resume_noirq() Thomas Richard
2024-03-04 15:35 ` [PATCH v4 02/18] pinctrl: pinctrl-single: move suspend()/resume() callbacks to noirq Thomas Richard
2024-03-08  8:39   ` Tony Lindgren
2024-03-20  7:44   ` Dhruva Gole
2024-03-20  8:37     ` Thomas Richard
2024-03-28 21:07   ` Linus Walleij
2024-03-04 15:35 ` [PATCH v4 03/18] i2c: omap: wakeup the controller during suspend() callback Thomas Richard
2024-03-08  8:42   ` Tony Lindgren
2024-03-12  8:03     ` Wolfram Sang
2024-03-13  0:48       ` Andi Shyti
2024-03-13  6:21         ` Wolfram Sang
2024-03-13  0:37   ` Andi Shyti
2024-03-04 15:35 ` [PATCH v4 04/18] mux: add mux_chip_resume() function Thomas Richard
2024-09-03 13:17   ` Peter Rosin [this message]
2024-03-04 15:35 ` [PATCH v4 05/18] mux: mmio: add resume support Thomas Richard
2024-03-04 15:35 ` [PATCH v4 06/18] phy: ti: phy-j721e-wiz: use dev_err_probe() instead of dev_err() Thomas Richard
2024-03-04 15:35 ` [PATCH v4 07/18] phy: ti: phy-j721e-wiz: split wiz_clock_init() function Thomas Richard
2024-04-05 16:42   ` Vinod Koul
2024-03-04 15:35 ` [PATCH v4 08/18] phy: ti: phy-j721e-wiz: add resume support Thomas Richard
2024-04-05 16:44   ` Vinod Koul
2024-04-05 17:14     ` Andy Shevchenko
2024-03-04 15:35 ` [PATCH v4 09/18] phy: cadence-torrent: extract calls to clk_get from cdns_torrent_clk Thomas Richard
2024-03-04 15:35 ` [PATCH v4 10/18] phy: cadence-torrent: register resets even if the phy is already configured Thomas Richard
2024-03-04 15:35 ` [PATCH v4 11/18] phy: cadence-torrent: add already_configured to struct cdns_torrent_phy Thomas Richard
2024-03-04 15:35 ` [PATCH v4 12/18] phy: cadence-torrent: remove noop_ops phy operations Thomas Richard
2024-03-04 15:35 ` [PATCH v4 13/18] phy: cadence-torrent: add suspend and resume support Thomas Richard
2024-03-04 15:35 ` [PATCH v4 14/18] PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() Thomas Richard
2024-03-04 15:35 ` [PATCH v4 15/18] PCI: cadence: Set cdns_pcie_host_init() global Thomas Richard
2024-03-04 15:35 ` [PATCH v4 16/18] PCI: j721e: Use dev_err_probe() in the probe() function Thomas Richard
2024-04-10  7:51   ` Francesco Dolcini
2024-03-04 15:36 ` [PATCH v4 17/18] PCI: j721e: Add reset GPIO to struct j721e_pcie Thomas Richard
2024-03-04 15:36 ` [PATCH v4 18/18] PCI: j721e: Add suspend and resume support Thomas Richard
2024-03-13  6:51   ` Siddharth Vadapalli
2024-03-28 22:07   ` Bjorn Helgaas

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=dd42f526-6da7-87f8-ad4c-bf18af41c665@axentia.se \
    --to=peda@axentia.se \
    --cc=aaro.koskinen@iki.fi \
    --cc=andi.shyti@kernel.org \
    --cc=andy@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=brgl@bgdev.pl \
    --cc=gregory.clement@bootlin.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=jmkrzyszt@gmail.com \
    --cc=kishon@kernel.org \
    --cc=kw@linux.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=theo.lebrun@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas.richard@bootlin.com \
    --cc=tony@atomide.com \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.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).