From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Fabio Estevam <festevam@gmail.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH 1/1] ARM: dts: imx6ul: add spdif node
Date: Thu, 03 Jun 2021 08:23:21 +0000 [thread overview]
Message-ID: <2e0c23355cbcd4aac46fa9f4c5b98732e9c98c29.camel@embedded.rocks> (raw)
In-Reply-To: <CAOMZO5BBBtLF=d-N6qJQ4tqtj2TkkUNY_u0bN9Jqmd7TPdud5Q@mail.gmail.com>
Hi Fabio,
yes, I am running it on a custom i.MX6ULL board:
```
imx-spdif sound-spdif: snd-soc-dummy-dai <-> 2004000.spdif mapping ok
```
Best regards
Jörg Krause
On Mon, 2021-05-31 at 18:32 -0300, Fabio Estevam wrote:
> Hi Jörg,
>
> On Mon, May 31, 2021 at 7:01 AM Jörg Krause <joerg.krause@embedded.rocks> wrote:
> >
> > The i.MX6UL has a SPDIF located at start address 0x02004000 in the
> > AIPS-1 memory region [1].
> >
> > SPDIF is also available on i.MX6ULL [2], so imx6ull.dtsi is fine.
> >
> > [1] i.MX 6UltraLite Applications Processor Reference Manual, Rev. 2,
> > 03/2017, Table-2-2 AIPS-1 memory map, p. 158
> > [2] i.MX 6ULL Applications Processor Reference Manual, Rev. 1,
> > 11/2017, Table-2-2 AIPS-1 memory map, p. 178
> >
> > Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks>
>
> The patch looks good.
>
> Did you have a chance to test this on your hardware?
>
> Thanks
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-03 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:01 [PATCH 1/1] ARM: dts: imx6ul: add spdif node Jörg Krause
2021-05-31 21:32 ` Fabio Estevam
2021-06-03 8:23 ` Jörg Krause [this message]
2021-06-12 7:21 ` Shawn Guo
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=2e0c23355cbcd4aac46fa9f4c5b98732e9c98c29.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).