All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	patches@opensource.wolfsonmicro.com,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: soc-core: Remove display_register() callback
Date: Wed, 02 Feb 2011 14:54:33 +0000	[thread overview]
Message-ID: <1296658473.4393.2.camel@dplaptop.localdomain> (raw)
In-Reply-To: <AANLkTing5zryWWt4HZHGUd15-6mrxpnRwA8EEiE8DGem@mail.gmail.com>

On Wed, 2011-02-02 at 09:50 -0500, jonsmirl@gmail.com wrote:
> On Wed, Feb 2, 2011 at 5:23 AM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Wed, Feb 02, 2011 at 10:20:54AM +0000, Dimitris Papastamos wrote:
> >> Remove the display_register() callback as there are no users of it
> >> in the upstream kernel and makes it difficult to unify the format
> >> of the codec_reg file.
> >
> >> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
> >
> > This was rather strongly requested for some devices with extremely large
> > registers (128 bits at least IIRC) which may eventually make it to
> > mainline.  It seems better to just have some sort of fallback for those
> > devices, if it causes output problems people can always fix those.
> >
> 
> TI Codec devices have two problems:
> 1) large registers - up to 128 bits
> 2) sparse register maps - big gaps between valid register addresses.

Yes, I've dropped the patch.

Thanks,
Dimitris

      parent reply	other threads:[~2011-02-02 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 10:20 [PATCH] ASoC: soc-core: Remove display_register() callback Dimitris Papastamos
2011-02-02 10:23 ` Mark Brown
2011-02-02 14:50   ` jonsmirl
2011-02-02 14:51     ` Mark Brown
2011-02-02 14:54     ` Dimitris Papastamos [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=1296658473.4393.2.camel@dplaptop.localdomain \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jonsmirl@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=patches@opensource.wolfsonmicro.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.