From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/10] ARM: marvell/dt: add crypto related nodes to armada 370 dtsi
Date: Thu, 27 Aug 2015 17:51:51 +0200 [thread overview]
Message-ID: <20150827175151.23994256@bbrezillon> (raw)
In-Reply-To: <877fog69a7.fsf@free-electrons.com>
Hi Gregory,
On Thu, 27 Aug 2015 17:28:00 +0200
Gregory CLEMENT <gregory.clement@free-electrons.com> wrote:
> Hi Boris and Arnaud,
>
> Boris Brezillon <boris.brezillon@free-electrons.com> writes:
>
> > From: Arnaud Ebalard <arno@natisbad.org>
> >
> > Add crypto related nodes in armada-370.dtsi.
> [...]
> > +
> > + crypto at 90000 {
> > + compatible = "marvell,armada-370-crypto";
> > + reg = <0x90000 0x10000>;
> > + reg-names = "regs";
> > + interrupts = <48>;
> > + clocks = <&gateclk 23>;
> > + clock-names = "cesa0";
> > + marvell,crypto-srams = <&crypto_sram>;
> > + marvell,crypto-sram-size = <0x7e0>;
> > + };
> > + };
> > +
> > + crypto_sram: sa-sram {
> > + compatible = "mmio-sram";
> > + reg = <MBUS_ID(0x09, 0x01) 0 0x800>;
> > + reg-names = "sram";
> > + clocks = <&gateclk 23>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges = <0 MBUS_ID(0x09, 0x01) 0 0x800>;
> > +
> > + idle-sram at 0 {
> > + reg = <0x0 0x20>;
> > + };
>
> So you think at the cpuilde hack using the sram. And you reserved 32
> bytes for it. So indeed it is enough to store the code we need. Could
> you add a little comment about it ?
Sure, I'll add a comment explaining why we reserve a memory region for
idle support.
>
> In mvebu_setup_boot_addr_wa we use mvebu_mbus_add_window_by_id but this
> windows was also added by the code you add. I wonder if it could be a
> problem.
I tested it and it works: apparently you can create different MBUS
windows pointing to the same peripheral (in our case the SRAM).
>
> Maybe we should look for if the idle-sram is present and in this case
> not calling mvebu_mbus_add_window_by_id, but it is not necessary for
> this series.
Hm, I considered reworking the code dealing with this erratum, but
since everything works as is I don't think this is necessary.
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-27 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 8:08 [PATCH 00/10] ARM: marvell/dt: add crypto nodes in existing DTs Boris Brezillon
2015-08-18 8:08 ` [PATCH 01/10] ARM: marvell/dt: add crypto related nodes to armada-xp.dtsi Boris Brezillon
2015-08-18 8:08 ` [PATCH 02/10] ARM: marvell/dt: define crypto SRAM ranges for all armada-xp boards Boris Brezillon
2015-08-18 8:08 ` [PATCH 03/10] ARM: marvell/dt: add crypto related nodes to armada 370 dtsi Boris Brezillon
2015-08-27 15:28 ` Gregory CLEMENT
2015-08-27 15:51 ` Boris Brezillon [this message]
2015-08-18 8:08 ` [PATCH 04/10] ARM: marvell/dt: define crypto SRAM ranges for all armada-370 boards Boris Brezillon
2015-08-18 8:08 ` [PATCH 05/10] ARM: marvell/dt: add crypto related nodes to armada 375 dtsi Boris Brezillon
2015-08-18 8:08 ` [PATCH 06/10] ARM: marvell/dt: define crypto SRAM ranges in armada-375-db.dts Boris Brezillon
2015-08-18 8:08 ` [PATCH 07/10] ARM: marvell/dt: add crypto related nodes to armada 38x dtsi Boris Brezillon
2015-08-18 8:08 ` [PATCH 08/10] ARM: marvell/dt: define crypto SRAM ranges for all armada-38x boards Boris Brezillon
2015-08-18 8:09 ` [PATCH 09/10] ARM: marvell: use new bindings for existing crypto devices Boris Brezillon
2015-08-18 8:09 ` [PATCH 10/10] ARM: marvell: modify Orion and Kirkwoord crypto compatible strings Boris Brezillon
2015-09-22 9:20 ` [PATCH v2 03/10] ARM: marvell/dt: add crypto related nodes to armada 370 dtsi Boris Brezillon
2015-09-29 15:34 ` [PATCH 00/10] ARM: marvell/dt: add crypto nodes in existing DTs Gregory CLEMENT
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=20150827175151.23994256@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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: link
Be 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.