From: Neil Armstrong <neil.armstrong@linaro.org>
To: Da Xue <da@libre.computer>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: gxl: set i2c bias to pull-up
Date: Mon, 28 Apr 2025 09:32:07 +0200 [thread overview]
Message-ID: <20523c9e-f7de-4355-82ed-380ee03083f0@linaro.org> (raw)
In-Reply-To: <20250425203118.1444481-1-da@libre.computer>
On 25/04/2025 22:31, Da Xue wrote:
> GXL I2C pins need internal pull-up enabled to operate if there
> is no external resistor. The pull-up is 60kohms per the datasheet.
>
> We should set the bias when i2c pinmux is enabled.
So, yes in some cases when the on-board pull-up is missing, the on-pad
pull-up is required, but the whole idea was to only add the pull-up property
when needed.
So I know the real motivation is again about the 40pin headers, where
some applications don't add a pull-up and still want to have i2c working.
So my question is: why can't the pull-up property be added in overlays ?
Neil
>
> Signed-off-by: Da Xue <da@libre.computer>
> ---
> arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> index 2dc2fdaecf9f..aed8dbfbb64d 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> @@ -214,7 +214,7 @@ mux {
> groups = "i2c_sck_ao",
> "i2c_sda_ao";
> function = "i2c_ao";
> - bias-disable;
> + bias-pull-up;
> };
> };
>
> @@ -576,7 +576,7 @@ mux {
> groups = "i2c_sck_a",
> "i2c_sda_a";
> function = "i2c_a";
> - bias-disable;
> + bias-pull-up;
> };
> };
>
> @@ -585,7 +585,7 @@ mux {
> groups = "i2c_sck_b",
> "i2c_sda_b";
> function = "i2c_b";
> - bias-disable;
> + bias-pull-up;
> };
> };
>
> @@ -594,7 +594,7 @@ mux {
> groups = "i2c_sck_c",
> "i2c_sda_c";
> function = "i2c_c";
> - bias-disable;
> + bias-pull-up;
> };
> };
>
> @@ -603,7 +603,7 @@ mux {
> groups = "i2c_sck_c_dv19",
> "i2c_sda_c_dv18";
> function = "i2c_c";
> - bias-disable;
> + bias-pull-up;
> };
> };
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-04-28 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 20:31 Da Xue
2025-04-27 21:08 ` Martin Blumenstingl
2025-04-28 2:36 ` Xianwei Zhao
2025-04-28 2:46 ` Da Xue
2025-04-28 7:32 ` Neil Armstrong [this message]
2025-04-29 2:08 ` Da Xue
2025-05-04 21:03 ` Martin Blumenstingl
2025-05-05 12:27 ` neil.armstrong
2025-05-05 12:36 ` Neil Armstrong
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=20523c9e-f7de-4355-82ed-380ee03083f0@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=conor+dt@kernel.org \
--cc=da@libre.computer \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh@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
all inboxes | Powered by JetHome®