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: Tue, 20 Jan 2015 07:58:43 +0100 From: Romain Perier <romain.perier@...il.com> To: Heiko Stübner <heiko@...ech.de> Cc: David Miller <davem@...emloft.net>, peppe.cavallaro@...com, netdev <netdev@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, devicetree <devicetree@...r.kernel.org>, roger.chen@...k-chips.com Subject: Re: [PATCH v1 0/4] net: stmmac: dwmac-rk: Fix phy regulator issues Hi all, 2015-01-19 21:19 GMT+01:00 Heiko Stübner <heiko@...ech.de>: > Hi Romain > > Am Montag, 19. Januar 2015, 18:08:05 schrieb Romain Perier: >> This series fixes few issues in dwmac-rk: >> >> 1. Voltage settings was hardcoded into the driver for the phy regulator. >> The driver now uses the default voltage settings found in the devicetree, >> which are applied throught the regulator framework. >> 2. The regulator name used to power on or power off the phy was put in the >> devicetree variable "phy_regulator", which is not standard and added a lot >> of code for nothing. The driver now uses the devicetree property >> "phy-supply" and the corresponding functions to manipulate this regulator. >> >> The corresponding devicetree files are also updated. As, dwmac-rk was >> recently pushed in the development tree, I don't care about devicetree >> backward compatibility issues. > > This last sentence is slightly misleading :-) . > Yes, I meant that I don't need to care about it, as you explain it well below. Sorry for my misleading sentence ;) . I will fix it in my second serie. > The actual fact is, that these new bindings for the rk3288 gmac have not been > released with any official kernel release yet ... i.e. the will be released with > 3.20 in whatever form, so we don't _need_ to care about keeping compatibility > still for the next 2.5 weeks or so. > > @Dave: it would be good if this series (when fixed) could still go into the > 3.20 material so we don't get stuck with the non-standard regulator property. > > > As we'll probably need a v2 due to at the issue in patch3, could you also > switch places of patch1 and 2, which would keep bisecatbility (i.e. regulator > property before removing the voltage setting from the driver). This sentence about re-ordering patches is for Dave or for me ? Thanks, Romain -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists