All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 2/2] ALSA: hda - Drop AZX_DCAPS_ALIGN_BUFSIZE
Date: Wed, 03 Dec 2014 10:18:29 +0100	[thread overview]
Message-ID: <s5hh9xd6qhm.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAN8cciZ6xf9EQUG5s7QEOGU8j=bKXfTN1PukoS7C3TkbVNGFdQ@mail.gmail.com>

At Wed, 3 Dec 2014 17:13:45 +0800,
Raymond Yau wrote:
> 
> >
> > We introduced AZX_DCAPS_ALIGN_BUFSIZE to explicity show that the
> > controller needs the alignment, with a slight hope that the buffer
> > size alignment will be disabled as default in future.  But the reality
> > tells that most chips need the buffer size alignment, and it'll be
> > likely enabled in future, too.
> >
> > This patch drops AZX_DCAPS_ALIGN_BUFSIZE to give back one more
> > previous DCAPS bit for future use.  At the same time, rename
> > AZX_DCAPS_BUFSIZE with AZX_DCAPS_NO_ALIGN_BUFSIZE for avoiding
> > confusion.
> >
> > AZX_DCAPS_ALIGN_BUFSIZE are still kept (but commented out) in each
> > DCAPS presets for a purpose as markers.
> 
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=2ae66c26550cd94b0e2606a9275eb0ab7070ad0e
> 
> Does it mean that there are still a few  hda controllers support arbitrary
> period size or no hda controller support arbitrary period size ?

Most of Intel chips except for HDMI/DP work with arbitrary size.


Takashi

      reply	other threads:[~2014-12-03  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  9:02 [PATCH 1/2] ALSA: hda - Define the DCAPS preset for the old Intel chipsets Takashi Iwai
2014-12-03  9:02 ` [PATCH 2/2] ALSA: hda - Drop AZX_DCAPS_ALIGN_BUFSIZE Takashi Iwai
2014-12-03  9:13   ` Raymond Yau
2014-12-03  9:18     ` Takashi Iwai [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=s5hh9xd6qhm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.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.