Message ID | 20230121112358.52216-2-robimarko@gmail.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp679966wrn; Sat, 21 Jan 2023 03:30:47 -0800 (PST) X-Google-Smtp-Source: AMrXdXusQGJb6skUk9lkZ3tFblLbexGcdJPRCGV7oErjzSuxTYAzGxmfExYAhUyB++7PQ5qYnPKZ X-Received: by 2002:a05:6a00:2194:b0:58a:fa8d:ecce with SMTP id h20-20020a056a00219400b0058afa8deccemr21638968pfi.29.1674300646769; Sat, 21 Jan 2023 03:30:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674300646; cv=none; d=google.com; s=arc-20160816; b=XCFexChcILPX5kgNZfWikuwXjf8P9TsaCY1gMUvql7oxw+TuE2w8Sy3gZcyoxa+v4s YPcf4vEa+UnmuMLdgO+b07v6LesFHozV7yjnq+Ddud5ZtqoBq/z4NQ/dAEeWuE54UihS +2Eaim/fvXa2plYtKJIcA6DCWdi4liMbKeBEcpnCDI8eez7XW49uzgoMXClz0KLsG7jr AwNqH51jQDTzXsHc698Puj57eecW8sTvbfLxOiOZhmvTgzvgd3nKtiUZnkL9qM5v/qD7 MSnl7jIUx9SiR4CPsgs/pWhFwJTgTb/IGsHEQpqByH3k7ojDffKIV446d8xmCSOUll7+ 3N0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=HhM5qJGPxBSYXZ+6kwCdfI+MuMuQZtYYh38bbR24IOU=; b=VI/PoiQljybi+OJ5FLLmuiHnKyu8iU73oW/1WJAMu2twCObVVLqpl7PSn4xE/fDBHp lXQlDf1bqvWOlEzh99NriIw/BLwMvJyFKmCYqD2zudxpGgke1yHNGdlFufUQ9BiK0ege dNzz0Ql5M+S4v5XObyTpRm7xxWaYqfZWsoT3YPpFSRnS+Mx+XBdePVqPOyvtEtXuN2TM Id1+vWoVeSymPOuPyHlQApB31pFZSAbSUbsR0Dy0uVlm/oLFYZOACd7A/IGzdYjWIbPl kM/sRsBzuxTfMx2ZVCdqOYABfxrAnIzUVgQdzTe0oKcR7MeM6hxXbVuj7id5zVFHuC/7 awhA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Gp587WKz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g7-20020a056a0023c700b0058150179c5bsi18049389pfc.26.2023.01.21.03.30.34; Sat, 21 Jan 2023 03:30:46 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Gp587WKz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229553AbjAULYL (ORCPT <rfc822;forouhar.linux@gmail.com> + 99 others); Sat, 21 Jan 2023 06:24:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229484AbjAULYH (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sat, 21 Jan 2023 06:24:07 -0500 Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 13BB91ABDB; Sat, 21 Jan 2023 03:24:05 -0800 (PST) Received: by mail-ej1-x630.google.com with SMTP id az20so19950973ejc.1; Sat, 21 Jan 2023 03:24:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=HhM5qJGPxBSYXZ+6kwCdfI+MuMuQZtYYh38bbR24IOU=; b=Gp587WKzuBhzbJhcj2m7SGcQd430qD8dtMKAnx6sj6O0QsE49WPZ1CPsvrGhDEqN21 qZXip/tEt+qMo970kUUQvXWWB3wjqXqdeQgawc7EjAes44cIbsCLGYzj3ra2k2sS5rfd O92kJd2s2nwdDUUPHfYKP+f/3WEuaKXaFA7TRQ5G3UBZvYrKxZ+pttGoSCe5hE2LJtyA Vuuf/f40XSE2OqBh9cXCmO4ECeONQlHvPPkeGnJHqecelzlyX6hfOjhSZir4frM+9qD6 FaHNJ4W5LITdhuoo+CFuKFQ3RGri0eMxQb7YhUFmC1t8myqzwX00tRugt0xglht/g7Q0 I1sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HhM5qJGPxBSYXZ+6kwCdfI+MuMuQZtYYh38bbR24IOU=; b=7EQxvRaOSuE5YUb7AdIC5rahMG6CVmyvFhIMWLy0XT7jdKoohgL5pKSPtyXcYauKwP A5jVUF7fNiyzzKqQuCaN90ifM+SFfu4BS192mpwlHs49BIKYyrr2rKOaFjk1p/TBfO6/ okE9WwgcuUgLNpB1EPr0OjgkzMGTMTJE7u8OqZCGD8npyeNmFo33D0TztVoT2TY3Dm/s OTsNfSS//pzpnJsBFaEtyZQErxrbvc/jEWgs8/g+yHBIBgVKmblSUBA5oYkMR6g+EOSM dc8EdTk3vPcgOBHj/DnB6k+adYWV4zq5eR1Aivg/FttHJ637Dn7f1aAPoF1WsF8iOaRX /h9g== X-Gm-Message-State: AFqh2krIxiVIo5CAjPOomByGwqFHvaUOJwukCkls9rEbSRIQVw34uOKj vzHjnjW/F7dkd9ZBnGBYaY+DqAXEY2dRXw== X-Received: by 2002:a17:906:26d7:b0:862:11f6:a082 with SMTP id u23-20020a17090626d700b0086211f6a082mr17533322ejc.17.1674300243568; Sat, 21 Jan 2023 03:24:03 -0800 (PST) Received: from fedora.. ([188.252.220.152]) by smtp.googlemail.com with ESMTPSA id 21-20020a170906319500b0086faa5b06d4sm9236365ejy.181.2023.01.21.03.24.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Jan 2023 03:24:03 -0800 (PST) From: Robert Marko <robimarko@gmail.com> To: agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, srinivas.kandagatla@linaro.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Robert Marko <robimarko@gmail.com> Subject: [PATCH 2/2] arm64: dts: qcom: ipq8074: add QFPROM node Date: Sat, 21 Jan 2023 12:23:58 +0100 Message-Id: <20230121112358.52216-2-robimarko@gmail.com> X-Mailer: git-send-email 2.39.1 In-Reply-To: <20230121112358.52216-1-robimarko@gmail.com> References: <20230121112358.52216-1-robimarko@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1755631475036826390?= X-GMAIL-MSGID: =?utf-8?q?1755631475036826390?= |
Series |
[1/2] dt-bindings: nvmem: qfprom: add IPQ8074 compatible
|
|
Commit Message
Robert Marko
Jan. 21, 2023, 11:23 a.m. UTC
IPQ8074 has efuses like other Qualcomm SoC-s that are required for
determining various HW quirks which will be required later for CPR etc,
so lets add the QFPROM node for start.
Individidual fuses will be added as they are required.
Signed-off-by: Robert Marko <robimarko@gmail.com>
---
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
Comments
On 1/21/2023 4:53 PM, Robert Marko wrote: > IPQ8074 has efuses like other Qualcomm SoC-s that are required for > determining various HW quirks which will be required later for CPR etc, > so lets add the QFPROM node for start. > > Individidual fuses will be added as they are required. > > Signed-off-by: Robert Marko <robimarko@gmail.com> > --- > arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > index 8eba586065a3..f29491f647fe 100644 > --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi > +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > @@ -301,6 +301,13 @@ mdio: mdio@90000 { > status = "disabled"; > }; > > + qfprom: efuse@a4000 { > + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; > + reg = <0x000a4000 0x1000>; From the HW document, I see the overall size of this region is 0x2000, any reason to stick with 0x1000? Thanks, Kathiravan T. > + #address-cells = <1>; > + #size-cells = <1>; > + }; > + > prng: rng@e3000 { > compatible = "qcom,prng-ee"; > reg = <0x000e3000 0x1000>;
On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy <quic_kathirav@quicinc.com> wrote: > > > On 1/21/2023 4:53 PM, Robert Marko wrote: > > IPQ8074 has efuses like other Qualcomm SoC-s that are required for > > determining various HW quirks which will be required later for CPR etc, > > so lets add the QFPROM node for start. > > > > Individidual fuses will be added as they are required. > > > > Signed-off-by: Robert Marko <robimarko@gmail.com> > > --- > > arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > > index 8eba586065a3..f29491f647fe 100644 > > --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi > > +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > > @@ -301,6 +301,13 @@ mdio: mdio@90000 { > > status = "disabled"; > > }; > > > > + qfprom: efuse@a4000 { > > + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; > > + reg = <0x000a4000 0x1000>; > > > From the HW document, I see the overall size of this region is 0x2000, > any reason to stick with 0x1000? Like always, I dont have access to docs and 0x1000 is all I could find downstream being used. Any chance you can share the regions inside of QFPROM, it would be great to use the ECC corrected one if available. Regards, Robert > > Thanks, Kathiravan T. > > > > + #address-cells = <1>; > > + #size-cells = <1>; > > + }; > > + > > prng: rng@e3000 { > > compatible = "qcom,prng-ee"; > > reg = <0x000e3000 0x1000>;
On 1/22/2023 10:29 PM, Robert Marko wrote: > On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy > <quic_kathirav@quicinc.com> wrote: >> >> On 1/21/2023 4:53 PM, Robert Marko wrote: >>> IPQ8074 has efuses like other Qualcomm SoC-s that are required for >>> determining various HW quirks which will be required later for CPR etc, >>> so lets add the QFPROM node for start. >>> >>> Individidual fuses will be added as they are required. >>> >>> Signed-off-by: Robert Marko <robimarko@gmail.com> >>> --- >>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ >>> 1 file changed, 7 insertions(+) >>> >>> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>> index 8eba586065a3..f29491f647fe 100644 >>> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>> @@ -301,6 +301,13 @@ mdio: mdio@90000 { >>> status = "disabled"; >>> }; >>> >>> + qfprom: efuse@a4000 { >>> + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; >>> + reg = <0x000a4000 0x1000>; >> >> From the HW document, I see the overall size of this region is 0x2000, >> any reason to stick with 0x1000? > Like always, I dont have access to docs and 0x1000 is all I could find > downstream > being used. > > Any chance you can share the regions inside of QFPROM, it would be great to use > the ECC corrected one if available. Sorry, What do you refer by "ECC corrected" here? Thanks, Kathiravan T. > > Regards, > Robert >> Thanks, Kathiravan T. >> >> >>> + #address-cells = <1>; >>> + #size-cells = <1>; >>> + }; >>> + >>> prng: rng@e3000 { >>> compatible = "qcom,prng-ee"; >>> reg = <0x000e3000 0x1000>;
On Sun, 22 Jan 2023 at 18:05, Kathiravan Thirumoorthy <quic_kathirav@quicinc.com> wrote: > > > On 1/22/2023 10:29 PM, Robert Marko wrote: > > On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy > > <quic_kathirav@quicinc.com> wrote: > >> > >> On 1/21/2023 4:53 PM, Robert Marko wrote: > >>> IPQ8074 has efuses like other Qualcomm SoC-s that are required for > >>> determining various HW quirks which will be required later for CPR etc, > >>> so lets add the QFPROM node for start. > >>> > >>> Individidual fuses will be added as they are required. > >>> > >>> Signed-off-by: Robert Marko <robimarko@gmail.com> > >>> --- > >>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ > >>> 1 file changed, 7 insertions(+) > >>> > >>> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>> index 8eba586065a3..f29491f647fe 100644 > >>> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>> @@ -301,6 +301,13 @@ mdio: mdio@90000 { > >>> status = "disabled"; > >>> }; > >>> > >>> + qfprom: efuse@a4000 { > >>> + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; > >>> + reg = <0x000a4000 0x1000>; > >> > >> From the HW document, I see the overall size of this region is 0x2000, > >> any reason to stick with 0x1000? > > Like always, I dont have access to docs and 0x1000 is all I could find > > downstream > > being used. > > > > Any chance you can share the regions inside of QFPROM, it would be great to use > > the ECC corrected one if available. > > Sorry, What do you refer by "ECC corrected" here? Isnt there a corrected region in the QFPROM meant for reading? As far as I understand it's protected by FEC. Regards, Robert > > Thanks, Kathiravan T. > > > > > > Regards, > > Robert > >> Thanks, Kathiravan T. > >> > >> > >>> + #address-cells = <1>; > >>> + #size-cells = <1>; > >>> + }; > >>> + > >>> prng: rng@e3000 { > >>> compatible = "qcom,prng-ee"; > >>> reg = <0x000e3000 0x1000>;
On 1/22/2023 10:39 PM, Robert Marko wrote: > On Sun, 22 Jan 2023 at 18:05, Kathiravan Thirumoorthy > <quic_kathirav@quicinc.com> wrote: >> >> On 1/22/2023 10:29 PM, Robert Marko wrote: >>> On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy >>> <quic_kathirav@quicinc.com> wrote: >>>> On 1/21/2023 4:53 PM, Robert Marko wrote: >>>>> IPQ8074 has efuses like other Qualcomm SoC-s that are required for >>>>> determining various HW quirks which will be required later for CPR etc, >>>>> so lets add the QFPROM node for start. >>>>> >>>>> Individidual fuses will be added as they are required. >>>>> >>>>> Signed-off-by: Robert Marko <robimarko@gmail.com> >>>>> --- >>>>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ >>>>> 1 file changed, 7 insertions(+) >>>>> >>>>> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>>>> index 8eba586065a3..f29491f647fe 100644 >>>>> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>>>> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi >>>>> @@ -301,6 +301,13 @@ mdio: mdio@90000 { >>>>> status = "disabled"; >>>>> }; >>>>> >>>>> + qfprom: efuse@a4000 { >>>>> + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; >>>>> + reg = <0x000a4000 0x1000>; >>>> From the HW document, I see the overall size of this region is 0x2000, >>>> any reason to stick with 0x1000? >>> Like always, I dont have access to docs and 0x1000 is all I could find >>> downstream >>> being used. >>> >>> Any chance you can share the regions inside of QFPROM, it would be great to use >>> the ECC corrected one if available. >> Sorry, What do you refer by "ECC corrected" here? > Isnt there a corrected region in the QFPROM meant for reading? > As far as I understand it's protected by FEC. Yes, there are two regions for the QFPROM, the region which you used here is the one used for reading and there is a error correction logic for it and it is size is 8KB not 4KB. Thanks, Kathiravan T. > > Regards, > Robert >> Thanks, Kathiravan T. >> >> >>> Regards, >>> Robert >>>> Thanks, Kathiravan T. >>>> >>>> >>>>> + #address-cells = <1>; >>>>> + #size-cells = <1>; >>>>> + }; >>>>> + >>>>> prng: rng@e3000 { >>>>> compatible = "qcom,prng-ee"; >>>>> reg = <0x000e3000 0x1000>;
On Mon, 23 Jan 2023 at 05:44, Kathiravan Thirumoorthy <quic_kathirav@quicinc.com> wrote: > > > On 1/22/2023 10:39 PM, Robert Marko wrote: > > On Sun, 22 Jan 2023 at 18:05, Kathiravan Thirumoorthy > > <quic_kathirav@quicinc.com> wrote: > >> > >> On 1/22/2023 10:29 PM, Robert Marko wrote: > >>> On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy > >>> <quic_kathirav@quicinc.com> wrote: > >>>> On 1/21/2023 4:53 PM, Robert Marko wrote: > >>>>> IPQ8074 has efuses like other Qualcomm SoC-s that are required for > >>>>> determining various HW quirks which will be required later for CPR etc, > >>>>> so lets add the QFPROM node for start. > >>>>> > >>>>> Individidual fuses will be added as they are required. > >>>>> > >>>>> Signed-off-by: Robert Marko <robimarko@gmail.com> > >>>>> --- > >>>>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++ > >>>>> 1 file changed, 7 insertions(+) > >>>>> > >>>>> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>>>> index 8eba586065a3..f29491f647fe 100644 > >>>>> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>>>> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi > >>>>> @@ -301,6 +301,13 @@ mdio: mdio@90000 { > >>>>> status = "disabled"; > >>>>> }; > >>>>> > >>>>> + qfprom: efuse@a4000 { > >>>>> + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; > >>>>> + reg = <0x000a4000 0x1000>; > >>>> From the HW document, I see the overall size of this region is 0x2000, > >>>> any reason to stick with 0x1000? > >>> Like always, I dont have access to docs and 0x1000 is all I could find > >>> downstream > >>> being used. > >>> > >>> Any chance you can share the regions inside of QFPROM, it would be great to use > >>> the ECC corrected one if available. > >> Sorry, What do you refer by "ECC corrected" here? > > Isnt there a corrected region in the QFPROM meant for reading? > > As far as I understand it's protected by FEC. > > > Yes, there are two regions for the QFPROM, the region which you used > here is the one used for reading and there is a error correction logic > for it and it is size is 8KB not 4KB. Ok, thanks for the info, I will expand the size to 0x2000 then in v2. Regards, Robert > > Thanks, Kathiravan T. > > > > > Regards, > > Robert > >> Thanks, Kathiravan T. > >> > >> > >>> Regards, > >>> Robert > >>>> Thanks, Kathiravan T. > >>>> > >>>> > >>>>> + #address-cells = <1>; > >>>>> + #size-cells = <1>; > >>>>> + }; > >>>>> + > >>>>> prng: rng@e3000 { > >>>>> compatible = "qcom,prng-ee"; > >>>>> reg = <0x000e3000 0x1000>;
diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi index 8eba586065a3..f29491f647fe 100644 --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi @@ -301,6 +301,13 @@ mdio: mdio@90000 { status = "disabled"; }; + qfprom: efuse@a4000 { + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom"; + reg = <0x000a4000 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + }; + prng: rng@e3000 { compatible = "qcom,prng-ee"; reg = <0x000e3000 0x1000>;