From: Pavel Machek <pavel@ucw.cz>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org, arnd@arndb.de,
f.fainelli@gmail.com, krzyszccf.kozlowski+dt@linaro.org,
nsaenz@kernel.org, olof@lixom.net, robh+dt@kernel.org,
soc@kernel.org, stefan.wahren@i2se.com,
william.zhang@broadcom.com
Subject: Re: [PATCH] ARM: dts: Add Raspberry Pi Compute Module 4 CANOPi Board
Date: Thu, 20 Oct 2022 14:16:08 +0200 [thread overview]
Message-ID: <20221020121608.GA1774@bug> (raw)
In-Reply-To: <e652ad18-3a35-e8a0-939c-5f2a59cfc3d0@linaro.org>
Hi!
> > + led-pwr {
> > + label = "PWR";
> > + gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
> > + default-state = "keep";
> > + linux,default-trigger = "default-on";
> > + };
NAK on the label, see/modify well-known-leds.txt.
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org, arnd@arndb.de,
f.fainelli@gmail.com, krzyszccf.kozlowski+dt@linaro.org,
nsaenz@kernel.org, olof@lixom.net, robh+dt@kernel.org,
soc@kernel.org, stefan.wahren@i2se.com,
william.zhang@broadcom.com
Subject: Re: [PATCH] ARM: dts: Add Raspberry Pi Compute Module 4 CANOPi Board
Date: Thu, 20 Oct 2022 14:16:08 +0200 [thread overview]
Message-ID: <20221020121608.GA1774@bug> (raw)
In-Reply-To: <e652ad18-3a35-e8a0-939c-5f2a59cfc3d0@linaro.org>
Hi!
> > + led-pwr {
> > + label = "PWR";
> > + gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
> > + default-state = "keep";
> > + linux,default-trigger = "default-on";
> > + };
NAK on the label, see/modify well-known-leds.txt.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-20 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 15:31 [PATCH] ARM: dts: Add Raspberry Pi Compute Module 4 CANOPi Board Ariel D'Alessandro
2022-09-16 15:31 ` Ariel D'Alessandro
2022-09-17 10:18 ` Stefan Wahren
2022-09-17 10:18 ` Stefan Wahren
2022-09-19 7:47 ` Alexander Dahl
2022-09-19 7:47 ` Alexander Dahl
2022-09-19 11:18 ` Stefan Wahren
2022-09-19 11:18 ` Stefan Wahren
2022-09-20 8:31 ` Alexander Dahl
2022-09-20 8:31 ` Alexander Dahl
2022-09-20 15:41 ` Stefan Wahren
2022-09-20 15:41 ` Stefan Wahren
2022-09-20 9:51 ` Krzysztof Kozlowski
2022-09-20 9:51 ` Krzysztof Kozlowski
2022-10-20 12:16 ` Pavel Machek [this message]
2022-10-20 12:16 ` Pavel Machek
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=20221020121608.GA1774@bug \
--to=pavel@ucw.cz \
--cc=ariel.dalessandro@collabora.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzyszccf.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=william.zhang@broadcom.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 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.