All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: manjugk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 : Fix McSPI RX Timeout
Date: Fri, 9 Oct 2009 12:25:59 -0700	[thread overview]
Message-ID: <20091009192559.GR25892@atomide.com> (raw)
In-Reply-To: <1254811036-22666-1-git-send-email-manjugk@ti.com>

* manjugk@ti.com <manjugk@ti.com> [091005 23:42]:
> McSPI RX timeout issues are reported on some of the OMAP3 custom boards.
> 
> After verifying configuration sequence in TRM, there seems to be issue with 
> McSPI configuration sequence.
> 
> The steps to be followed for both TX and RX:
> 1. Configure OMAP2_MCSPI_CHCONF0 register with required settings such as
> TX/RX mode, word length, force chip select(if required).
> 2. Set MS bit to 0 in OMAP2_MCSPI_CHCTRL0 register to provide the clock.
> 3. Enable SPI channel in OMAP2_MCSPI_MODULCTRL
> 
> But, the sequence used in current code seems to be wrong. Here it is:
> 1. Set MS bit to 0 in OMAP2_MCSPI_CHCTRL0 register to provide the clock
> (This is done during bootup)
> 2. Enable SPI channel in OMAP2_MCSPI_MODULCTRL
> 3. Configure OMAP2_MCSPI_CHCONF0 register with required settings such as
> TX/RX mode, word length, force chip select(if required).
> 
> After correcting configuration sequence, the timeout seems to be not
> reproducible anymore.

Please resend this to the right lists one for merging:

$ grep -A7 "SPI SUBSYSTEM" MAINTAINERS 
SPI SUBSYSTEM
M:      David Brownell <dbrownell@users.sourceforge.net>
L:      spi-devel-general@lists.sourceforge.net
S:      Maintained
F:      Documentation/spi/
F:      drivers/spi/
F:      include/linux/spi/

Please also Cc linux-omap list too so people can easily keep track of it.

Regards,

Tony


> 
> Signed-off-by: Manjunatha GK <manjugk@ti.com>
> ---
>  drivers/spi/omap2_mcspi.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/spi/omap2_mcspi.c b/drivers/spi/omap2_mcspi.c
> index ba1a872..846485c 100644
> --- a/drivers/spi/omap2_mcspi.c
> +++ b/drivers/spi/omap2_mcspi.c
> @@ -802,7 +802,6 @@ static void omap2_mcspi_work(struct work_struct *work)
>  		spi = m->spi;
>  		cs = spi->controller_state;
>  
> -		omap2_mcspi_set_enable(spi, 1);
>  		list_for_each_entry(t, &m->transfers, transfer_list) {
>  			if (t->tx_buf == NULL && t->rx_buf == NULL && t->len) {
>  				status = -EINVAL;
> @@ -830,6 +829,9 @@ static void omap2_mcspi_work(struct work_struct *work)
>  				chconf |= OMAP2_MCSPI_CHCONF_TRM_TX_ONLY;
>  			mcspi_write_chconf0(spi, chconf);
>  
> +			omap2_mcspi_set_master_mode(mcspi->master);
> +
> +			omap2_mcspi_set_enable(spi, 1);
>  			if (t->len) {
>  				unsigned	count;
>  
> -- 
> 1.6.0.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-10-09 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  6:37 [PATCH] OMAP3 : Fix McSPI RX Timeout manjugk
2009-10-09 19:25 ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-12 11:04 manjugk

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=20091009192559.GR25892@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manjugk@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.