From: Jitao Shi <jitao.shi@mediatek.com>
To: CK Hu <ck.hu@mediatek.com>
Cc: "Bibby Hsieh (謝濟遠)" <Bibby.Hsieh@mediatek.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
"David Airlie" <airlied@linux.ie>,
"stonea168@163.com" <stonea168@163.com>,
"Cawa Cheng (鄭曄禧)" <cawa.cheng@mediatek.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Sj Huang (黃信璋)" <sj.huang@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Yingjoe Chen (陳英洲)" <Yingjoe.Chen@mediatek.com>,
"Eddie Huang (黃智傑)" <eddie.huang@mediatek.com>
Subject: Re: [PATCH 1/4] dt-binds: display: mediatek: add property to control mipi tx drive current
Date: Tue, 25 Feb 2020 19:42:35 +0800 [thread overview]
Message-ID: <1582630955.13085.2.camel@mszsdaap41> (raw)
In-Reply-To: <1576647693.15003.11.camel@mtksdaap41>
On Wed, 2019-12-18 at 13:41 +0800, CK Hu wrote:
> Hi, Jitao:
>
> On Mon, 2019-12-16 at 16:29 +0800, Jitao Shi wrote:
> > Add a property to control mipi tx drive current:
> > "mipitx-current-drive"
> >
> > Signed-off-by: Jitao Shi <jitao.shi@mediatek.com>
> > ---
> > .../devicetree/bindings/display/mediatek/mediatek,dsi.txt | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt
> > index a19a6cc375ed..780201ddcd5c 100644
> > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt
> > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt
> > @@ -33,6 +33,9 @@ Required properties:
> > - #clock-cells: must be <0>;
> > - #phy-cells: must be <0>.
> >
> > +Optional properties:
> > +- mipitx-current-drive: adjust driving current, should be 1 ~ 0xF
> > +
>
> In "[PATCH 3/4] drm/mediatek: add the mipitx driving control" [1], I see
> that you actually control a register its name is MIPITX_VOLTAGE_SEL, so
> I guess this control the voltage. If mipi_tx has the ability to control
> the voltage, could we just treat mipi_tx as a regulator? For a
> regulator, regulator-min-microvolt and regulator-max-microvolt would
> limit the volt range and you could get it by
> of_get_regulator_init_data(). If it actually control the current,
> regulator-min-microamp and regulator-max-microamp could be used. I'm not
> expert on this, so please give me more information on this.
>
> [1]
> http://lists.infradead.org/pipermail/linux-mediatek/2019-December/025638.html
>
> Regards,
> CK
>
'MIPITX_VOLTAGE_SEL' is the whole 32bit name.
mipitx-current-drive is just bit[9:6] RG_DSI_HSTX_LDO_REF_SEL,
Not for voltage.
Best Regards
Jitao
> > Example:
> >
> > mipi_tx0: mipi-dphy@10215000 {
> > @@ -42,6 +45,7 @@ mipi_tx0: mipi-dphy@10215000 {
> > clock-output-names = "mipi_tx0_pll";
> > #clock-cells = <0>;
> > #phy-cells = <0>;
> > + mipitx-current-drive = <0x8>;
> > };
> >
> > dsi0: dsi@1401b000 {
>
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-02-25 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 8:29 [PATCH 0/4] Config mipi tx drive current and impedance Jitao Shi
2019-12-16 8:29 ` [PATCH 1/4] dt-binds: display: mediatek: add property to control mipi tx drive current Jitao Shi
2019-12-18 5:41 ` CK Hu
2020-02-25 11:42 ` Jitao Shi [this message]
2019-12-16 8:29 ` [PATCH 2/4] dt-binds: display: mediatek: get mipitx calibration data from nvmem Jitao Shi
2019-12-16 8:29 ` [PATCH 3/4] drm/mediatek: add the mipitx driving control Jitao Shi
2019-12-16 8:29 ` [PATCH 4/4] drm/mediatek: config mipitx impedance with calibration data Jitao Shi
2019-12-20 2:31 ` CK Hu
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=1582630955.13085.2.camel@mszsdaap41 \
--to=jitao.shi@mediatek.com \
--cc=Bibby.Hsieh@mediatek.com \
--cc=Yingjoe.Chen@mediatek.com \
--cc=airlied@linux.ie \
--cc=cawa.cheng@mediatek.com \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eddie.huang@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=stonea168@163.com \
/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