From: Mark Brown <broonie@kernel.org>
To: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH RFC SPI for-next 2/2] spi: microchip: pci1xxxx: Add suspend and resume support for PCI1XXXX SPI driver
Date: Wed, 28 Sep 2022 12:30:11 +0100 [thread overview]
Message-ID: <YzQwQwL4NOTMMe18@sirena.org.uk> (raw)
In-Reply-To: <20220928034336.2939265-3-tharunkumar.pasumarthi@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
On Wed, Sep 28, 2022 at 09:13:36AM +0530, Tharun Kumar P wrote:
> + for (iter = 0; iter < spi_ptr->total_hw_instances; iter++) {
> + spi_sub_ptr = spi_ptr->spi_int[iter];
> +
> + /* Store existing config before suspend */
> + store_restore_config(spi_ptr, spi_sub_ptr, iter, 1);
> + spi_master_suspend(spi_sub_ptr->spi_host);
> + writel(reg1, spi_ptr->reg_base +
> + SPI_MST_EVENT_MASK_REG_OFFSET(iter));
> + }
This saves the register configuration before suspending the device,
meaning there may be in progress transfers changing the device while the
save is going on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-28 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 3:43 [PATCH RFC SPI for-next 0/2] spi: microchip: pci1xxxx: Load SPI driver for SPI endpoint of PCI1XXXX switch Tharun Kumar P
2022-09-28 3:43 ` [PATCH RFC SPI for-next 1/2] spi: microchip: pci1xxxx: Add driver for SPI controller of PCI1XXXX PCIe switch Tharun Kumar P
2022-09-28 11:26 ` Mark Brown
2022-09-30 5:51 ` Tharunkumar.Pasumarthi
2022-09-28 3:43 ` [PATCH RFC SPI for-next 2/2] spi: microchip: pci1xxxx: Add suspend and resume support for PCI1XXXX SPI driver Tharun Kumar P
2022-09-28 11:30 ` Mark Brown [this message]
2022-09-30 5:56 ` Tharunkumar.Pasumarthi
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=YzQwQwL4NOTMMe18@sirena.org.uk \
--to=broonie@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tharunkumar.pasumarthi@microchip.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
all inboxes | Powered by JetHome®