From: Bartosz Golaszewski <brgl@bgdev.pl>
To: "Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"J . Neuschäfer" <j.ne@posteo.net>,
"Csókás Bence" <csokas.bence@prolan.hu>,
"Geert Uytterhoeven via gmail . com" <geert@linux-m68k.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH 0/2] gpio: 74x164: use a compatible fallback and don't extend the driver
Date: Fri, 10 Jan 2025 14:00:23 +0100 [thread overview]
Message-ID: <20250110130025.55004-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
There were other suggested solutions (for instance: just use the
existing compatible for the On Semi variant) but I figured the most
common approach is to use a fallback value for 100% compatible models
and this is what Rob suggested as well.
This reverts the driver change and makes the "onnn,74hc595a" compatible
use "fairchild,74hc595" as fallback.
Bartosz Golaszewski (2):
Revert "gpio: 74x164: Add On Semi MC74HC595A compat"
dt-bindings: gpio: fairchild,74hc595: use a fallback for Semi
MC74HC595A
.../devicetree/bindings/gpio/fairchild,74hc595.yaml | 10 ++++++----
drivers/gpio/gpio-74x164.c | 2 --
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2025-01-10 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:00 Bartosz Golaszewski [this message]
2025-01-10 13:00 ` [PATCH 1/2] Revert "gpio: 74x164: Add On Semi MC74HC595A compat" Bartosz Golaszewski
2025-01-11 10:53 ` Krzysztof Kozlowski
2025-01-10 13:00 ` [PATCH 2/2] dt-bindings: gpio: fairchild,74hc595: use a fallback for Semi MC74HC595A Bartosz Golaszewski
2025-01-11 10:50 ` Krzysztof Kozlowski
2025-01-10 13:32 ` [PATCH 0/2] gpio: 74x164: use a compatible fallback and don't extend the driver Csókás Bence
2025-01-10 13:38 ` Bartosz Golaszewski
2025-01-10 14:09 ` Geert Uytterhoeven
2025-01-10 14:14 ` Bartosz Golaszewski
2025-01-11 11:00 ` Krzysztof Kozlowski
2025-01-12 9:57 ` Geert Uytterhoeven
2025-01-13 8:22 ` Bartosz Golaszewski
2025-01-11 10:56 ` Krzysztof Kozlowski
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=20250110130025.55004-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=csokas.bence@prolan.hu \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=j.ne@posteo.net \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--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