[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZRp-DFQgb3=Ut27DHd1w11_aEY0HbLjJHob=C5Ek-dyw@mail.gmail.com>
Date: Tue, 16 Apr 2024 14:22:09 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, Kent Gibson <warthog618@...il.com>,
linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
brcm80211@...ts.linux.dev, brcm80211-dev-list.pdl@...adcom.com,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Arend van Spriel <arend.vanspriel@...adcom.com>, Kalle Valo <kvalo@...nel.org>,
Charles Keepax <ckeepax@...nsource.cirrus.com>
Subject: Re: [PATCH v2 1/2] gpiolib: Fix a mess with the GPIO_* flags
On Fri, Apr 12, 2024 at 9:44 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> IIUC include/dt-bindings/ headers should only be used by DT sources
> and code that parses the OF properties.
That's what I have come to understand as well.
I wonder if there is something that can be done to enforce it?
Ideally the code that parses OF properties should have to
opt in to get access to the <dt-bindings/*> namespace.
Yours,
Linus Walleij
Powered by blists - more mailing lists