From: Peter Korsgaard <peter@korsgaard.com>
To: Marek Vasut <marex@nabladev.com>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michal Simek <michal.simek@amd.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: zynqmp: Add ifm ZynqMP VHIP6 EvalBoard
Date: Mon, 14 Sep 2026 07:32:05 +0200 [thread overview]
Message-ID: <87y0d4v1nu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <00acb35f-ea7c-465c-96da-4eb5dac9e2cc@nabladev.com> (Marek Vasut's message of "Mon, 14 Sep 2026 03:55:28 +0200")
>>>>> "Marek" == Marek Vasut <marex@nabladev.com> writes:
Hi,
>> OK, but why not add all the referenced GPIOs if you fill out
>> gpio-line-names anyway?
> Because the userspace depends only on this one line name. But since
> eeprom node contains wp-gpios DT property now and the kernel controls
> the nWP GPIO, I can also turn this around and drop the gpio-line-names
> entirely. What do you think ?
Up to you. I personally find it helpful for debugging (E.G. the debugfs
output), but if it isn't used at all...
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2026-09-14 5:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 18:26 [PATCH v2 1/2] dt-bindings: soc: xilinx: Document ifm ZynqMP VHIP6 EvalBoard Marek Vasut
2026-09-09 18:26 ` [PATCH v2 2/2] arm64: zynqmp: Add " Marek Vasut
2026-09-09 18:39 ` sashiko-bot
2026-09-11 7:32 ` Krzysztof Kozlowski
2026-09-11 14:50 ` Marek Vasut
2026-09-11 9:38 ` Peter Korsgaard
2026-09-11 14:49 ` Marek Vasut
2026-09-13 14:27 ` Peter Korsgaard
2026-09-14 1:55 ` Marek Vasut
2026-09-14 5:32 ` Peter Korsgaard [this message]
2026-09-14 13:50 ` Marek Vasut
2026-09-10 6:22 ` [PATCH v2 1/2] dt-bindings: soc: xilinx: Document " Michal Simek
2026-09-10 7:01 ` Marek Vasut
2026-09-10 7:17 ` Michal Simek
2026-09-10 23:39 ` Marek Vasut
2026-09-11 8:38 ` Michal Simek
2026-09-11 15:54 ` Marek Vasut
2026-09-14 6:29 ` Michal Simek
2026-09-15 0:10 ` Marek Vasut
2026-09-11 7:32 ` 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=87y0d4v1nu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=michal.simek@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.