From: Kuogee Hsieh <quic_khsieh@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
<linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>
Subject: Re: [RFC PATCH v2 4/5] drm/msm/dp: replace dp_connector with drm_bridge_connector
Date: Wed, 23 Feb 2022 16:40:56 -0800 [thread overview]
Message-ID: <552d9809-0499-23b5-e437-a77c893b96c2@quicinc.com> (raw)
In-Reply-To: <CAE-0n50VWH9Mum_W9e+6X1vjxvS3KWDqBtPfKHL-weA7S+_3Hg@mail.gmail.com>
On 2/23/2022 1:33 PM, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2022-02-23 10:27:26)
>> On 2/23/2022 10:22 AM, Dmitry Baryshkov wrote:
>>> On 23/02/2022 20:21, Kuogee Hsieh wrote:
>>>
>>> In the panel device node.
>>>
>>> Can you please share it too?
>>
>> &soc {
>> edp_power_supply: edp_power {
>> compatible = "regulator-fixed";
>> regulator-name = "edp_backlight_power";
>>
>> regulator-always-on;
>> regulator-boot-on;
>> };
>>
>> edp_backlight: edp_backlight {
>> compatible = "pwm-backlight";
>>
>> pwms = <&pm8350c_pwm 3 65535>;
>> power-supply = <&edp_power_supply>;
>> enable-gpio = <&pm8350c_gpios 7 GPIO_ACTIVE_HIGH>;
>>
>> pinctrl-names = "default";
>> pinctrl-0 = <&backlight_pwm_default>;
>> };
>>
>> edp_panel: edp_panel {
>> compatible = "sharp_lq140m1jw46";
> Is that supposed to be sharp,lq140m1jw46 with a comma instead of an
> underscore?
Stephen,
This is our internal branch which does not have patches up to date yet.
I will cherry-pick newer edp related patches which are under review now
to re test it.
next prev parent reply other threads:[~2022-02-24 0:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 22:40 [RFC PATCH v2 0/5] Simplify and correct msm/dp bridge implementation Dmitry Baryshkov
2022-02-11 22:40 ` [RFC PATCH v2 1/5] drm/msm/dp: fix panel bridge attachment Dmitry Baryshkov
2022-02-18 21:14 ` Kuogee Hsieh
2022-02-18 23:56 ` Stephen Boyd
2022-02-19 2:26 ` Dmitry Baryshkov
2022-02-24 18:25 ` [Freedreno] " Abhinav Kumar
2022-02-24 20:41 ` Dmitry Baryshkov
2022-02-25 2:01 ` Abhinav Kumar
2022-02-25 4:22 ` Dmitry Baryshkov
2022-02-25 4:45 ` Abhinav Kumar
2022-02-25 9:04 ` Dmitry Baryshkov
2022-02-25 17:11 ` Abhinav Kumar
2022-02-25 17:25 ` Dmitry Baryshkov
2022-02-11 22:40 ` [RFC PATCH v2 2/5] drm/msm/dp: support attaching bridges to the DP encoder Dmitry Baryshkov
2022-02-18 21:28 ` Kuogee Hsieh
2022-02-18 21:31 ` Dmitry Baryshkov
2022-02-18 23:38 ` Stephen Boyd
2022-02-23 17:47 ` Kuogee Hsieh
2022-02-24 19:56 ` Abhinav Kumar
2022-02-11 22:40 ` [RFC PATCH v2 3/5] drm/msm/dp: support finding next bridge even for DP interfaces Dmitry Baryshkov
2022-02-18 21:29 ` Kuogee Hsieh
2022-02-19 0:34 ` Stephen Boyd
2022-02-24 20:13 ` Abhinav Kumar
2022-02-24 20:49 ` Dmitry Baryshkov
2022-02-24 21:09 ` Abhinav Kumar
2022-02-11 22:40 ` [RFC PATCH v2 4/5] drm/msm/dp: replace dp_connector with drm_bridge_connector Dmitry Baryshkov
2022-02-18 21:31 ` Kuogee Hsieh
2022-02-18 21:52 ` Dmitry Baryshkov
2022-02-18 22:32 ` Dmitry Baryshkov
2022-02-19 0:55 ` Stephen Boyd
2022-02-19 2:22 ` Dmitry Baryshkov
2022-02-23 17:21 ` Kuogee Hsieh
2022-02-23 18:22 ` Dmitry Baryshkov
2022-02-23 18:27 ` Kuogee Hsieh
2022-02-23 18:45 ` Dmitry Baryshkov
2022-02-23 21:33 ` Stephen Boyd
2022-02-24 0:40 ` Kuogee Hsieh [this message]
[not found] ` <64a5ae1a-df65-b0a5-5d0d-cfb1d4da3bf7@quicinc.com>
2022-03-16 16:45 ` Sankeerth Billakanti (QUIC)
2022-04-14 20:17 ` Abhinav Kumar
2022-02-11 22:40 ` [RFC PATCH v2 5/5] drm/msm/dp: remove extra wrappers and public functions Dmitry Baryshkov
[not found] ` <26549f55-6195-a7ec-5896-de5f986ad716@quicinc.com>
2022-03-16 16:31 ` Sankeerth Billakanti (QUIC)
2022-04-14 20:17 ` Abhinav Kumar
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=552d9809-0499-23b5-e437-a77c893b96c2@quicinc.com \
--to=quic_khsieh@quicinc.com \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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