From: Mark Brown <broonie@kernel.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org,
linux-spi <linux-spi@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH v1 3/4] spi/xilinx: Simplify irq allocation
Date: Tue, 9 Jul 2013 15:47:04 +0100 [thread overview]
Message-ID: <20130709144704.GY27646@sirena.org.uk> (raw)
In-Reply-To: <51DC1AF1.3090401@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Tue, Jul 09, 2013 at 04:15:13PM +0200, Michal Simek wrote:
> 4. spi_master_release()
> 5. devres_release() with irq
> If interrupt happends between 4 and 5 than it can be the problem.
> Do I understand you correctly?
Yes.
> If this is problematic case we can disable local and global interrupts
> and add it between 2 and 3 or 3-4.
> /* Disable all the interrupts just in case */
> xspi->write_fn(0, regs_base + XIPIF_V123B_IIER_OFFSET);
> /* Disable the global IPIF interrupt */
> xspi->write_fn(0, regs_base + XIPIF_V123B_DGIER_OFFSET);
> What do you think about this solution?
That's fine, though if just manually freeing the IRQ works that's also
OK...
> I have also tried to run one thing with and without this patch
> and the results are below.
> When I add this irq disable function between 1 and 2 then
> module removing stucks.
You'll need to wait until the device is quiesced at least if it's
relying on the interrupt to complete operations.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-09 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 13:29 [PATCH v1 1/4] spi/xilinx: Remove CONFIG_OF from the driver Michal Simek
2013-07-08 13:29 ` [PATCH v1 2/4] spi/xilinx: Clean ioremap calling Michal Simek
2013-07-08 14:50 ` Mark Brown
2013-07-08 13:29 ` [PATCH v1 3/4] spi/xilinx: Simplify irq allocation Michal Simek
2013-07-08 14:49 ` Mark Brown
2013-07-08 15:48 ` Michal Simek
2013-07-08 16:26 ` Mark Brown
2013-07-09 14:15 ` Michal Simek
2013-07-09 14:47 ` Mark Brown [this message]
2013-07-09 14:53 ` Michal Simek
2013-07-12 14:00 ` Michal Simek
2013-08-22 13:10 ` Mark Brown
2013-07-08 13:29 ` [PATCH v1 4/4] spi/xilinx: Use of_property_read_u32 for reading value from node Michal Simek
2013-07-08 14:51 ` Mark Brown
2013-07-09 5:26 ` Michal Simek
2013-07-09 9:14 ` Mark Brown
2013-07-08 14:49 ` [PATCH v1 1/4] spi/xilinx: Remove CONFIG_OF from the driver Mark Brown
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=20130709144704.GY27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=spi-devel-general@lists.sourceforge.net \
/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®