From: Shawn Guo <shawnguo@kernel.org> To: Martin Kepplinger <martin.kepplinger@puri.sm> Cc: robh@kernel.org, festevam@gmail.com, kernel@pengutronix.de, linux-imx@nxp.com, krzk@kernel.org, kernel@puri.sm, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Angus Ainslie <angus@akkea.ca> Subject: Re: [PATCH v3 4/5] arm64: dts: librem5: protect some partitions of the nor-flash Date: Sun, 7 Mar 2021 21:39:59 +0800 [thread overview] Message-ID: <20210307133958.GH543@dragon> (raw) In-Reply-To: <20210219100439.9428-5-martin.kepplinger@puri.sm> On Fri, Feb 19, 2021 at 11:04:38AM +0100, Martin Kepplinger wrote: > From: Angus Ainslie <angus@akkea.ca> > > These sections should be read only as they contain important data. > > Signed-off-by: Angus Ainslie <angus@akkea.ca> > Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm> > --- > .../boot/dts/freescale/imx8mq-librem5.dtsi | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi b/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > index c2bbbdeb93e3..d39ae27c8e42 100644 > --- a/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > +++ b/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > @@ -258,6 +258,23 @@ > compatible = "jedec,spi-nor"; > reg = <0>; > spi-max-frequency = <1000000>; > + #address-cells = <1>; > + #size-cells = <1>; > + > + partition@0 { > + label = "protected0"; > + reg = <0x0 0x30000>; > + read-only; > + }; > + partition@30000 { > + label = "protected1"; > + reg = <0x30000 0x10000>; > + read-only; > + }; Please have a newline between nodes. I fixed it up when applying. Shawn > + partition@40000 { > + label = "rw"; > + reg = <0x40000 0x1C0000>; > + }; > }; > }; > > -- > 2.20.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org> To: Martin Kepplinger <martin.kepplinger@puri.sm> Cc: robh@kernel.org, festevam@gmail.com, kernel@pengutronix.de, linux-imx@nxp.com, krzk@kernel.org, kernel@puri.sm, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Angus Ainslie <angus@akkea.ca> Subject: Re: [PATCH v3 4/5] arm64: dts: librem5: protect some partitions of the nor-flash Date: Sun, 7 Mar 2021 21:39:59 +0800 [thread overview] Message-ID: <20210307133958.GH543@dragon> (raw) In-Reply-To: <20210219100439.9428-5-martin.kepplinger@puri.sm> On Fri, Feb 19, 2021 at 11:04:38AM +0100, Martin Kepplinger wrote: > From: Angus Ainslie <angus@akkea.ca> > > These sections should be read only as they contain important data. > > Signed-off-by: Angus Ainslie <angus@akkea.ca> > Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm> > --- > .../boot/dts/freescale/imx8mq-librem5.dtsi | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi b/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > index c2bbbdeb93e3..d39ae27c8e42 100644 > --- a/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > +++ b/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > @@ -258,6 +258,23 @@ > compatible = "jedec,spi-nor"; > reg = <0>; > spi-max-frequency = <1000000>; > + #address-cells = <1>; > + #size-cells = <1>; > + > + partition@0 { > + label = "protected0"; > + reg = <0x0 0x30000>; > + read-only; > + }; > + partition@30000 { > + label = "protected1"; > + reg = <0x30000 0x10000>; > + read-only; > + }; Please have a newline between nodes. I fixed it up when applying. Shawn > + partition@40000 { > + label = "rw"; > + reg = <0x40000 0x1C0000>; > + }; > }; > }; > > -- > 2.20.1 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-07 13:41 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-19 10:04 [PATCH v3 0/5] arm64: dts: librem5 phone and devkit dts and config updates Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-19 10:04 ` [PATCH v3 1/5] arm64: dts: imx8mq-librem5-devkit: Drop buck3 startup-ramp-delay Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-19 10:04 ` [PATCH v3 2/5] arm64: dts: librem5: Drop assigned-clocks from SAI2 Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-19 10:04 ` [PATCH v3 3/5] arm64: defconfig: Enable devfreq support for i.MX8MQ Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-19 10:04 ` [PATCH v3 4/5] arm64: dts: librem5: protect some partitions of the nor-flash Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-20 19:14 ` Krzysztof Kozlowski 2021-02-20 19:14 ` Krzysztof Kozlowski 2021-03-07 13:39 ` Shawn Guo [this message] 2021-03-07 13:39 ` Shawn Guo 2021-02-19 10:04 ` [PATCH v3 5/5] arm64: dts: imx8mq-librem5-r2: set nearlevel to 120 Martin Kepplinger 2021-02-19 10:04 ` Martin Kepplinger 2021-02-22 10:28 ` [PATCH v3 0/5] arm64: dts: librem5 phone and devkit dts and config updates Pavel Machek 2021-02-22 10:28 ` Pavel Machek 2021-03-07 13:38 ` Shawn Guo 2021-03-07 13:38 ` Shawn Guo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210307133958.GH543@dragon \ --to=shawnguo@kernel.org \ --cc=angus@akkea.ca \ --cc=devicetree@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=kernel@puri.sm \ --cc=krzk@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=martin.kepplinger@puri.sm \ --cc=robh@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.