mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: Harini Katakam <harinik@xilinx.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	rob@landley.net, grant.likely@linaro.org,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	michals@xilinx.com
Subject: Re: [PATCH] SPI: Add driver for Cadence SPI controller
Date: Mon, 17 Mar 2014 18:14:40 +0000	[thread overview]
Message-ID: <20140317181440.GY11706@sirena.org.uk> (raw)
In-Reply-To: <20140317175911.GU18529@joshc.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On Mon, Mar 17, 2014 at 12:59:11PM -0500, Josh Cartwright wrote:
> On Mon, Mar 17, 2014 at 05:30:17PM +0000, Mark Brown wrote:
> > On Mon, Mar 17, 2014 at 05:35:36PM +0530, Harini Katakam wrote:

> > > +static int __maybe_unused cdns_spi_suspend(struct device *dev)
> > > +{

> > This needs to call spi_master_suspend() as well (and similarly on
> > resume).

> I'm not that familiar with the SPI core, but this seems like an
> inversion.  Is there a reason why the SPI master class doesn't implement
> suspend/resume() callbacks which handle stopping/starting the queue
> automatically for all masters?

This is for users of an optional feature of the infrastructure.  We
probably should just call it anyway since it does have checks for the
feature being used (but given all the open coding around this stuff I'd
need to verify that the class callbacks would reliably get called).

In any case that's not happening now and the driver as it stands is
buggy since it's trampling all over the hardware without syncing with
anything that isn't ongoing.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-03-17 18:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 12:05 Harini Katakam
2014-03-17 12:47 ` Rob Herring
2014-03-17 13:14   ` Mark Brown
2014-03-17 13:22   ` Michal Simek
2014-03-17 13:30     ` Geert Uytterhoeven
2014-03-17 13:54     ` Harini Katakam
2014-03-17 19:00     ` Rob Herring
2014-03-20 11:23       ` Michal Simek
2014-03-17 14:01   ` Harini Katakam
2014-03-17 17:30 ` Mark Brown
2014-03-17 17:59   ` Josh Cartwright
2014-03-17 18:14     ` Mark Brown [this message]
2014-03-18  5:22       ` Harini Katakam
2014-03-18 11:06         ` Mark Brown
2014-03-18  5:16   ` Harini Katakam
2014-03-18 11:04     ` Mark Brown
2014-03-18 12:13       ` Harini Katakam
2014-03-18 12:33         ` Mark Brown
2014-03-18 14:45           ` Harini Katakam
2014-03-18 15:59             ` 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=20140317181440.GY11706@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=harinik@xilinx.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=joshc@codeaurora.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michals@xilinx.com \
    --cc=pawel.moll@arm.com \
    --cc=rob@landley.net \
    --cc=robh+dt@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

Powered by JetHome