mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: od@zcrc.me, linux-kernel@vger.kernel.org,
	"H . Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH] memory: jz4780_nemc: Only request IO memory the driver will use
Date: Tue, 28 Jul 2020 14:52:03 +0200	[thread overview]
Message-ID: <RQJ6EQ.X0RPEZHBGXEN1@crapouillou.net> (raw)
In-Reply-To: <20200728092150.GA4437@kozik-lap>



Le mar. 28 juil. 2020 à 11:21, Krzysztof Kozlowski <krzk@kernel.org> a 
écrit :
> On Mon, Jul 27, 2020 at 06:20:34PM +0200, Paul Cercueil wrote:
>>  The driver only uses the registers up to offset 0x54. Since the 
>> EFUSE
>>  registers are in the middle of the NEMC registers, we only request
>>  the registers we will use for now - that way the EFUSE driver can
>>  probe too.
>> 
>>  Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
>>  Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>>  ---
>>   drivers/memory/jz4780-nemc.c | 15 ++++++++++++++-
>>   1 file changed, 14 insertions(+), 1 deletion(-)
>> 
>>  diff --git a/drivers/memory/jz4780-nemc.c 
>> b/drivers/memory/jz4780-nemc.c
>>  index b232ed279fc3..647267ea8c63 100644
>>  --- a/drivers/memory/jz4780-nemc.c
>>  +++ b/drivers/memory/jz4780-nemc.c
>>  @@ -8,6 +8,7 @@
>> 
>>   #include <linux/clk.h>
>>   #include <linux/init.h>
>>  +#include <linux/io.h>
>>   #include <linux/math64.h>
>>   #include <linux/of.h>
>>   #include <linux/of_address.h>
>>  @@ -288,7 +289,19 @@ static int jz4780_nemc_probe(struct 
>> platform_device *pdev)
>>   	nemc->dev = dev;
>> 
>>   	res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>  -	nemc->base = devm_ioremap_resource(dev, res);
>>  +
>>  +	/*
>>  +	 * The driver only uses the registers up to offset 0x54. Since 
>> the EFUSE
>>  +	 * registers are in the middle of the NEMC registers, we only 
>> request
>>  +	 * the registers we will use for now - that way the EFUSE driver 
>> can
>>  +	 * probe too.
>>  +	 */
>>  +	if (!devm_request_mem_region(dev, res->start, 0x54, 
>> dev_name(dev))) {
>>  +		dev_err(dev, "unable to request I/O memory region\n");
>>  +		return -EBUSY;
>>  +	}
>>  +
>>  +	nemc->base = devm_ioremap(dev, res->start, resource_size(res));
> 
> Shouldn't you map only 0x54 size as well?

I can do that.

Cheers,
-Paul



      reply	other threads:[~2020-07-28 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 16:20 Paul Cercueil
2020-07-28  9:21 ` Krzysztof Kozlowski
2020-07-28 12:52   ` Paul Cercueil [this message]

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=RQJ6EQ.X0RPEZHBGXEN1@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=hns@goldelico.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=od@zcrc.me \
    /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

all inboxes | Powered by JetHome®