LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] pinctrl: uniphier: add LD20 MPEG2-TS I/O pin-mux settings
Date: Wed, 2 May 2018 14:16:59 +0200 [thread overview]
Message-ID: <CACRpkdZUypgGfgWMOy_Vjcu_djRhX1Ue8ReLUNeJ2BQ4LSfF6w@mail.gmail.com> (raw)
In-Reply-To: <20180427014905.19520-1-suzuki.katsuhiro@socionext.com>
On Fri, Apr 27, 2018 at 3:49 AM, Katsuhiro Suzuki
<suzuki.katsuhiro@socionext.com> wrote:
> The MPEG2-TS input/output core both accepts serial TS and parallel TS.
>
> The serial TS interface uses following pins:
> hscin0_s : HS0DOUT[0-3]
> hscin1_s : HS0DOUT[4-7]
> hscin2_s : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN0
> hscin3_s : HS1DIN[2-5]
> hscout0_s: HS0DOUT[0-3]
> hscout1_s: HS0DOUT[4-7]
>
> And the parallel TS interface uses following pins:
> hscin0_p : HS0BCLKIN, HS0SYNCIN, HS0VALIN, HS0DIN[0-7]
> hscin1_p : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN[0-7]
> hscout0_p: HS0BCLKOUT, HS0SYNCOUT, HS0VALOUT, HS0DOUT[0-7]
>
> Signed-off-by: Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com>
> Changes in v2:
This v2 version applied with Masahiro's ACK.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-05-02 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 1:49 Katsuhiro Suzuki
2018-04-27 1:49 ` [PATCH v2 2/2] pinctrl: uniphier: add LD11 " Katsuhiro Suzuki
2018-04-27 3:11 ` Masahiro Yamada
2018-05-02 12:18 ` Linus Walleij
2018-04-27 3:11 ` [PATCH v2 1/2] pinctrl: uniphier: add LD20 " Masahiro Yamada
2018-05-02 12:16 ` Linus Walleij [this message]
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=CACRpkdZUypgGfgWMOy_Vjcu_djRhX1Ue8ReLUNeJ2BQ4LSfF6w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=suzuki.katsuhiro@socionext.com \
--cc=yamada.masahiro@socionext.com \
--subject='Re: [PATCH v2 1/2] pinctrl: uniphier: add LD20 MPEG2-TS I/O pin-mux settings' \
/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
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).