All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: alsa-devel@alsa-project.org, nicoleotsuka@gmail.com
Cc: niranjan Patil <Niranjan.Patil@infocus.com>,
	markus.lindroth@limesaudio.com,
	richard Jiang <Richard.Jiang@infocus.com>
Subject: About iMX6SL sign extension of SSI Receive Configuration Register (SSIx_SRCR)
Date: Mon, 09 Mar 2015 17:09:34 +0800	[thread overview]
Message-ID: <54FD634E.8040007@gmail.com> (raw)

Hi Nicolin and community,

iMX6SL reference manual section "48.9.8 SSI Receive Configuration 
Register (SSIx_SRCR)" says about sign extension.

Below is a quote from iMX6SL reference manual:
-------------------------------------------------------------
Receive Data Extension. This control bit allows SSI to store the 
received data word in sign extended form.
This bit affects data storage only in case received data is LSB aligned 
(SRCR[9]=1)

0 OFF — Sign extension turned off.
1 ON — Sign extension turned on.
-------------------------------------------------------------

After I receive data (in the format of S16_LE) from SSI/I2S, I got data 
like 0x7FFF or 0x77d2. Are they supposed to be 0xFFFF or 0xF7d2?

After setting bit 10 (RXEXT) of SSIx_SRCR, I still get 0x7FFF or 0x77d2.
-- Note: SRCR[9] is 1.

Any suggestions? Thanks.

-- 
Xuebing
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

             reply	other threads:[~2015-03-09  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09  9:09 Xuebing Wang [this message]
2015-03-10  2:33 ` About iMX6SL sign extension of SSI Receive Configuration Register (SSIx_SRCR) Nicolin Chen

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=54FD634E.8040007@gmail.com \
    --to=xbing6@gmail.com \
    --cc=Niranjan.Patil@infocus.com \
    --cc=Richard.Jiang@infocus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=markus.lindroth@limesaudio.com \
    --cc=nicoleotsuka@gmail.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.