From: "\"Stéphane Viau\"" <sviau@codeaurora.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] drm/msm/hdmi: Use pinctrl in HDMI driver
Date: Tue, 2 Jun 2015 10:12:59 -0500 [thread overview]
Message-ID: <ceda7fbb98cf30c5b60bc54ead29fd80.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1433228366.6844.18.camel@mm-sol.com>
Hi Ivan,
>
> Hi Stephane,
>
> On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
>> Some targets (eg: msm8994) use the pinctrl framework to configure
>> interface pins. This change adds support for initialization and
>> pinctrl active/sleep state control for the HDMI driver.
>>
>> Signed-off-by: Stephane Viau <sviau@codeaurora.org>
>> ---
>> v2:
>> - Add devicetree binding documentation for pinctrl property [Ivan]
>> - Use pinctrl framework's PINCTRL_STATE_DEFAULT/SLEEP states [Ivan]
>>
>
> <snip>
>
>>
>> static int hdmi_bind(struct device *dev, struct device *master, void
>> *data)
>> @@ -365,6 +379,7 @@ static int hdmi_bind(struct device *dev, struct
>> device *master, void *data)
>> #ifdef CONFIG_OF
>> struct device_node *of_node = dev->of_node;
>> const struct of_device_id *match;
>> + struct pinctrl *pinctrl;
>>
>> match = of_match_node(dt_match, of_node);
>> if (match && match->data) {
>> @@ -383,6 +398,18 @@ static int hdmi_bind(struct device *dev, struct
>> device *master, void *data)
>> hdmi_cfg->mux_sel_gpio = get_gpio(dev, of_node,
>> "qcom,hdmi-tx-mux-sel");
>> hdmi_cfg->mux_lpm_gpio = get_gpio(dev, of_node,
>> "qcom,hdmi-tx-mux-lpm");
>>
>> + /* not all targets have pinctrl, do not fail in case of error:
>> */
>> + pinctrl = devm_pinctrl_get(dev);
>
> Probably I have to be more explicit. Why not using pins binding handled in
> driver
> really_probe()? I have to admit that I am not familiar with DRM subsystem.
This would work, indeed, for default/sleep/idle states.
I actually had in mind that we'd need to keep track of HDMI pinctrl states
because we may need to add a couple more in the near future in order to
independently enable/disable certain parts of the HDMI controller (eg:
HPD, DDC, CEC..).
Each of this HW sub-sections of the controller are driven by a different
"pin" in the downstream driver... But since this is nowhere close to being
upstream-ed yet, I'll go ahead with your idea of using the common pins
binding (v3 to follow).
Thanks,
Stephane.
>
> Regards,
> Ivan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "\"Stéphane Viau\"" <sviau@codeaurora.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: "Stephane Viau" <sviau@codeaurora.org>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robdclark@gmail.com
Subject: Re: [PATCH v2] drm/msm/hdmi: Use pinctrl in HDMI driver
Date: Tue, 2 Jun 2015 10:12:59 -0500 [thread overview]
Message-ID: <ceda7fbb98cf30c5b60bc54ead29fd80.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1433228366.6844.18.camel@mm-sol.com>
Hi Ivan,
>
> Hi Stephane,
>
> On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
>> Some targets (eg: msm8994) use the pinctrl framework to configure
>> interface pins. This change adds support for initialization and
>> pinctrl active/sleep state control for the HDMI driver.
>>
>> Signed-off-by: Stephane Viau <sviau@codeaurora.org>
>> ---
>> v2:
>> - Add devicetree binding documentation for pinctrl property [Ivan]
>> - Use pinctrl framework's PINCTRL_STATE_DEFAULT/SLEEP states [Ivan]
>>
>
> <snip>
>
>>
>> static int hdmi_bind(struct device *dev, struct device *master, void
>> *data)
>> @@ -365,6 +379,7 @@ static int hdmi_bind(struct device *dev, struct
>> device *master, void *data)
>> #ifdef CONFIG_OF
>> struct device_node *of_node = dev->of_node;
>> const struct of_device_id *match;
>> + struct pinctrl *pinctrl;
>>
>> match = of_match_node(dt_match, of_node);
>> if (match && match->data) {
>> @@ -383,6 +398,18 @@ static int hdmi_bind(struct device *dev, struct
>> device *master, void *data)
>> hdmi_cfg->mux_sel_gpio = get_gpio(dev, of_node,
>> "qcom,hdmi-tx-mux-sel");
>> hdmi_cfg->mux_lpm_gpio = get_gpio(dev, of_node,
>> "qcom,hdmi-tx-mux-lpm");
>>
>> + /* not all targets have pinctrl, do not fail in case of error:
>> */
>> + pinctrl = devm_pinctrl_get(dev);
>
> Probably I have to be more explicit. Why not using pins binding handled in
> driver
> really_probe()? I have to admit that I am not familiar with DRM subsystem.
This would work, indeed, for default/sleep/idle states.
I actually had in mind that we'd need to keep track of HDMI pinctrl states
because we may need to add a couple more in the near future in order to
independently enable/disable certain parts of the HDMI controller (eg:
HPD, DDC, CEC..).
Each of this HW sub-sections of the controller are driven by a different
"pin" in the downstream driver... But since this is nowhere close to being
upstream-ed yet, I'll go ahead with your idea of using the common pins
binding (v3 to follow).
Thanks,
Stephane.
>
> Regards,
> Ivan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-06-02 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 20:28 [PATCH v2] drm/msm/hdmi: Use pinctrl in HDMI driver Stephane Viau
2015-06-02 6:59 ` Ivan T. Ivanov
2015-06-02 15:12 ` "Stéphane Viau" [this message]
2015-06-02 15:12 ` "Stéphane Viau"
2015-06-02 15:25 ` Ivan T. Ivanov
2015-06-02 15:42 ` "Stéphane Viau"
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=ceda7fbb98cf30c5b60bc54ead29fd80.squirrel@www.codeaurora.org \
--to=sviau@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-msm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.