Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	spi-devel-general <spi-devel-general@lists.sourceforge.net>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH v3 1/1] OMAP2: Spi: Force CS to be in inactive state after off-mode transition
Date: Fri, 12 Nov 2010 12:37:14 -0800	[thread overview]
Message-ID: <8739r6qnwl.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4CDD6F21.7000609@free-electrons.com> (Gregory CLEMENT's message of "Fri, 12 Nov 2010 17:45:21 +0100")

Gregory CLEMENT <gregory.clement@free-electrons.com> writes:

> When SPI wake up from OFF mode, CS is in the wrong state: force it to
> the inactive state.
>
> During the system life, I monitored the CS behavior using a
> oscilloscope. I also activated debug in omap2_mcspi, so I saw when
> driver disable the clocks and
> Each time the CS was in the correct state.
> It was only when system was put suspend to ram with off-mode activated
> that on resume the CS was in wrong state( ie activated).
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>

Lots of whitespace issues in this patch, please run through checkpatch.

> ---
>  drivers/spi/omap2_mcspi.c |   29 +++++++++++++++++++++++++++++
>  1 files changed, 29 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/spi/omap2_mcspi.c b/drivers/spi/omap2_mcspi.c
> index 2a651e6..708990e 100644
> --- a/drivers/spi/omap2_mcspi.c
> +++ b/drivers/spi/omap2_mcspi.c
> @@ -1305,11 +1305,40 @@ static int __exit omap2_mcspi_remove(struct
> platform_device *pdev)
>  /* work with hotplug and coldplug */
>  MODULE_ALIAS("platform:omap2_mcspi");
>  +#ifdef	CONFIG_PM
> +/* When SPI wake up, CS is in wrong state: force it to unactive state*/

This comment should be more specific that only this condition happens
only on off-mode wakeups

> +static int omap2_mcspi_resume(struct platform_device *pdev)
> +{
> +	struct spi_master	*master;
> +	struct omap2_mcspi	*mcspi;
> +	struct omap2_mcspi_cs *cs;
> +
> +	master = dev_get_drvdata(&pdev->dev);
> +	mcspi = spi_master_get_devdata(master);
> +	omap2_mcspi_enable_clocks(master);

insert blank line here

> +	/* We need to togle CS state for OMAP take this chang in account*/
> +

remove blank line here

> +	list_for_each_entry(cs, &omap2_mcspi_ctx[master->bus_num - 1].cs,
> +			    node)
> +    {

this '{' belongs on like above 

> +        MOD_REG_BIT(cs->chconf0, OMAP2_MCSPI_CHCONF_FORCE, 1);
> +		__raw_writel(cs->chconf0, cs->base + OMAP2_MCSPI_CHCONF0);
> +        MOD_REG_BIT(cs->chconf0, OMAP2_MCSPI_CHCONF_FORCE, 0);
> +		__raw_writel(cs->chconf0, cs->base + OMAP2_MCSPI_CHCONF0);
> +    }

Rather than force the state to a hard-coded value, it seems better if
the driver instead restore the previous state, which could be saved
during suspend.

> +	omap2_mcspi_disable_clocks(master);
> +    return 0;
> +}
> +#else
> +#define	omap2_mcspi_resume	NULL
> +#endif
> +
>  static struct platform_driver omap2_mcspi_driver = {
>  	.driver = {
>  		.name =		"omap2_mcspi",
>  		.owner =	THIS_MODULE,
>  	},
> +	.resume =	omap2_mcspi_resume,
>  	.remove =	__exit_p(omap2_mcspi_remove),
>  };
>  -- 1.7.0.4

Kevin

  reply	other threads:[~2010-11-12 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 16:45 [PATCH v3 1/1] OMAP2: Spi: Force CS to be in inactive state after off-mode transition Gregory CLEMENT
2010-11-12 20:37 ` Kevin Hilman [this message]
2010-11-12 23:01   ` Gregory CLEMENT

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=8739r6qnwl.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=grant.likely@secretlab.ca \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-omap@vger.kernel.org \
    --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