linux-kernel - Re: [PATCH v7 4/4] clk: qcom: add clock controller driver for qca8386/qca8084

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e08e3cc1-f70c-31b7-7e7c-0cc368213374@quicinc.com>
Date:   Thu, 14 Sep 2023 16:58:16 +0800
From:   Jie Luo <quic_luoj@...cinc.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        <andersson@...nel.org>, <agross@...nel.org>,
        <konrad.dybcio@...aro.org>, <mturquette@...libre.com>,
        <sboyd@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
        <catalin.marinas@....com>, <will@...nel.org>,
        <p.zabel@...gutronix.de>
CC:     <linux-arm-msm@...r.kernel.org>, <linux-clk@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <quic_srichara@...cinc.com>
Subject: Re: [PATCH v7 4/4] clk: qcom: add clock controller driver for
 qca8386/qca8084



On 9/14/2023 3:58 PM, Krzysztof Kozlowski wrote:
> On 14/09/2023 09:52, Jie Luo wrote:
>>
>>
>> On 9/14/2023 2:15 PM, Krzysztof Kozlowski wrote:
>>> On 14/09/2023 07:46, Luo Jie wrote:
>>>> The clock controller driver of qca8386/qca8084 is registered
>>>> as the MDIO device, the hardware register is accessed by MDIO bus
>>>> that is normally used to access general PHY device, which is
>>>> different from the current existed qcom clock controller drivers
>>>> using ioremap to access hardware clock registers.
>>>>
>>>> MDIO bus is common utilized by both qca8386/qca8084 and other
>>>> PHY devices, so the mutex lock mdio_bus->mdio_lock should be
>>>> used instead of using the mutex lock of remap.
>>>>
>>>> To access the hardware clock registers of qca8386/qca8084, there
>>>> is special MDIO frame sequence(three MDIO read/write operations)
>>>> need to be sent to device.
>>>>
>>>> Signed-off-by: Luo Jie <quic_luoj@...cinc.com>
>>>> ---
>>>>    drivers/clk/qcom/Kconfig       |    9 +
>>>>    drivers/clk/qcom/Makefile      |    1 +
>>>>    drivers/clk/qcom/nsscc-qca8k.c | 2178 ++++++++++++++++++++++++++++++++
>>>>    3 files changed, 2188 insertions(+)
>>>>    create mode 100644 drivers/clk/qcom/nsscc-qca8k.c
>>>>
>>>> diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
>>>> index 865db5202e4c..c95ada6a1385 100644
>>>> --- a/drivers/clk/qcom/Kconfig
>>>> +++ b/drivers/clk/qcom/Kconfig
>>>> @@ -203,6 +203,15 @@ config IPQ_GCC_9574
>>>>    	  i2c, USB, SD/eMMC, etc. Select this for the root clock
>>>>    	  of ipq9574.
>>>>    
>>>> +config IPQ_NSSCC_QCA8K
>>>> +	tristate "QCA8K(QCA8386 or QCA8084) NSS Clock Controller"
>>>> +	depends on MDIO_BUS || COMPILE_TEST
>>>
>>> This is SoC is for both ARM and ARM64 worlds?
>>>
>> Thanks Krzysztof for the comments.
>> This chip is independent of the ARCH, which just depends on the MDIO
>> bus, both mips and arm are supported.
> 
> There is no ARCH_QCOM on MIPS, so it's limited to ARM. Then add
> restriction to ARM || COMPILE_TEST.
> 
> Best regards,
> Krzysztof
> 
okay, will add the depends on ARM, thanks Krzysztof.