Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jernej Skrabec <jernej.skrabec@siol.net>,
	Jonas Karlman <jonas@kwiboo.se>,
	Neil Armstrong <narmstrong@baylibre.com>,
	alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org,
	Andrzej Hajda <a.hajda@samsung.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [alsa-devel] [PATCH for-5.6 0/2] drm/bridge: dw-hdmi: PCM API updates
Date: Thu, 9 Jan 2020 10:25:43 +0000	[thread overview]
Message-ID: <20200109102543.GN25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <s5h8smhm1vy.wl-tiwai@suse.de>

On Thu, Jan 09, 2020 at 10:10:09AM +0100, Takashi Iwai wrote:
> On Tue, 10 Dec 2019 16:45:34 +0100,
> Takashi Iwai wrote:
> > 
> > Hi,
> > 
> > this is a patch set for updating ALSA PCM API usages in dw-hdmi
> > driver.  I already tried to "fix" the driver some time ago but it was
> > utterly wrong.  So this is a combination of the revised patch and
> > another cleanup patch.
> > 
> > The first one is to change the buffer allocation mechanism in the
> > driver to the manual allocation of the h/w buffer and the automatic
> > allocation of PCM stream buffers via the new standard API.  The
> > significant change is that size of the h/w buffer isn't no longer
> > controlled via ALSA preallocation proc file but rather via the new
> > module option (if any).
> > 
> > The second one is a oneliner patch just to remove the superfluous PCM
> > ops.
> > 
> > Both need the ALSA PCM core changes in 5.5-rc1, so please apply them
> > on top of 5.5-rc1 or later.  Or, just let me know if I should apply
> > them through sound git tree.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> > ===
> > 
> > Takashi Iwai (2):
> >   drm/bridge: dw-hdmi: Follow the standard ALSA memalloc way
> >   drm/bridge: dw-hdmi: Drop superfluous ioctl PCM ops
> 
> Any chance for reviewing these patches?
> 
> Since this driver is the only one who is still using the old ALSA
> vmalloc API, I'd like to change it and drop the old API in 5.6.

It isn't something I can even test at the moment; I have the platforms
but no TV to connect them to.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      parent reply	other threads:[~2020-01-09 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 15:45 [alsa-devel] [PATCH for-5.6 0/2] drm/bridge: dw-hdmi: PCM API updates Takashi Iwai
2019-12-10 15:45 ` [alsa-devel] [PATCH for-5.6 1/2] drm/bridge: dw-hdmi: Follow the standard ALSA memalloc way Takashi Iwai
2019-12-10 15:45 ` [alsa-devel] [PATCH for-5.6 2/2] drm/bridge: dw-hdmi: Drop superfluous ioctl PCM ops Takashi Iwai
2020-01-09  9:10 ` [alsa-devel] [PATCH for-5.6 0/2] drm/bridge: dw-hdmi: PCM API updates Takashi Iwai
2020-01-09 10:18   ` Neil Armstrong
2020-01-09 10:25   ` Russell King - ARM Linux admin [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=20200109102543.GN25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=narmstrong@baylibre.com \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox