From: Masahiro Yamada <masahiroy@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu@linaro.org>
Cc: Rob Herring <robh@kernel.org>, DTML <devicetree@vger.kernel.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] arm64: dts: uniphier: Add support for Akebi96
Date: Mon, 20 Apr 2020 20:41:53 +0900 [thread overview]
Message-ID: <CAK7LNATJy=J-GLJL7O5oaMWk5C46ATmxL6FgorNwn+541=HeFg@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQtTPLdKN8cz842gvoS36GVQvk2ztahGp8XWoW3C8BzQg@mail.gmail.com>
Hiramatsu-san,
On Mon, Apr 20, 2020 at 8:15 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> On Mon, Apr 20, 2020 at 7:08 PM Masami Hiramatsu
> <masami.hiramatsu@linaro.org> wrote:
> >
> > Add the device tree for Akebi96. Akebi96 is a 96boards certified
> > development board based on UniPhir LD20.
> > ( https://www.96boards.org/product/akebi96/ )
> >
> > This board has;
> > - MAX3421 USB-SPI chip on SPI port3 (for USB gadget port)
> > - Simple frame buffer with 1080p fixed resolution.
> > - I2S port which is connected to aout1b instead of aout1.
> > - 3 serial ports, only serial3 has CTS/RTS.
> > - No NAND, only eMMC on the board.
> > - OP-TEE support.
>
>
> Lastly, is the pin-setting "aout1", "aout1b" correct ?
I am not sure if I understood this code correctly, but
there are two ports "aout1" and "aout1b"
outputting the same audio, is this correct?
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2020-04-20 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <158737719165.27947.6617937231903079086.stgit@localhost>
2020-04-20 10:07 ` [PATCH v2 1/2] dt-bindings: arm: Add Akebi96 board support Masami Hiramatsu
2020-04-20 10:07 ` [PATCH v2 2/2] arm64: dts: uniphier: Add support for Akebi96 Masami Hiramatsu
2020-04-20 11:15 ` Masahiro Yamada
2020-04-20 11:41 ` Masahiro Yamada [this message]
2020-04-20 13:21 ` Masami Hiramatsu
2020-04-21 12:56 ` Masahiro Yamada
2020-04-22 2:19 ` Masami Hiramatsu
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='CAK7LNATJy=J-GLJL7O5oaMWk5C46ATmxL6FgorNwn+541=HeFg@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mhiramat@kernel.org \
--cc=robh@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).