From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2.3/5 v2] ARM: mach-shmobile: add bonito board support.
Date: Mon, 07 Nov 2011 04:48:11 +0000 [thread overview]
Message-ID: <20111107044811.GC3927@linux-sh.org> (raw)
In-Reply-To: <87zkg8rcxs.wl%kuninori.morimoto.gx@renesas.com>
On Sun, Nov 06, 2011 at 04:30:59PM -0800, Kuninori Morimoto wrote:
> diff --git a/arch/arm/configs/bonito_defconfig b/arch/arm/configs/bonito_defconfig
> new file mode 100644
> index 0000000..adb4fc3
> --- /dev/null
> +++ b/arch/arm/configs/bonito_defconfig
> @@ -0,0 +1,978 @@
> +#
> +# Automatically generated file; DO NOT EDIT.
> +# Linux/arm 3.1.0-rc3 Kernel Configuration
> +#
We're only interested in defconfig fragments.
See c2330e286f68f1c408b4aa6515ba49d57f05beae for a script you can use to
trim this down.
> +/*
> + * FPGA
> + */
> +#define A1MDSR 0x10E0
> +#define BVERR 0x1100
> +u16 fpga_read(u32 offset)
> +{
> + return __raw_readw(0xf0003000 + offset);
> +}
> +
> +void fpga_write(u32 offset, u16 val, u16 mask)
> +{
> + u16 tmp;
> +
> + tmp = fpga_read(offset);
> + tmp = (tmp & ~mask) | (val & mask);
> + __raw_writew(tmp, 0xf0003000 + offset);
> +}
> +
You may want a more descriptive name, like bonito_fpga_read/write() or
so. This also seems like something you are going to want in a header and
inlined, rather than part of the global namespace (especially with such
generic naming).
The rest looks fine to me.
prev parent reply other threads:[~2011-11-07 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 0:30 [PATCH 2.3/5 v2] ARM: mach-shmobile: add bonito board support Kuninori Morimoto
2011-11-07 4:48 ` Paul Mundt [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=20111107044811.GC3927@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.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).