From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v9 0/4] OMAP: McBSP: Use register cache
Date: Mon, 18 Jan 2010 10:07:36 +0200 [thread overview]
Message-ID: <201001181007.36436.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <201001141658.32034.jkrzyszt@tis.icnet.pl>
Hello,
On Thursday 14 January 2010 17:58:29 ext Janusz Krzysztofik wrote:
> Change the way McBSP registers are maintained: store values written to the
> device in a cache in order to make use of those cached values when
> convenient.
>
> This could help for developing the McBSP context save/restore features, as
> well as solve the problem of possible register corruption, experienced on
> OMAP1510 based Amstrad Delta board at least.
>
Please make a followup patch for the unneeded masking of status bits as we
discussed regarding to patch 4.
Acked-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
next prev parent reply other threads:[~2010-01-18 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 15:58 [PATCH v9 0/4] OMAP: McBSP: Use register cache Janusz Krzysztofik
2010-01-14 16:03 ` [PATCH v9 1/4] OMAP: McBSP: Use macros for all register read/write operations Janusz Krzysztofik
2010-01-14 16:07 ` [PATCH v9 2/4] OMAP: McBSP: Modify macros/functions API for easy cache access Janusz Krzysztofik
2010-01-14 16:11 ` [PATCH v9 3/4] OMAP: McBSP: Introduce caching in register write operations Janusz Krzysztofik
2010-01-14 16:13 ` [PATCH v9 4/4] OMAP: McBSP: Use cache when modifying individual register bits Janusz Krzysztofik
2010-01-15 9:11 ` Peter Ujfalusi
2010-01-15 16:43 ` Janusz Krzysztofik
2010-01-18 8:05 ` Peter Ujfalusi
2010-01-18 11:13 ` Jarkko Nikula
2010-01-15 7:42 ` [PATCH v9 0/4] OMAP: McBSP: Use register cache Jarkko Nikula
2010-01-18 8:07 ` Peter Ujfalusi [this message]
2010-02-03 19:49 ` Tony Lindgren
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=201001181007.36436.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=jhnikula@gmail.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.