From: Andrei Lalaev <andrei.lalaev@emlid.com>
To: andy.shevchenko@gmail.com
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrei Lalaev <andrei.lalaev@emlid.com>
Subject: Re: [PATCH] gpiolib: of: fix bounds check for valid mask
Date: Tue, 12 Apr 2022 10:03:58 +0300 [thread overview]
Message-ID: <20220412070355.139507-1-andrei.lalaev@emlid.com> (raw)
In-Reply-To: <CAHp75VePiCm6wH7aXcbnrt-4nntqx99s45wYk3+C2AKs=Usang@mail.gmail.com>
On Mon, Apr 11, 2022 at 7:55 PM Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
...
> On top of that, it would be nice to be sure that at least all current
> in-kernel users (meaning all DTS provided so far by the kernel) do
> interpret it as start,size.
I checked the DTS and only 36 of them use "gpio-reserved-ranges".
The 33 of them use tuple with the second element that is less than the first.
So it means that the maintainers interpreted it as "start,size".
And only 3 of them use one tuple with the second element is greater than the first.
The list of this DTS:
1. arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone.dtsi
AngeloGioacchino Del Regno added it in the commit 9da65e441d4d
("arm64: dts: qcom: Add support for SONY Xperia X Performance / XZ / XZs (msm8996, Tone platform)")
But in another commit 8b36c824b9a77 ("arm64: dts: qcom: sdm630-xperia-nile: Add all RPM and fixed regulators")
he clearly interpreted it as "start,size" because the second element
is less than the first.
2. arch/arm64/boot/dts/qcom/msm8998-fxtec-pro1.dts
The same maintainer as for the previous DTS.
He added "reserved-range" in the commit 122d2c5f31b6e
("arm64: dts: qcom: Add support for MSM8998 F(x)tec Pro1 QX1000")
3. arch/arm64/boot/dts/qcom/sa8155p-adp.dts
Bhupesh Sharma added it in the commit 12dd4ebda47ab
("arm64: dts: qcom: Fix usb entries for SA8155p adp board")
Should I ask these maintainers how they interpreted this property?
> Otherwise this will be an (unacceptable) ABI change and hence documentation
> would need to be fixed with variable names in the code
I want you to notice that "of_gpiochip_init_valid_mask" uses "bitmap_clear"
that clears "nbits" bits starting from the "start". So it can't be interpreted
as "start,end". That's why I think everyone interprets it as "start,size" because
it works like "start,size" and the documentation tells it is "start,size".
next prev parent reply other threads:[~2022-04-12 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 6:33 Andrei Lalaev
2022-04-11 10:48 ` Bartosz Golaszewski
2022-04-11 12:12 ` Andy Shevchenko
2022-04-11 14:46 ` Andrei Lalaev
2022-04-11 16:55 ` Andy Shevchenko
2022-04-12 7:03 ` Andrei Lalaev [this message]
2022-04-12 8:35 ` Andy Shevchenko
2022-04-12 8:28 ` Bartosz Golaszewski
2022-04-12 8:36 ` Andy Shevchenko
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=20220412070355.139507-1-andrei.lalaev@emlid.com \
--to=andrei.lalaev@emlid.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 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®