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
| ||
|
Message-ID: <4ad99501-01e2-47e7-b185-f7f96d872bf7@linaro.org> Date: Wed, 20 Dec 2023 08:28:15 +0100 From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> To: Jie Luo <quic_luoj@...cinc.com>, Conor Dooley <conor@...nel.org> Cc: agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk, robert.marko@...tura.hr, linux-arm-msm@...r.kernel.org, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, quic_srichara@...cinc.com Subject: Re: [PATCH v2 5/5] dt-bindings: net: ipq4019-mdio: Document ipq5332 platform On 16/12/2023 16:37, Jie Luo wrote: >> >> I'm surprised you didn't pick up on this, but there are actually _2_ >> internal references, which I have just noticed while double checking the >> binding patch. > > i noticed this, the reference clock source can be supported by clocks as > you suggested here, it is really helpful. >> >> What is the impact of using the 48 MHz or 96 MHz internal reference? > They works on the different IPQ platform, 96MHZ internal reference is > used on IPQ5018, the internal 48MHZ is used on the IPQ5332, that is So the binding is just incorrect. Why do you even consider configuring 96 MHz internal reference on IPQ5332? Best regards, Krzysztof
Powered by blists - more mailing lists