From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ben Dooks <ben-linux@fluff.org>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/3] h1940: use gpiolib for latch access
Date: Tue, 24 Aug 2010 17:04:00 +0300 [thread overview]
Message-ID: <201008241704.07384.anarsoul@gmail.com> (raw)
In-Reply-To: <201008241549.51513.marek.vasut@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1016 bytes --]
В сообщении от 24 августа 2010 16:49:51 автор Marek Vasut написал:
> > + ret = gpio_request(H1940_LATCH_BLUETOOTH_POWER, dev_name(&pdev-
>dev));
>
> This should contain the name of the GPIO, not dev_name I assume.
Ok
> > + if (ret) {
> > + gpio_free(S3C2410_GPH(1));
>
> What's this constant (the 1) here ? Maybe some sane #define wont hurt or
> comment around it.
GPH(1) specifies gpio bit, that's not magic constant.
> > +#ifndef __ASSEMBLY__
> > +#define H1940_LATCH ((void __force __iomem *)0xF8000000)
> > +#else
> > +#define H1940_LATCH 0xF8000000
> > +#endif
>
> Is the __ASSEMBLY__ really needed ? You can establish mapping when the
> kernel boots (looks like you're doing that already) but then use
> __raw_readX __raw_writeX to access that space instead of this stuff above.
Uh, I just moved this code from another file, not sure if __ASSEMBLY__ is
necessary, I'll remove it if it is not.
Thanks for review :)
Regards
Vasily
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] h1940: use gpiolib for latch access
Date: Tue, 24 Aug 2010 17:04:00 +0300 [thread overview]
Message-ID: <201008241704.07384.anarsoul@gmail.com> (raw)
In-Reply-To: <201008241549.51513.marek.vasut@gmail.com>
? ????????? ?? 24 ??????? 2010 16:49:51 ????? Marek Vasut ???????:
> > + ret = gpio_request(H1940_LATCH_BLUETOOTH_POWER, dev_name(&pdev-
>dev));
>
> This should contain the name of the GPIO, not dev_name I assume.
Ok
> > + if (ret) {
> > + gpio_free(S3C2410_GPH(1));
>
> What's this constant (the 1) here ? Maybe some sane #define wont hurt or
> comment around it.
GPH(1) specifies gpio bit, that's not magic constant.
> > +#ifndef __ASSEMBLY__
> > +#define H1940_LATCH ((void __force __iomem *)0xF8000000)
> > +#else
> > +#define H1940_LATCH 0xF8000000
> > +#endif
>
> Is the __ASSEMBLY__ really needed ? You can establish mapping when the
> kernel boots (looks like you're doing that already) but then use
> __raw_readX __raw_writeX to access that space instead of this stuff above.
Uh, I just moved this code from another file, not sure if __ASSEMBLY__ is
necessary, I'll remove it if it is not.
Thanks for review :)
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100824/f6e24406/attachment-0001.sig>
next prev parent reply other threads:[~2010-08-24 14:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 15:00 [PATCH 0/3] h1940 series Vasily Khoruzhick
2010-08-19 15:00 ` Vasily Khoruzhick
2010-08-19 15:00 ` [PATCH 1/3] h1940: use gpiolib for latch access Vasily Khoruzhick
2010-08-19 15:00 ` Vasily Khoruzhick
2010-08-24 13:49 ` Marek Vasut
2010-08-24 13:49 ` Marek Vasut
2010-08-24 14:04 ` Vasily Khoruzhick [this message]
2010-08-24 14:04 ` Vasily Khoruzhick
2010-08-24 14:40 ` Marek Vasut
2010-08-24 14:40 ` Marek Vasut
2010-08-24 14:50 ` Vasily Khoruzhick
2010-08-24 14:50 ` Vasily Khoruzhick
2010-08-24 15:04 ` Marek Vasut
2010-08-24 15:04 ` Marek Vasut
2010-09-02 10:53 ` Russell King - ARM Linux
2010-09-02 10:53 ` Russell King - ARM Linux
2010-08-19 15:00 ` [PATCH 2/3] h1940: fix h1940-bluetooth compilation Vasily Khoruzhick
2010-08-19 15:00 ` Vasily Khoruzhick
2010-08-24 13:50 ` Marek Vasut
2010-08-24 13:50 ` Marek Vasut
2010-08-24 13:57 ` Vasily Khoruzhick
2010-08-24 13:57 ` Vasily Khoruzhick
2010-08-24 14:00 ` Marek Vasut
2010-08-24 14:00 ` Marek Vasut
2010-08-19 15:00 ` [PATCH 3/3] h1940: implement mmc_power function Vasily Khoruzhick
2010-08-19 15:00 ` Vasily Khoruzhick
2010-08-24 13:52 ` Marek Vasut
2010-08-24 13:52 ` Marek Vasut
2010-08-24 14:00 ` Vasily Khoruzhick
2010-08-24 14:00 ` Vasily Khoruzhick
2010-08-24 14:01 ` Marek Vasut
2010-08-24 14:01 ` Marek Vasut
2010-08-24 14:21 ` Vasily Khoruzhick
2010-08-24 14:21 ` Vasily Khoruzhick
2010-08-24 14:41 ` Marek Vasut
2010-08-24 14:41 ` Marek Vasut
2010-08-24 14:56 ` Vasily Khoruzhick
2010-08-24 14:56 ` Vasily Khoruzhick
2010-08-24 15:07 ` Marek Vasut
2010-08-24 15:07 ` Marek Vasut
2010-08-24 15:19 ` Vasily Khoruzhick
2010-08-24 15:19 ` Vasily Khoruzhick
2010-08-24 13:24 ` [PATCH 0/3] h1940 series Vasily Khoruzhick
2010-08-24 13:24 ` Vasily Khoruzhick
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=201008241704.07384.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marek.vasut@gmail.com \
/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.