From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v2 0/2] SRAM dt binding and fix
Date: Thu, 20 Apr 2023 23:17:33 +0200 [thread overview]
Message-ID: <20230417-ux500-sram-v2-0-6e62ad551faa@linaro.org> (raw)
This adds a DT binding for the U8500 SRAMs.
This patch series also fixes an issue with pool labels that I
saw on U8500.
I suppose SRAM patches will go in through the SoC tree, I kind
of feel that SRAM is a SoC concept and the driver should
actually be in drivers/soc...
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v2:
- Change to just use dev_name() for naming the SRAM partition
when no label is passed.
- Link to v1: https://lore.kernel.org/r/20230417-ux500-sram-v1-0-5924988bb835@linaro.org
---
Linus Walleij (2):
dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM
misc: sram: Generate unique names for subpools
Documentation/devicetree/bindings/sram/sram.yaml | 1 +
drivers/misc/sram.c | 9 +++++----
2 files changed, 6 insertions(+), 4 deletions(-)
---
base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6
change-id: 20230417-ux500-sram-961796726db4
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2023-04-20 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 21:17 Linus Walleij [this message]
2023-04-20 21:17 ` [PATCH v2 1/2] dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM Linus Walleij
2023-04-20 21:17 ` [PATCH v2 2/2] misc: sram: Generate unique names for subpools Linus Walleij
2023-06-18 21:33 ` Dmitry Osipenko
2023-06-19 7:11 ` Linus Walleij
2023-06-20 8:23 ` Dmitry Osipenko
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=20230417-ux500-sram-v2-0-6e62ad551faa@linaro.org \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).