From: paulius.zaleckas@gmail.com (Paulius Zaleckas)
To: linux-arm-kernel@lists.infradead.org
Subject: Submitting patches for new LPC313x machine support
Date: Thu, 12 Nov 2009 13:06:44 +0200 [thread overview]
Message-ID: <4AFBEC44.2050309@gmail.com> (raw)
In-Reply-To: <A2403073D589354FB342892C1CB8F90607DC7C8FA7@EU1RDCRDC1WX029.exi.nxp.com>
On 11/12/2009 04:10 AM, Durgesh Pattamatta wrote:
> Hi All,
[...]
> We have used 'mach-lh7a40x' as an example in accessing registers. But other mach- use
> readl()/writel() routines to access chip registers. Is 'mach-lh7a40x' technique acceptable?
Please use readl()/writel() or even __raw_readl()/__raw_writel()
depending on how bus endianess is/isn't changed.
'mach-lh7a40x' technique hides important details about atomicity of
these register manipulations.
> Regards,
> Durgesh
prev parent reply other threads:[~2009-11-12 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 2:10 Submitting patches for new LPC313x machine support Durgesh Pattamatta
2009-11-12 11:06 ` Paulius Zaleckas [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=4AFBEC44.2050309@gmail.com \
--to=paulius.zaleckas@gmail.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;
as well as URLs for NNTP newsgroup(s).