From: subhasish@mistralsolutions.com (Subhasish Ghosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 01/11] mfd: add pruss mfd driver.
Date: Wed, 27 Apr 2011 18:48:54 +0530 [thread overview]
Message-ID: <5BAE2D6F9E6047C19B6BE8FF26F7270B@subhasishg> (raw)
In-Reply-To: <20110427091252.GP17290@n2100.arm.linux.org.uk>
My problem is, I am doing something like this:
s32 pruss_writel_multi(struct device *dev, u32 offset,
u32 *pdatatowrite, u16 wordstowrite)
{
struct pruss_priv *pruss = dev_get_drvdata(dev->parent);
u32 __iomem *paddresstowrite;
u16 i;
paddresstowrite = pruss->ioaddr + offset;
for (i = 0; i < wordstowrite; i++)
iowrite32(*pdatatowrite++, paddresstowrite++);
return 0;
}
So, if I make paddresstowrite as void, it will not work.
The above implementation does not generate any sparse errors though.
> On Wed, Apr 27, 2011 at 09:29:59AM +0200, Marc Kleine-Budde wrote:
>> On 04/27/2011 08:39 AM, Subhasish Ghosh wrote:
>> > - Is it ok to have u32 etc for __iomem cookie ?
>>
>> no - "void __iomem *" is "void __iomem *"
>
> Actually, it is _provided_ you don't directly dereference it. You can
> then do pointer arithmetic on it in the usual way - which is about the
> only valid thing to do with an __iomem pointer. The voidness just acts
> as an additional check against direct dereferences of this.
>
> The important thing though is that the code passes sparse checks.
next prev parent reply other threads:[~2011-04-27 13:18 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 12:08 [PATCH v4 00/11] pruss mfd drivers Subhasish Ghosh
2011-04-22 11:50 ` [PATCH v4 08/11] tty: add pruss SUART driver Subhasish Ghosh
2011-04-25 21:20 ` Greg KH
2011-04-26 6:51 ` Nori, Sekhar
2011-04-26 12:45 ` Greg KH
2011-04-27 5:23 ` Subhasish Ghosh
2011-04-27 11:19 ` Nori, Sekhar
2011-04-27 13:15 ` Subhasish Ghosh
2011-04-27 17:50 ` Nori, Sekhar
2011-05-02 8:34 ` Subhasish Ghosh
2011-05-02 17:15 ` Nori, Sekhar
2011-05-10 10:54 ` Subhasish Ghosh
2011-05-10 13:13 ` Nori, Sekhar
2011-05-13 12:10 ` Subhasish Ghosh
2011-05-09 13:39 ` Subhasish Ghosh
2011-05-09 13:46 ` Alan Cox
2011-05-09 13:50 ` Subhasish Ghosh
2011-05-09 13:55 ` Alan Cox
2011-05-10 6:17 ` Subhasish Ghosh
2011-05-10 13:32 ` Alan Cox
2011-05-11 7:01 ` Subhasish Ghosh
2011-05-11 10:35 ` Alan Cox
2011-04-22 12:08 ` [PATCH v4 01/11] mfd: add pruss mfd driver Subhasish Ghosh
2011-04-22 16:00 ` Marc Kleine-Budde
2011-04-27 6:39 ` Subhasish Ghosh
2011-04-27 7:29 ` Marc Kleine-Budde
2011-04-27 9:12 ` Russell King - ARM Linux
2011-04-27 13:18 ` Subhasish Ghosh [this message]
2011-04-27 13:35 ` Marc Kleine-Budde
2011-04-28 7:22 ` Subhasish Ghosh
2011-04-28 7:46 ` Arnd Bergmann
2011-04-27 13:16 ` Arnd Bergmann
2011-04-27 13:38 ` Subhasish Ghosh
2011-04-27 14:05 ` Arnd Bergmann
2011-04-28 7:17 ` Subhasish Ghosh
2011-04-28 7:35 ` Arnd Bergmann
2011-05-04 7:18 ` Subhasish Ghosh
2011-05-04 13:44 ` Arnd Bergmann
2011-05-04 14:38 ` Nori, Sekhar
2011-05-05 13:25 ` Subhasish Ghosh
2011-05-05 14:12 ` Arnd Bergmann
2011-05-10 9:53 ` Subhasish Ghosh
2011-05-10 21:44 ` Arnd Bergmann
2011-05-11 9:28 ` Subhasish Ghosh
2011-05-11 20:03 ` Arnd Bergmann
2011-05-13 10:55 ` Subhasish Ghosh
2011-05-14 16:01 ` Mark Brown
2011-05-14 20:33 ` Arnd Bergmann
2011-05-14 22:14 ` Mark Brown
2011-05-15 9:33 ` Arnd Bergmann
2011-05-16 6:06 ` Subhasish Ghosh
2011-05-23 15:30 ` Arnd Bergmann
2011-05-24 12:17 ` Subhasish Ghosh
2011-05-24 12:40 ` Arnd Bergmann
2011-05-24 13:43 ` Greg KH
2011-05-30 13:25 ` Subhasish Ghosh
2011-05-30 14:02 ` Greg KH
2011-05-30 14:38 ` Subhasish Ghosh
2011-05-30 14:04 ` Arnd Bergmann
2011-05-30 14:13 ` Subhasish Ghosh
2011-05-30 14:43 ` Arnd Bergmann
2011-05-30 15:28 ` Subhasish Ghosh
2011-05-22 20:24 ` Samuel Ortiz
2011-05-22 20:21 ` Samuel Ortiz
2011-05-23 15:13 ` Arnd Bergmann
2011-04-22 12:08 ` [PATCH v4 02/11] da850: add pruss clock Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 03/11] da850: pruss platform specific additions Subhasish Ghosh
2011-04-26 11:06 ` Sergei Shtylyov
2011-04-27 6:43 ` Subhasish Ghosh
2011-04-27 10:05 ` Sergei Shtylyov
2011-04-27 10:19 ` Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 04/11] da850: pruss board " Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 05/11] mfd: pruss SUART private data Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 06/11] da850: pruss SUART board specific additions Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 07/11] da850: pruss SUART platform " Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 09/11] mfd: pruss CAN private data Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 10/11] da850: pruss CAN platform specific additions Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 11/11] da850: pruss CAN board " Subhasish Ghosh
2011-04-22 16:03 ` Marc Kleine-Budde
2011-04-26 10:57 ` Sergei Shtylyov
2011-04-27 7:03 ` Subhasish Ghosh
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=5BAE2D6F9E6047C19B6BE8FF26F7270B@subhasishg \
--to=subhasish@mistralsolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox