From: Neil Armstrong <narmstrong@baylibre.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
dri-devel@lists.freedesktop.org,
laurent.pinchart+renesas@ideasonboard.com
Cc: linux-amlogic@lists.infradead.org,
kieran.bingham@ideasonboard.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC/RFT PATCH 2/4] drm/bridge: dw-hdmi: Add support for custom PHY handling
Date: Wed, 18 Jan 2017 12:20:43 +0100 [thread overview]
Message-ID: <5efc1cc1-05e4-b763-9b1a-db0859988e7b@baylibre.com> (raw)
In-Reply-To: <88d1f45a-bfd2-2e6b-6c23-2d0686faa2ce@synopsys.com>
Hi Jose,
On 01/18/2017 11:40 AM, Jose Abreu wrote:
> Hi Neil,
>
>
> On 17-01-2017 12:31, Neil Armstrong wrote:
>> @@ -1434,9 +1434,18 @@ static int dw_hdmi_setup(struct dw_hdmi *hdmi, struct drm_display_mode *mode)
>> hdmi_av_composer(hdmi, mode);
>>
>> /* HDMI Initializateion Step B.2 */
>> - ret = dw_hdmi_phy_init(hdmi);
>> - if (ret)
>> - return ret;
>> + if (hdmi->plat_data->hdmi_phy_init) {
>> + ret = hdmi->plat_data->hdmi_phy_init(hdmi, hdmi->plat_data,
>> @@ -1551,7 +1560,11 @@ static void dw_hdmi_poweron(struct dw_hdmi *hdmi)
>>
>> static void dw_hdmi_poweroff(struct dw_hdmi *hdmi)
>> {
>> - dw_hdmi_phy_disable(hdmi);
>> + if (hdmi->phy_enabled && hdmi->plat_data->hdmi_phy_disable) {
>> + hdmi->plat_data->hdmi_phy_disable(hdmi, hdmi->plat_data);
>> + hdmi->phy_enabled = false;
>> + } else
>> + dw_hdmi_phy_disable(hdmi);
>> hdmi->bridge_is_on = false;
>> }
>>
>> @@ -1921,7 +1962,9 @@ static int dw_hdmi_detect_phy(struct dw_hdmi *hdmi)
>> return -ENODEV;
>> }
>>
>> - if (!hdmi->phy->configure && !hdmi->plat_data->configure_phy) {
>> + if (!hdmi->phy->configure &&
>> + !hdmi->plat_data->configure_phy &&
>> + !hdmi->plat_data->hdmi_phy_init) {
>> dev_err(hdmi->dev, "%s requires platform support\n",
>> hdmi->phy->name);
>> return -ENODEV;
>> @@ -2119,9 +2164,10 @@ static int dw_hdmi_detect_phy(struct dw_hdmi *hdmi)
>> + if (!hdmi->plat_data || !hdmi->plat_data->hdmi_read_hpd)
>> + /* Unmute interrupts */
>> + hdmi_writeb(hdmi, ~(HDMI_IH_PHY_STAT0_HPD | HDMI_IH_PHY_STAT0_RX_SENSE),
>> + HDMI_IH_MUTE_PHY_STAT0);
>>
>>
>
> [sniped some parts of the patch]
>
> I personally don't like this kind of 'if plat_data ... else ...'
> Can't we just abstract all of the phy configuration (for a
> Synopsys Phy) to a new file and then pass it always in pdata as
> default? Then overwrite it with custom one if needed. Much like
> what you did with the regmap. Or even leave it in dw-hdmi.c but
> have a generic pdata structure with generic phy init/disable
> functions.
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
>
> Best regards,
> Jose Miguel Abreu
>
next prev parent reply other threads:[~2017-01-18 11: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 [this message]
2017-01-19 14:20 ` Jose Abreu
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=5efc1cc1-05e4-b763-9b1a-db0859988e7b@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=Jose.Abreu@synopsys.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).