From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Will Deacon <will.deacon@arm.com>,
kraxel@redhat.com, Lee Jones <lee@kernel.org>,
Andrea Merello <andrea.merello@gmail.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
bcm-kernel-feedback-list@broadcom.com,
Mark Rutland <mark.rutland@arm.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] ARM64: dts: bcm2837-rpi-3-b: remove incorrect pwr LED
Date: Mon, 14 Nov 2016 16:39:41 -0800 [thread overview]
Message-ID: <871sydfueq.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <741880731.428971.a2c5fd60-1b30-481e-b728-fc62c8d1c81a.open-xchange@email.1und1.de>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Stefan Wahren <stefan.wahren@i2se.com> writes:
> Hi Eric,
>
> [add Gerd to CC]
>
>> Eric Anholt <eric@anholt.net> hat am 11. November 2016 um 18:38 geschrieben:
>>
>>
>> From: Andrea Merello <andrea.merello@gmail.com>
>>
>> We are incorrectly defining the pwr LED, attaching it to a gpio line
>> that is wired to the Wi-Fi SDIO module (which fails due to this).
>
> i agree with the intention of this patch, but is the upstream kernel really
> affected? I can't see any compatible for the Wifi interface.
The wifi isn't in the DT yet because the driver isn't merged. Some
progress was made on that a while ago, but people asked for more
cleanups so it's still living out of tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-15 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 17:38 [PATCH] ARM64: dts: bcm2837-rpi-3-b: remove incorrect pwr LED Eric Anholt
2016-11-12 14:41 ` Stefan Wahren
2016-11-15 0:39 ` Eric Anholt [this message]
2016-11-15 10:46 ` Gerd Hoffmann
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=871sydfueq.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=andrea.merello@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=kraxel@redhat.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).