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, 30 Aug 2018 18:06:57 -0700 From: Stephen Boyd <sboyd@...nel.org> To: Andy Gross <andy.gross@...aro.org>, Bjorn Andersson <bjorn.andersson@...aro.org>, Stephen Boyd <sboyd@...eaurora.org> Cc: Sricharan R <sricharan@...eaurora.org>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-soc@...r.kernel.org, linux-kernel@...r.kernel.org, Craig Tatlor <ctatlor97@...il.com> Subject: Re: [PATCH 2/3] firmware: qcom: scm: Refactor clock handling Quoting Bjorn Andersson (2018-08-29 16:15:04) > At one point in time all "future" platforms required three clocks, so > the binding and driver was written to treat this as the default case. > But new platforms has no clock requirements, which currently makes them > all a special case, causing the need for a patch in the binding and > driver for each new platform added. > > This patch reworks the driver logic so that it will attempt to acquire > all three clocks and fail based on the given compatible. This allow us > to drop the clock requirement from "qcom,scm", in a way that will remain > backwards compatible with existing DT files. > > Specific compatibles are added for apq8084, msm8916 and msm8974 to match > the updated binding and although equivalent to qcom,scm both ipq4019 and > msm8996 are kept as these have been used without fallback to qcom,scm. > > The result of this patch is that new platforms, that require no clocks, > can be use the fallback compatible of "qcom,scm". > > Signed-off-by: Bjorn Andersson <bjorn.andersson@...aro.org> > --- Reviewed-by: Stephen Boyd <sboyd@...nel.org>
Powered by blists - more mailing lists