[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200128080518.29970-1-daniel.baluta@oss.nxp.com>
Date: Tue, 28 Jan 2020 08:06:07 +0000
From: "Daniel Baluta (OSS)" <daniel.baluta@....nxp.com>
To: "broonie@...nel.org" <broonie@...nel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>
CC: "festevam@...il.com" <festevam@...il.com>,
dl-linux-imx <linux-imx@....com>,
"pierre-louis.bossart@...ux.intel.com"
<pierre-louis.bossart@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Daniel Baluta <daniel.baluta@....com>
Subject: [PATCH 0/4] Add a better separation between i.MX8 families
From: Daniel Baluta <daniel.baluta@....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
Powered by blists - more mailing lists