[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87k2bbyyir.wl-kuninori.morimoto.gx@renesas.com>
Date: Thu, 8 Dec 2016 01:57:38 +0000
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Rob Herring <robh@...nel.org>
CC: Mark Brown <broonie@...nel.org>,
Linux-ALSA <alsa-devel@...a-project.org>,
Liam Girdwood <lgirdwood@...il.com>,
Simon <horms@...ge.net.au>,
Laurent <laurent.pinchart@...asonboard.com>,
Guennadi <g.liakhovetski@....de>,
"Grant Likely" <grant.likely@...aro.org>,
Frank Rowand <frowand.list@...il.com>,
Linux-DT <devicetree@...r.kernel.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 01/14] Documentation: of: add type property
Hi Rob
> > From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
> >
> > OF graph indicates each devices connection. But it doesn't support type
> > of each port. For example HDMI case, it has video port and sound port
> > in one device node.
> > In this case, current driver can't handle each port correctly.
> > This patch enables to use type property on OF graph.
>
> I still don't think this is necessary. Simply define which port number
> is which for each HDMI chip.
>
> If this is necessary, then the types, video and sound, are too generic.
About this, if OF-graph can have "query" function to each port,
I can remove this "type" property from DT, and driver can answer
each port feature.
But is this OK approach ?
Best regards
---
Kuninori Morimoto
Powered by blists - more mailing lists