linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	"linus.walleij" <linus.walleij@linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Cc: Phil Elwell <phil@raspberrypi.com>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>
Subject: Re: DTB backward/forward compatibility with "pinctrl: bcm2835: Change init order for gpio hogs"
Date: Mon, 7 Mar 2022 12:38:31 +0100	[thread overview]
Message-ID: <e335eeba-a527-04c3-3cac-9d80387bb9fc@i2se.com> (raw)
In-Reply-To: <cf47c05b-cddd-d61b-2668-8a98f1ac77b3@gmail.com>

Hi,

Am 06.03.22 um 17:54 schrieb Florian Fainelli:
> Hi Stefan,
>
> On 3/6/2022 7:03 AM, Stefan Wahren wrote:
>> Hi Florian,
>>
>> it seems that other platform stumbled on the same issue:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220304&id=9b4924da4711674e62d97d4f5360446cc78337af
>>
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220304&id=7ed07855773814337b9814f1c3e866df52ebce68
>>
>>
>> I will try to prepare a patch.
>
> Thank you! Do you think we could have a core function expose which
> would do essentially avoid drivers having to sprinkle checks for the
> absence of a 'gpio-ranges' property?

unfortunately my first attempts to implement it similiar to the
solutions above failed. I read the explanations from the original fix
from Christian Lamparter [1] and from my understanding the backward
compatibility must be implemented into gpiochip_add_data() or a variant.
Before the gpiochip is not registered and afterwards it would be too late.

My test scenario (worst case) is an additional gpio hog for the
Raspberry Pi 3 B with removed gpio-ranges:

diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
b/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
index e12938b..a5163cc 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
+++ b/arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts
@@ -123,6 +123,14 @@
                          "SD_DATA1_R",
                          "SD_DATA2_R",
                          "SD_DATA3_R";
+
+       ant1: ant1-hog {
+               gpio-hog;
+               gpios = <23 GPIO_ACTIVE_HIGH>;
+               output-high;
+               line-name = "ant1";
+       };
 };
 
 &hdmi {
diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
index c113661..4b65954 100644
--- a/arch/arm/boot/dts/bcm283x.dtsi
+++ b/arch/arm/boot/dts/bcm283x.dtsi
@@ -126,7 +126,7 @@
                        interrupt-controller;
                        #interrupt-cells = <2>;
 
-                       gpio-ranges = <&gpio 0 0 54>;
+                       // gpio-ranges = <&gpio 0 0 54>;
 
                        /* Defines common pin muxing groups
                         *

[1] -
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220307&id=a86caa9ba5d70696ceb35d1d39caa20d8b641387
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-03-07 11:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 19:39 DTB backward/forward compatibility with "pinctrl: bcm2835: Change init order for gpio hogs" Florian Fainelli
2022-01-25 19:48 ` Phil Elwell
2022-01-25 19:58   ` Florian Fainelli
2022-01-26  1:33     ` Florian Fainelli
2022-01-27 16:31       ` Stefan Wahren
2022-03-06 15:03         ` Stefan Wahren
2022-03-06 16:54           ` Florian Fainelli
2022-03-06 17:58             ` Stefan Wahren
2022-03-07 11:38             ` Stefan Wahren [this message]
2022-03-08 19:13               ` Stefan Wahren
2022-03-09  1:10                 ` Florian Fainelli

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=e335eeba-a527-04c3-3cac-9d80387bb9fc@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=f.fainelli@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=nsaenz@kernel.org \
    --cc=phil@raspberrypi.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;
as well as URLs for NNTP newsgroup(s).