From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "Varadarajan, Charu Latha" <charu@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Syed, Rafiuddin" <rafiuddin.syed@ti.com>
Subject: Re: [PATCH] OMAP3: Fix McBSP poll read and write for 32bit reg access
Date: Thu, 15 Oct 2009 10:25:30 +0300 [thread overview]
Message-ID: <200910151025.30493.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02BB37CDA1@dbde02.ent.ti.com>
On Thursday 15 October 2009 09:10:54 ext Shilimkar, Santosh wrote:
> > > > > > - writew(buf, base + OMAP_MCBSP_REG_DXR1);
> > > > > > + OMAP_MCBSP_WRITE(base, DXR, buf);
> > > > >
> > > > > Why do you need this? Is writew()/readw() not doing 16 bit
> > > > > operations ?
> > > >
> > > > The intension is to use 32 bit access and not 16 bit access
> > >
> > > Use readl() / writel() then.
> >
> > Yes, OMAP_MCBSP_WRITE macro makes use of readl() / writel() for OMAP3
>
> Good!! Then get rid of this macro and directly use kernel standard
> API- readl() / writel() --
Well, OMAP1 and OMAP2 still has 16 bit registers in McBSP.
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-15 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E0D41E29EB0DAC4E9F3FF173962E9E940253DAF74A@dbde02.ent.ti.com>
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02BA31ADB2@dbde02.ent.ti.com>
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02BB255576@dbde02.ent.ti.com>
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02BA31ADB7@dbde02.ent.ti.com>
[not found] ` <19F8576C6E063C45BE387C64729E73940436DB248C@dbde02.ent.ti.com>
2009-10-15 5:29 ` [PATCH] OMAP3: Fix McBSP poll read and write for 32bit reg access Varadarajan, Charu Latha
2009-10-15 6:10 ` Shilimkar, Santosh
2009-10-15 7:25 ` Peter Ujfalusi [this message]
2009-10-15 7:30 ` Shilimkar, Santosh
[not found] ` <5A47E75E594F054BAF48C5E4FC4B92AB030A46D070@dbde02.ent.ti.com>
2009-10-15 11:57 ` Varadarajan, Charu Latha
[not found] <E0D41E29EB0DAC4E9F3FF173962E9E940253DAF724@dbde02.ent.ti.com>
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02BA31ADB4@dbde02.ent.ti.com>
[not found] ` <EAF47CD23C76F840A9E7FCE10091EFAB02BA31ADB8@dbde02.ent.ti.com>
[not found] ` <19F8576C6E063C45BE387C64729E73940436DB248F@dbde02.ent.ti.com>
2009-10-15 5:32 ` Varadarajan, Charu Latha
[not found] <E0D41E29EB0DAC4E9F3FF173962E9E940253DAF770@dbde02.ent.ti.com>
2009-10-14 11:01 ` Varadarajan, Charu Latha
2009-10-14 9:30 charu
2009-10-14 9:52 ` vimal singh
2009-10-14 10:31 ` G, Manjunath Kondaiah
2009-10-14 10:05 ` Shilimkar, Santosh
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=200910151025.30493.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rafiuddin.syed@ti.com \
--cc=santosh.shilimkar@ti.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.