From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Mon, 16 Mar 2015 14:25:09 -0700 Subject: [PATCH v6 6/6] wlcore: remove wl12xx_platform_data In-Reply-To: <201503162215.06436@pali> References: <1426162154-8716-1-git-send-email-eliad@wizery.com> <201503162158.50587@pali> <20150316210143.GF12397@atomide.com> <201503162215.06436@pali> Message-ID: <20150316212508.GI12397@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Pali Roh?r [150316 14:15]: > On Monday 16 March 2015 22:01:43 Tony Lindgren wrote: > > * Pali Roh?r [150316 13:59]: > > > On Monday 16 March 2015 16:29:39 Tony Lindgren wrote: > > > > I believe the last pending issues is the support for > > > > ATAG_REVISION in device tree mode as posted by Pali. > > > > > > No. In DT boot there is missing /proc/atags file (readable > > > by userspace processes). > > > > Oh OK thanks for the update. > > > > > And also broken AES/SHA/MD5 support. Fix for crypto DT stuff > > > I already sent. > > > > But this is not a regression in mainline with legacy boot vs > > device tree based booting, right? Sounds like it never worked > > in the mainline or am thinking of some other set of patches? > > > > Regards, > > > > Tony > > In legacy board code are DMA channels defined. In DT files not. > So I think this is regression. Omap secure devices are broken in > both legacy & DT code, but non secure could work with legacy > code. But all devices booted with DT are broken. OK I'll apply the DMA channels into omap-for-v4.0/fixes in that case. Regards, Tony