From: icenowy@aosc.io
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Mark Brown <broonie@kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-sunxi] [PATCH v6 9/9] arm64: allwinner: a64: enable Wi-Fi for Pine64
Date: Fri, 19 May 2017 15:22:28 +0800 [thread overview]
Message-ID: <16dee602b96510170ee1117cfaae0025@aosc.io> (raw)
In-Reply-To: <20170519071922.awmib4qphl6ac6mj@flea.home>
在 2017-05-19 15:19,Maxime Ripard 写道:
> On Fri, May 19, 2017 at 11:03:33AM +0800, Icenowy Zheng wrote:
>> >The patch looks OK, but given the module is removable, I think it
>> >should be
>> >an overlay. The overlay would enable WiFi + Bluetooth, and all the
>> >peripherals needed to connect them.
>> >
>> >That way, if the module is not installed, we avoid confusing the user
>> >with
>> >unused peripherals, and avoid having live voltage on an unoccupied
>> >header.
>>
>> But as this header have specific usage, we will also confuse user
>> if it's not enabled as its target usage.
>
> Yet you would enable unused resources.
>
> This was already pointed out here:
> https://patchwork.kernel.org/patch/9670235/
I think, before we have an official repository of device tree
overlays (either directly in torvalds/linux or maintained by
linux-sunxi), we shouldn't rely on device tree overlay
functionality.
>
> Maxime
>
> _______________________________________________
> 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:[~2017-05-19 7:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 7:16 [PATCH v6 0/9] AXP803 PMIC support " Icenowy Zheng
2017-05-18 7:16 ` [PATCH v6 1/9] irqchip/sunxi-nmi: add A64 R_INTC to the binding doc Icenowy Zheng
2017-05-18 7:40 ` [linux-sunxi] " Chen-Yu Tsai
2017-05-18 7:52 ` Maxime Ripard
2017-05-18 7:16 ` [PATCH v6 2/9] irqchip/sunxi-nmi: add support for the NMI in A64 R_INTC Icenowy Zheng
2017-05-18 7:52 ` Maxime Ripard
2017-05-19 2:27 ` Chen-Yu Tsai
2017-05-22 9:39 ` Marc Zyngier
2017-05-22 9:41 ` Icenowy Zheng
2017-05-22 14:25 ` [linux-sunxi] " Chen-Yu Tsai
2017-06-05 5:57 ` Chen-Yu Tsai
2017-06-05 7:53 ` Marc Zyngier
2017-06-05 7:56 ` Icenowy Zheng
2017-06-05 8:05 ` Marc Zyngier
2017-05-18 7:16 ` [PATCH v6 3/9] arm64: allwinner: a64: add NMI (R_INTC) controller on A64 Icenowy Zheng
2017-05-19 2:28 ` [linux-sunxi] " Chen-Yu Tsai
2017-05-18 7:16 ` [PATCH v6 4/9] arm64: allwinner: a64: add AXP803 node to Pine64 device tree Icenowy Zheng
2017-05-19 2:28 ` [linux-sunxi] " Chen-Yu Tsai
2017-07-18 3:02 ` Chen-Yu Tsai
2017-05-18 7:16 ` [PATCH v6 5/9] regulator: axp20x-regulator: add support for AXP803 Icenowy Zheng
2017-05-18 7:16 ` [PATCH v6 6/9] mfd: axp20x: add axp20x-regulator cell " Icenowy Zheng
2017-05-22 12:17 ` Lee Jones
2017-05-18 7:16 ` [PATCH v6 7/9] arm64: allwinner: a64: add DTSI file for AXP803 PMIC Icenowy Zheng
2017-05-19 2:29 ` [linux-sunxi] " Chen-Yu Tsai
2017-07-18 3:02 ` Chen-Yu Tsai
2017-05-18 7:16 ` [PATCH v6 8/9] arm64: allwinner: a64: enable AXP803 regulators for Pine64 Icenowy Zheng
2017-05-19 2:54 ` [linux-sunxi] " Chen-Yu Tsai
2017-05-19 3:00 ` Icenowy Zheng
2017-05-19 3:10 ` Chen-Yu Tsai
2017-05-19 3:12 ` Icenowy Zheng
2017-05-19 8:27 ` Andre Przywara
2017-05-19 8:29 ` Icenowy Zheng
2017-05-19 8:55 ` Andre Przywara
2017-07-18 2:58 ` Chen-Yu Tsai
2017-07-18 3:07 ` Icenowy Zheng
2017-05-19 8:56 ` Maxime Ripard
2017-05-18 7:16 ` [PATCH v6 9/9] arm64: allwinner: a64: enable Wi-Fi " Icenowy Zheng
2017-05-19 3:01 ` [linux-sunxi] " Chen-Yu Tsai
2017-05-19 3:03 ` Icenowy Zheng
2017-05-19 7:19 ` Maxime Ripard
2017-05-19 7:22 ` icenowy [this message]
2017-05-23 14:44 ` Maxime Ripard
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=16dee602b96510170ee1117cfaae0025@aosc.io \
--to=icenowy@aosc.io \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=marc.zyngier@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wens@csie.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
all inboxes | Powered by JetHome®