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
| ||
|
Date: Mon, 25 Jan 2016 11:07:32 +0900 From: Masahiro Yamada <yamada.masahiro@...ionext.com> To: Arnd Bergmann <arnd@...db.de> Cc: Robert Jarzmik <robert.jarzmik@...e.fr>, Russell King <linux@....linux.org.uk>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Haojian Zhuang <haojian.zhuang@...il.com>, arm@...nel.org, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, Daniel Mack <daniel@...que.org> Subject: Re: [PATCH] ARM: pxa: let PXA27x select PINCTRL Hi Robert, 2016-01-25 6:33 GMT+09:00 Arnd Bergmann <arnd@...db.de>: > On Sunday 24 January 2016 21:39:11 Robert Jarzmik wrote: >> Arnd Bergmann <arnd@...db.de> writes: >> >> > On Saturday 23 January 2016 23:07:44 Robert Jarzmik wrote: >> >> I have this patch in my local tree for 2 monthes (see [1]). This is the patch >> >> I'd rather have. I had not posted it as I didn't think the pinctrl work was over >> >> yet. I know at least that pxa3xx is ready (as pinctrl-single should be used), >> >> and I had not the time to create the map for pxa25x. >> > >> > Once you are done, does that mean the plat-pxa/mfp.c stuff becomes >> > completely unused on pxa, or will it coexist with pinctrl? >> At first it will coexist. >> The main blocker so far I have are : >> - the pinconf in platform_data platform to define sleep state pin levels >> (aka. MFPR_LPM_DRIVE_LOW and MFPR_LPM_DRIVE_HIGH) >> I have [1], but it's not working yet, ie. upon entering suspend to RAM, the >> GPIO sleep registers are not programmed as expected. >> - all the pxa machine code have to be migrated from MFP to pinctrl >> >> So it will take time. > > Ok. > >> > I'm asking because it seems that at that point, the entire plat-pxa >> > directory can be removed, with the dma.c and ssp.c files getting >> > moved to mach-pxa, and mfp.c moved to mach-mmp. :-) >> dma.c will die soon enough anyway, ssp.c will move to mach-pxa indeed, and as >> for mfp.c it requires a bit of work. > > Sounds good. > It's OK if you will this later. Just disregard mine. -- Best Regards Masahiro Yamada
Powered by blists - more mailing lists