[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250110130025.55004-1-brgl@bgdev.pl>
Date: Fri, 10 Jan 2025 14:00:23 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Maxime Ripard <mripard@...nel.org>,
J . Neuschäfer <j.ne@...teo.net>,
Csókás Bence <csokas.bence@...lan.hu>,
"Geert Uytterhoeven via gmail . com" <geert@...ux-m68k.org>
Cc: linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: [PATCH 0/2] gpio: 74x164: use a compatible fallback and don't extend the driver
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.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
Powered by blists - more mailing lists