linux-kernel - Re: [PATCH 0/2] ARM: dts: Use MMC pwrseq instead regulators for IGEP WiFi init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20151208001406.GS23396@atomide.com>
Date:	Mon, 7 Dec 2015 16:14:06 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Enric Balletbo Serra <eballetbo@...il.com>
Cc:	Javier Martinez Canillas <javier@....samsung.com>,
	linux-kernel@...r.kernel.org,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Agustí Fontquerni i Gorchs 
	<afontquerni@...ebcn.com>, Pau Pajuel <ppajuel@...il.com>
Subject: Re: [PATCH 0/2] ARM: dts: Use MMC pwrseq instead regulators for IGEP
 WiFi init

* Enric Balletbo Serra <eballetbo@...il.com> [151204 06:40]:
> 2015-12-03 20:27 GMT+01:00 Tony Lindgren <tony@...mide.com>:
> > * Javier Martinez Canillas <javier@....samsung.com> [151203 10:29]:
> >
> >> Since is working for the boards with the libertas chip, I preferred
> >> to remove the DTS hack but left the boards with wlcore chip since
> >> you said the startup-delay-us is needed there (but probably we should
> >> add to the regulators in the boards that don't have it then).
> >
> > OK
> 
> I guess will be interesting cc'ing the ISEE people. Added Agusti and Pau.

Applying these both into omap-for-v4.5/dt thanks.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/