linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michele Jr De Candia <michele.de_candia@alcatel-lucent.com>
To: <Linuxppc-dev@lists.ozlabs.org>
Subject: espi enable/disable issue
Date: Fri, 16 Sep 2011 12:28:34 +0200	[thread overview]
Message-ID: <1316168914.2033.190.camel@nbdecandia> (raw)

Hi all,
we're using your driver for espi controller on P1015 freescale micro.

We're testing an issue trying to do multiple operation into a single
chip select "window".

We've noted that the driver disables and enables the ESPI_SPMODE[EN] bit
in order to change the "ESPI_SPMODE x" register; probably it does it
because, such as for ESPI_SPMODE register, its bits can't change when
ESPI_SPMODE[EN] is enabled (although  the datasheet doesn't say nothing
about the mandatory disable operation for changing "ESPI_SPMODE x"
regs). 

The enable/disable operation issues a clock spike on SPI_CLK signal.

We need to do multiple SPI read/write into a single chip-select window
without changing SPIMODE and using an external chip select gpio.

Unfortunately, the clock spike generated from the enable/disable
operation its' destructive for our data.

We've tryed to remove the "enable/disable" operation into the
fsl_espi_setup_transfer() function but just the first operation went
fine; the next operation reply all as "FF". 

Seems that we can't do multiple operations into a single chip select
window without changing mode. Is it true? Is it possible to avoid this
issue (probably into the irq management)?

We're not using the last version of the driver but we've looked already
to the new driver uploaded into 3.0.4 kernel and the "Enable/Disable"
operation is still there.

Thank you in advance,
Michele De Candia
Angelo Spada

                 reply	other threads:[~2011-09-16 10:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1316168914.2033.190.camel@nbdecandia \
    --to=michele.de_candia@alcatel-lucent.com \
    --cc=Linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).