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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 02 Nov 2017 15:49:13 +0800 From: Icenowy Zheng <icenowy@...c.io> To: Stephen Boyd <sboyd@...eaurora.org> Cc: linux-arm-kernel@...ts.infradead.org, Maxime Ripard <maxime.ripard@...e-electrons.com>, Chen-Yu Tsai <wens@...e.org>, linux-sunxi@...glegroups.com, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/2] Add a regmap to Allwinner R40 CCU to export GMAC register 在 2017-11-02 15:11,Stephen Boyd 写道: > On 10/09, Icenowy Zheng wrote: >> >> >> 于 2017年10月9日 GMT+08:00 下午3:18:09, Maxime Ripard >> <maxime.ripard@...e-electrons.com> 写到: >> >On Fri, Oct 06, 2017 at 06:33:31AM +0000, Icenowy Zheng wrote: >> >> In the CCU of the Allwinner R40 SoC, there's a GMAC configuration >> >register, >> >> which is intended to be accessed by the dwmac-sun8i driver. On SoCs >> >already >> >> supported by the driver the register is placed in the syscon rather >> >than >> >> the CCU. >> >> >> >> As CCU is a critical part of the SoC, so write to it should be >> >strictly >> >> limited. A regmap with restricted write permission is created by the >> >R40 >> >> CCU driver, and can be get with dev_get_regmap. In order to tie the >> >regmap >> >> to the CCU device, the R40 CCU is now a platform driver, so a >> >platform >> >> device is created for it (and then tied with the regmap). >> >> >> >> The first patch does the conversion of the driver to a platform >> >driver, >> >> and the second patch adds the regmap. >> > >> >I'd like to see first what you want to do with it. >> >> Export the GMAC configuration register to dwmac-sun8i. >> > > Is this series going to be reposted? Yes, thanks.
Powered by blists - more mailing lists