Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1646680 > unrolled thread

Re: [RFC 0/2] Synopsys Designware HDMI Video Capture Controller + PHY

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [RFC 0/2] Synopsys Designware HDMI Video Capture Controller + PHY Jose Abreu <Jose.Abreu@synopsys.com> - 2017-05-22 11:50 +0200

#1646680 — Re: [RFC 0/2] Synopsys Designware HDMI Video Capture Controller + PHY

Hi Hans,


On 21-04-2017 10:53, Jose Abreu wrote:
> Hi All,
>
> This is a RFC series that is intended to collect comments regarding the
> Synopsys Designware HDMI RX controller and Synopsys Designware HDMI RX e405 PHY
> drivers.
>
> The Synopsys Designware HDMI RX controller is an HDMI receiver controller that
> is responsible to process digital data that comes from a phy. The final result
> is a stream of raw video data that can then be connected to a video DMA, for
> example, and transfered into RAM so that it can be displayed.
>
> The controller + phy available in this series natively support all HDMI 1.4 and
> HDMI 2.0 modes, including deep color. Although, the driver is quite in its
> initial stage and unfortunatelly only non deep color modes are supported. Also,
> audio is not yet supported in the driver (the controller has several audio
> output interfaces).
>
> Feel free to take a look at this series and please leave a comment! I can
> expand a little bit more about design decisions and would like to know wether
> these were the best choices.
>
> With best regards,
> Jose Miguel Abreu
>
> Jose Abreu (2):
>   [media] platform: Add Synopsys Designware HDMI RX PHY e405 Driver
>   [media] platform: Add Synopsys Designware HDMI RX Controller Driver
>
> Cc: Carlos Palminha <palminha@synopsys.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Hans Verkuil <hans.verkuil@cisco.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-media@vger.kernel.org
>
>  drivers/media/platform/Kconfig                |    2 +
>  drivers/media/platform/Makefile               |    2 +
>  drivers/media/platform/dwc/Kconfig            |   17 +
>  drivers/media/platform/dwc/Makefile           |    2 +
>  drivers/media/platform/dwc/dw-hdmi-phy-e405.c |  879 ++++++++++++++++
>  drivers/media/platform/dwc/dw-hdmi-phy-e405.h |   63 ++
>  drivers/media/platform/dwc/dw-hdmi-rx.c       | 1396 +++++++++++++++++++++++++
>  drivers/media/platform/dwc/dw-hdmi-rx.h       |  313 ++++++
>  include/media/dwc/dw-hdmi-phy-pdata.h         |   64 ++
>  include/media/dwc/dw-hdmi-rx-pdata.h          |   50 +
>  10 files changed, 2788 insertions(+)
>  create mode 100644 drivers/media/platform/dwc/Kconfig
>  create mode 100644 drivers/media/platform/dwc/Makefile
>  create mode 100644 drivers/media/platform/dwc/dw-hdmi-phy-e405.c
>  create mode 100644 drivers/media/platform/dwc/dw-hdmi-phy-e405.h
>  create mode 100644 drivers/media/platform/dwc/dw-hdmi-rx.c
>  create mode 100644 drivers/media/platform/dwc/dw-hdmi-rx.h
>  create mode 100644 include/media/dwc/dw-hdmi-phy-pdata.h
>  create mode 100644 include/media/dwc/dw-hdmi-rx-pdata.h
>

Sorry for pinging but could you review this rfc series? This is
not for the controller I mentioned a while ago, its for a
different one which I had a few free time to make a driver.
Though, the behavior and phy interface is similar, and the phy
driver used is the same also.

Best regards,
Jose Miguel Abreu

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web