From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: alsa-devel@alsa-project.org, peter.ujfalusi@ti.com,
devicetree@vger.kernel.org, tomi.valkeinen@ti.com,
arnaud.pouliquen@st.com, dri-devel@lists.freedesktop.org,
liam.r.girdwood@linux.intel.com, tony@atomide.com,
broonie@kernel.org, bcousson@baylibre.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH RFC v5 4/8] drm/i2c: tda998x: Add support of a DT graph of ports
Date: Thu, 18 Feb 2016 15:32:03 +0000 [thread overview]
Message-ID: <20160218153203.GL5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160218161823.fc54c61bd0c5cee75ab59578@free.fr>
On Thu, Feb 18, 2016 at 04:18:23PM +0100, Jean-Francois Moine wrote:
> On Thu, 18 Feb 2016 08:35:30 -0600
> Rob Herring <robh@kernel.org> wrote:
>
> > On Wed, Feb 17, 2016 at 04:49:05PM +0200, Jyri Sarha wrote:
> > > From: Jean-Francois Moine <moinejf@free.fr>
> > >
> > > Two kinds of ports may be declared in a DT graph of ports: video and audio.
> > > This patch accepts the port value from a video port as an alternative
> > > to the video-ports property.
> > > It also accepts audio ports in the case the transmitter is not used as
> > > a slave encoder.
> > > The new file include/sound/tda998x.h prepares to the definition of
> > > a tda998x CODEC.
> > >
> > > Signed-off-by: Jean-Francois Moine <moinejf@free.fr>
> > > Signed-off-by: Jyri Sarha <jsarha@ti.com>
> > > ---
> > > .../devicetree/bindings/display/bridge/tda998x.txt | 51 ++++++++++++
> > > drivers/gpu/drm/i2c/tda998x_drv.c | 90 +++++++++++++++++++---
> > > include/sound/tda998x.h | 8 ++
> > > 3 files changed, 140 insertions(+), 9 deletions(-)
> > > create mode 100644 include/sound/tda998x.h
> > >
> > > diff --git a/Documentation/devicetree/bindings/display/bridge/tda998x.txt b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> > > index e9e4bce..35f6a80 100644
> > > --- a/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> > > +++ b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> > > @@ -16,6 +16,35 @@ Optional properties:
> > >
> > > - video-ports: 24 bits value which defines how the video controller
> > > output is wired to the TDA998x input - default: <0x230145>
> > > + This property is not used when ports are defined.
> > > +
> > > +Optional nodes:
> > > +
> > > + - port: up to three ports.
> > > + The ports are defined according to [1].
> > > +
> > > + Video port.
> > > + There may be only one video port.
> > > + This one must contain the following property:
> > > +
> > > + - port-type: must be "rgb"
> >
> > This should be implied from the port unit address. In other words,
> > port@0 is defined to be the rgb port. Now, if this is one of several
> > modes for the video port, then that is a different story.
> >
> > > + and may contain the optional property:
> > > +
> > > + - reg: 24 bits value which defines how the video controller
> > > + output is wired to the TDA998x input (video pins)
> > > + When absent, the default value is <0x230145>.
> >
> > This is not really how reg is intended to be used. Can you explain how
> > this value is determined?
> >
> > > + Audio ports.
> > > + There may be one or two audio ports.
> > > + These ones must contain the following properties:
> > > +
> > > + - port-type: must be "i2s" or "spdif"
> > > +
> > > + - reg: 8 bits value which defines how the audio controller
> > > + output is wired to the TDA998x input (audio pins)
> >
> > Same here.
>
> Hi Rob,
>
> These audio/video port definitions were discussed in the thread
> http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/095836.html
> but, you are right, and as you already said in the thread
> https://lists.freedesktop.org/archives/dri-devel/2015-September/090544.html
> 'reg' should not be used here.
However, ePAPR requires that a node name with @n also have a reg property
with the same n value. See ePAPR 2.2.1.1. This statement in it seems
to be particularly clear on this subject:
"The unit-address must match the first address specified in the reg
property of the node. If the node has no reg property, the @ and
unit-address must be omitted and the node-name alone differentiates
the node from other nodes at the same level in the tree."
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-18 15:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 14:49 [PATCH RFC v5 0/8] Implement generic ASoC HDMI codec and use it in tda998x Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 1/8] ALSA: pcm: add IEC958 channel status helper for hw_params Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 2/8] ASoC: hdmi-codec: Add hdmi-codec for external HDMI-encoders Jyri Sarha
2016-02-22 14:22 ` Arnaud Pouliquen
2016-03-08 16:59 ` Arnaud Pouliquen
[not found] ` <cover.1455720381.git.jsarha-l0cyMroinI0@public.gmane.org>
2016-02-17 14:49 ` [PATCH RFC v5 3/8] ASoC: hdmi-codec: Add audio abort() callback for video side to use Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 4/8] drm/i2c: tda998x: Add support of a DT graph of ports Jyri Sarha
[not found] ` <842e221030a0b14bc862790eb2f5bc97bb29c012.1455720381.git.jsarha-l0cyMroinI0@public.gmane.org>
2016-02-18 14:35 ` Rob Herring
2016-02-18 15:18 ` Jean-Francois Moine
2016-02-18 15:32 ` Russell King - ARM Linux [this message]
2016-02-25 13:42 ` Jyri Sarha
[not found] ` <56CF04DA.8080905-l0cyMroinI0@public.gmane.org>
2016-02-26 0:43 ` Russell King - ARM Linux
2016-02-26 10:14 ` Jyri Sarha
2016-02-26 11:21 ` Russell King - ARM Linux
2016-02-29 10:36 ` Jyri Sarha
2016-03-01 14:26 ` Alternative binding proposal for tda998x audio (Was: Re: [PATCH RFC v5 4/8] drm/i2c: tda998x: Add support of a DT graph of ports) Jyri Sarha
2016-03-01 15:35 ` Jean-Francois Moine
2016-03-01 15:51 ` Jyri Sarha
2016-03-01 16:16 ` Jean-Francois Moine
2016-03-01 18:29 ` Jyri Sarha
[not found] ` <56D5DF7D.7090608-l0cyMroinI0@public.gmane.org>
2016-03-01 19:26 ` Jean-Francois Moine
2016-03-02 8:34 ` Jyri Sarha
[not found] ` <20160301171630.630a47dc00060645f89bb8ab-GANU6spQydw@public.gmane.org>
2016-03-02 4:29 ` Mark Brown
2016-02-17 14:49 ` [PATCH RFC v5 5/8] drm/i2c: tda998x: Remove include/sound/tda998x.h and fix graph parsing Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 6/8] drm/i2c: tda998x: Improve tda998x_configure_audio() audio related pdata Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 7/8] drm/i2c: tda998x: Register ASoC HDMI codec for audio functionality Jyri Sarha
2016-02-17 14:49 ` [PATCH RFC v5 8/8] ARM: dts: am335x-boneblack: Add HDMI audio support Jyri Sarha
2016-02-17 19:36 ` Robert Nelson
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=20160218153203.GL5783@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-omap@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/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).