devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@nxp.com>
To: broonie@kernel.org
Cc: l.stach@pengutronix.de, mihai.serban@gmail.com,
	alsa-devel@alsa-project.org, timur@kernel.org,
	shengjiu.wang@nxp.com, angus@akkea.ca, tiwai@suse.com,
	nicoleotsuka@gmail.com, linux-imx@nxp.com, kernel@pengutronix.de,
	festevam@gmail.com, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org,
	Daniel Baluta <daniel.baluta@nxp.com>
Subject: [PATCH v3 0/5] Add support for new SAI IP version
Date: Tue,  6 Aug 2019 18:12:09 +0300	[thread overview]
Message-ID: <20190806151214.6783-1-daniel.baluta@nxp.com> (raw)

So far SAI IPs integrated with imx6 only supported one data line.
Starting with imx7 and imx8 SAI integration support up to 8 data
lines. First patch introduce register definition to support this.

New SAI IP version introduces two new registers (Version and Parmeter
registers) which are placed at the beginning of register address space.
For this reason we need to fix the register's address. Support for
this is introduced in patch 3.

Changes since v2:
	- removed patches regarding data line mask because I need to
	find a better way to describe to model data lines. Perhaps,we
	only need to specify how many datalines a specific SAI instance
	supports and then let SAI driver to activate datalines based on
	the number of channels. Will open the discussion on this on a
	separate thread.
	- fixed devicetree documentation as per Nicolin comments and
	will send a separate patch to convert it to yaml.

Changes since v1:
        - removed patches from Lucas as they were already accepted
        - addressed comments from Lucas and Nicolin regarding
        device tree property naming
        - removed comment saying that "datalines" must be always
        consecutively enabled (this is not true, checked with IP owner)
        - added new patch to document newly introduced compatbile
          strings
        - removed patch introducing combined mode as I will still need
        some time to figure out how to properly allow users to set it.

Daniel Baluta (5):
  ASoC: fsl_sai: Add registers definition for multiple datalines
  ASoC: fsl_sai: Update Tx/Rx channel enable mask
  ASoC: fsl_sai: Add support for SAI new version
  ASoC: fsl_sai: Add support for imx7ulp/imx8mq
  ASoC: dt-bindings: Introduce compatible strings for 7ULP and 8MQ

 .../devicetree/bindings/sound/fsl-sai.txt     |   3 +-
 sound/soc/fsl/fsl_sai.c                       | 320 ++++++++++++------
 sound/soc/fsl/fsl_sai.h                       |  78 +++--
 3 files changed, 273 insertions(+), 128 deletions(-)

-- 
2.17.1

             reply	other threads:[~2019-08-06 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 15:12 Daniel Baluta [this message]
2019-08-06 15:12 ` [PATCH v3 1/5] ASoC: fsl_sai: Add registers definition for multiple datalines Daniel Baluta
2019-08-07  1:16   ` Nicolin Chen
2019-08-07 13:30   ` Applied "ASoC: fsl_sai: Add registers definition for multiple datalines" to the asoc tree Mark Brown
2019-08-06 15:12 ` [PATCH v3 2/5] ASoC: fsl_sai: Update Tx/Rx channel enable mask Daniel Baluta
2019-08-07  1:17   ` Nicolin Chen
2019-08-07 13:30   ` Applied "ASoC: fsl_sai: Update Tx/Rx channel enable mask" to the asoc tree Mark Brown
2019-08-06 15:12 ` [PATCH v3 3/5] ASoC: fsl_sai: Add support for SAI new version Daniel Baluta
2019-08-07  1:40   ` Nicolin Chen
2019-08-07 13:30   ` Applied "ASoC: fsl_sai: Add support for SAI new version" to the asoc tree Mark Brown
2019-08-06 15:12 ` [PATCH v3 4/5] ASoC: fsl_sai: Add support for imx7ulp/imx8mq Daniel Baluta
2019-08-07 13:30   ` Applied "ASoC: fsl_sai: Add support for imx7ulp/imx8mq" to the asoc tree Mark Brown
2019-08-06 15:12 ` [PATCH v3 5/5] ASoC: dt-bindings: Introduce compatible strings for 7ULP and 8MQ Daniel Baluta
2019-08-07  1:42   ` Nicolin Chen
2019-08-07 13:30   ` Applied "ASoC: dt-bindings: Introduce compatible strings for 7ULP and 8MQ" to the asoc tree 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=20190806151214.6783-1-daniel.baluta@nxp.com \
    --to=daniel.baluta@nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=angus@akkea.ca \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.serban@gmail.com \
    --cc=nicoleotsuka@gmail.com \
    --cc=robh@kernel.org \
    --cc=shengjiu.wang@nxp.com \
    --cc=timur@kernel.org \
    --cc=tiwai@suse.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 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).