linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Baluta (OSS)" <daniel.baluta@oss.nxp.com>
To: "broonie@kernel.org" <broonie@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "festevam@gmail.com" <festevam@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"pierre-louis.bossart@linux.intel.com"
	<pierre-louis.bossart@linux.intel.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/4] Add a better separation between i.MX8 families
Date: Tue, 28 Jan 2020 08:06:07 +0000	[thread overview]
Message-ID: <20200128080518.29970-1-daniel.baluta@oss.nxp.com> (raw)

From: Daniel Baluta <daniel.baluta@nxp.com>

So far the implementation was designed to support  a generic platform
named i.MX8. Anyhow, now working with specific i.MX8 instances we need
to account for the differences.

i.MX8 naming can be confusing at the first glance, so we need to have
a clean separation between different platforms.

Here is the split of i.MX8 per platforms. Notice that i.MX8 names
the entire family, but also a sub-family.

imx8
├── imx8
│   └── imx8qm (*)
├── imx8m
│   ├── imx8mm
│   ├── imx8mn
│   ├── imx8mp (*)
│   └── imx8mq
└── imx8x
    └── imx8qxp (*)

Platforms marked with (*) contain a DSP. In the future there might be
more platforms.

This patchseries does the following:
	* renames imx8 to imx8x (because the only supported platform now
        is imx8qxp).
        * adds support for imx8 (which is imx8qm)

A future patchset will add supprot for i.MX8MP.

Paul Olaru (4):
  ASoC: SOF: Rename i.MX8 platform to i.MX8X
  ASoC: SOF: imx8: Add ops for i.MX8QM
  ASoC: SOF: Add i.MX8QM device descriptor
  dt-bindings: dsp: fsl: Add fsl,imx8qm-dsp entry

 .../devicetree/bindings/dsp/fsl,dsp.yaml      |  1 +
 sound/soc/sof/imx/imx8.c                      | 57 ++++++++++++++++++-
 sound/soc/sof/sof-of-dev.c                    | 10 ++++
 3 files changed, 65 insertions(+), 3 deletions(-)

-- 
2.17.1

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-01-28  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  8:06 Daniel Baluta (OSS) [this message]
2020-01-28  8:06 ` [PATCH 1/4] ASoC: SOF: Rename i.MX8 platform to i.MX8X Daniel Baluta (OSS)
2020-01-28  8:06 ` [PATCH 2/4] ASoC: SOF: imx8: Add ops for i.MX8QM Daniel Baluta (OSS)
2020-01-28  8:06 ` [PATCH 3/4] ASoC: SOF: Add i.MX8QM device descriptor Daniel Baluta (OSS)
2020-01-28  8:06 ` [PATCH 4/4] dt-bindings: dsp: fsl: Add fsl,imx8qm-dsp entry Daniel Baluta (OSS)
2020-01-28 16:08 ` [PATCH 0/4] Add a better separation between i.MX8 families Pierre-Louis Bossart

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=20200128080518.29970-1-daniel.baluta@oss.nxp.com \
    --to=daniel.baluta@oss.nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=robh+dt@kernel.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).