From: Ahmad Fatoum <a.fatoum@pengutronix.de> To: barebox@lists.infradead.org Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, rcz@pengutronix.de Subject: [PATCH 1/4] nvmem: rmem: get, don't request, memory region Date: Thu, 9 Jun 2022 07:43:39 +0200 [thread overview] Message-ID: <20220609054342.661505-2-a.fatoum@pengutronix.de> (raw) In-Reply-To: <20220609054342.661505-1-a.fatoum@pengutronix.de> nvmem-rmem is a compatible for reserved memory entries, so the driver can't expect exclusive access to this region. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> --- drivers/nvmem/rmem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/nvmem/rmem.c b/drivers/nvmem/rmem.c index cd735e5ef39d..b9331f48ffac 100644 --- a/drivers/nvmem/rmem.c +++ b/drivers/nvmem/rmem.c @@ -31,7 +31,7 @@ static int rmem_probe(struct device_d *dev) struct resource *mem; struct rmem *priv; - mem = dev_request_mem_resource(dev, 0); + mem = dev_get_resource(dev, IORESOURCE_MEM, 0); if (IS_ERR(mem)) return PTR_ERR(mem); -- 2.30.2 _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-06-09 5:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 5:43 [PATCH 0/4] of: request reserved memory regions so other code can't Ahmad Fatoum 2022-06-09 5:43 ` Ahmad Fatoum [this message] 2022-06-09 5:43 ` [PATCH 2/4] of: reserve: mark runtime firmware code regions specially Ahmad Fatoum 2022-06-09 8:05 ` Sascha Hauer 2022-06-09 8:17 ` Ahmad Fatoum 2022-06-09 5:43 ` [PATCH 3/4] of: add of_get_reserve_map stub for !CONFIG_OFTREE Ahmad Fatoum 2022-06-09 9:14 ` Sascha Hauer 2022-06-09 5:43 ` [PATCH 4/4] of: request reserved memory regions so other code can't Ahmad Fatoum 2022-06-09 8:31 ` [PATCH] fixup! " Ahmad Fatoum 2022-06-09 8:31 ` [PATCH 4/4] " Sascha Hauer 2022-06-09 8:36 ` Ahmad Fatoum
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=20220609054342.661505-2-a.fatoum@pengutronix.de \ --to=a.fatoum@pengutronix.de \ --cc=barebox@lists.infradead.org \ --cc=rcz@pengutronix.de \ --subject='Re: [PATCH 1/4] nvmem: rmem: get, don'\''t request, memory region' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox