devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@collabora.com>,
	"David Matlack" <dmatlack@google.com>,
	Jing Zhang <jingzhangos@google.com>,
	"Marc Zyngier" <maz@kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Sean Wang <sean.wang@mediatek.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<ryder.lee@kernel.org>, <wenst@chromium.org>,
	<chunfeng.yun@mediatek.com>
Subject: Re: [PATCH v9 2/3] dt-bindings: pinctrl: mt8195: Add mediatek,drive-strength-adv property
Date: Tue, 25 Jan 2022 14:21:33 +0800	[thread overview]
Message-ID: <102ea6303dd16fdf9ec931d0a1845a93afe92545.camel@mediatek.com> (raw)
In-Reply-To: <18f7a647-6153-6d38-dff1-727b9592b01e@gmail.com>

On Thu, 2022-01-13 at 17:31 +0100, Matthias Brugger wrote:
> [dopping Maciej, Paolo and Sean Christopherson]
> 
> On 12/01/2022 12:47, Tinghan Shen wrote:
> > Extend driving support for I2C pins on SoC mt8195.
> > This property is already documented in mediatek,mt8183-pinctrl.yaml.
> > 
> > Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> 
> Looks good to me. Linus please let me know when you are queuing this patch and 
> I'll take the rest of the series. Another option is, that you provide an 
> Acked-by and I can take the whole set through my branch.
> 
> Regards,
> Matthias

Hi Matthias,

I want to send next version to update the CC list of this series, but I'm not sure 
whether this will break the conversation between you and Linus.

Is it ok to send next version? or waiting the response?

Best regards,
TingHan

> 
> > ---
> >   .../bindings/pinctrl/pinctrl-mt8195.yaml      | 35 +++++++++++++++++++
> >   1 file changed, 35 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml
> > b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml
> > index 328ea59c5466..4db4899af6b1 100644
> > --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml
> > +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml
> > @@ -98,6 +98,32 @@ patternProperties:
> >             drive-strength:
> >               enum: [2, 4, 6, 8, 10, 12, 14, 16]
> >   
> > +          mediatek,drive-strength-adv:
> > +            description: |
> > +              Describe the specific driving setup property.
> > +              For I2C pins, the existing generic driving setup can only support
> > +              2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
> > +              can support 0.125/0.25/0.5/1mA adjustment. If we enable specific
> > +              driving setup, the existing generic setup will be disabled.
> > +              The specific driving setup is controlled by E1E0EN.
> > +              When E1=0/E0=0, the strength is 0.125mA.
> > +              When E1=0/E0=1, the strength is 0.25mA.
> > +              When E1=1/E0=0, the strength is 0.5mA.
> > +              When E1=1/E0=1, the strength is 1mA.
> > +              EN is used to enable or disable the specific driving setup.
> > +              Valid arguments are described as below:
> > +              0: (E1, E0, EN) = (0, 0, 0)
> > +              1: (E1, E0, EN) = (0, 0, 1)
> > +              2: (E1, E0, EN) = (0, 1, 0)
> > +              3: (E1, E0, EN) = (0, 1, 1)
> > +              4: (E1, E0, EN) = (1, 0, 0)
> > +              5: (E1, E0, EN) = (1, 0, 1)
> > +              6: (E1, E0, EN) = (1, 1, 0)
> > +              7: (E1, E0, EN) = (1, 1, 1)
> > +              So the valid arguments are from 0 to 7.
> > +            $ref: /schemas/types.yaml#/definitions/uint32
> > +            enum: [0, 1, 2, 3, 4, 5, 6, 7]
> > +
> >             bias-pull-down:
> >               description: |
> >                 For pull down type is normal, it don't need add RSEL & R1R0 define
> > @@ -268,4 +294,13 @@ examples:
> >             bias-pull-down;
> >           };
> >         };
> > +
> > +      i2c0-pins {
> > +        pins {
> > +          pinmux = <PINMUX_GPIO8__FUNC_SDA0>,
> > +                   <PINMUX_GPIO9__FUNC_SCL0>;
> > +          bias-disable;
> > +          mediatek,drive-strength-adv = <7>;
> > +        };
> > +      };
> >       };
> > 


  reply	other threads:[~2022-01-25  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 11:47 [PATCH v9 0/3] Add basic SoC support for mediatek mt8195 Tinghan Shen
2022-01-12 11:47 ` [PATCH v9 1/3] dt-bindings: arm: mediatek: Add mt8195 pericfg compatible Tinghan Shen
2022-01-12 11:47 ` [PATCH v9 2/3] dt-bindings: pinctrl: mt8195: Add mediatek,drive-strength-adv property Tinghan Shen
2022-01-13 16:31   ` Matthias Brugger
2022-01-25  6:21     ` Tinghan Shen [this message]
2022-01-30  0:38       ` Linus Walleij
2022-02-22  9:18         ` Tinghan Shen
2022-01-12 11:47 ` [PATCH v9 3/3] arm64: dts: Add mediatek SoC mt8195 and evaluation board Tinghan Shen
2022-01-12 14:54 ` [PATCH v9 0/3] Add basic SoC support for mediatek mt8195 Maciej S. Szmigiero
2022-01-13  2:17   ` Tinghan Shen

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=102ea6303dd16fdf9ec931d0a1845a93afe92545.camel@mediatek.com \
    --to=tinghan.shen@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmatlack@google.com \
    --cc=jingzhangos@google.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=ryder.lee@kernel.org \
    --cc=sean.wang@mediatek.com \
    --cc=wenst@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;
as well as URLs for NNTP newsgroup(s).