From: Jose.Abreu@synopsys.com (Jose Abreu)
To: linus-amlogic@lists.infradead.org
Subject: [RFC/RFT PATCH 2/4] drm/bridge: dw-hdmi: Add support for custom PHY handling
Date: Thu, 19 Jan 2017 14:20:25 +0000 [thread overview]
Message-ID: <5ed16196-4666-d9af-cc5b-51d1a5cebec5@synopsys.com> (raw)
In-Reply-To: <5efc1cc1-05e4-b763-9b1a-db0859988e7b@baylibre.com>
Hi Neil,
On 18-01-2017 11:20, Neil Armstrong wrote:
>
> It's the idea we discussed with Laurent.
> Keeping the Synopsys PHY code inside the dw-hdmi driver would be simpler.
>
> But don't you think adding a proper "ops" structure apart from the plat_data
> should be necessary ?
>
> Neil
>
An "ops" structure seems fine by me :) We could have one for the
generic phy's (the ones that dw-hdmi already supports) and let
the developer specify other one if needed.
Best regards,
Jose Miguel Abreu
next prev parent reply other threads:[~2017-01-19 14:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:31 [RFC/RFT PATCH 0/4] drm/bridge: dw-hdmi: Add support for Custom PHYs Neil Armstrong
2017-01-17 12:31 ` [RFC/RFT PATCH 1/4] drm/bridge: dw-hdmi: Switch to regmap for register access Neil Armstrong
2017-01-17 14:39 ` Laurent Pinchart
2017-01-20 15:12 ` Neil Armstrong
2017-01-17 12:31 ` [RFC/RFT PATCH 2/4] drm/bridge: dw-hdmi: Add support for custom PHY handling Neil Armstrong
2017-01-17 14:54 ` Laurent Pinchart
2017-01-18 10:40 ` Jose Abreu
2017-01-18 11:20 ` Neil Armstrong
2017-01-19 14:20 ` Jose Abreu [this message]
2017-01-17 12:31 ` [RFC/RFT PATCH 3/4] drm/bridge: dw-hdmi: Enable CSC even for DVI Neil Armstrong
2017-01-17 14:40 ` Laurent Pinchart
2017-01-18 10:22 ` Jose Abreu
2017-01-18 11:15 ` Neil Armstrong
2017-01-17 12:31 ` [RFC/RFT PATCH 4/4] drm/bridge: dw-hdmi: Take input format from plat_data Neil Armstrong
2017-01-17 14:48 ` Laurent Pinchart
2017-01-18 10:28 ` Jose Abreu
2017-01-18 11:24 ` Neil Armstrong
2017-01-18 20:49 ` Laurent Pinchart
2017-01-19 15:21 ` Jose Abreu
2017-01-19 15:30 ` Hans Verkuil
2017-01-19 16:45 ` Laurent Pinchart
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=5ed16196-4666-d9af-cc5b-51d1a5cebec5@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®