[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141030112243.GV18557@sirena.org.uk>
Date: Thu, 30 Oct 2014 11:22:43 +0000
From: Mark Brown <broonie@...nel.org>
To: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
Cc: Huan Wang <alison.wang@...escale.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"tiwai@...e.de" <tiwai@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"perex@...ex.cz" <perex@...ex.cz>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] audio: sai: Add Power Management support
On Thu, Oct 30, 2014 at 03:30:40AM +0000, Li.Xiubo@...escale.com wrote:
> One more thing, if the device is not performance critical, then shouldn't we
> Take care of the cache memory consumption to determine using flat or rbtree
> Type ?
Yes, it's always fine to use a rbtree if it makes sense - it was just an
unusual choice for a device like this that didn't seem to be discussed.
Depending on the register map a flat cache can actually be more memory
efficient sometimes since there's some overhead for the rbtree data
structures, if you've just got one block of registers with no gaps a
flat cache is going to be a win there.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists