All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Ondrej Zary <linux@rainbow-software.org>
Subject: Re: [PATCH 3/4] Add Wolfson Microelectronics WM8776 codec ALSA driver
Date: Tue, 17 Apr 2012 22:16:01 +0200	[thread overview]
Message-ID: <4F8DCF81.4080508@ivitera.com> (raw)
In-Reply-To: <20120417194341.GX6652@opensource.wolfsonmicro.com>

Dne 17.4.2012 21:43, Mark Brown napsal(a):
>
> That's the case in the PC world but obviously this is exactly how
> essentially all embedded systems are built up.  It needs to be very
> clear that this is just legacy code for these old PC sound cards and
> nothing else, nothing about either the directory naming or the changelog
> here suggests that this is anything other than the standard way to add
> support for new CODECs to ALSA.
>
> We usually have to go through a loop of "you need to use the frameworks"
> with new vendors, we need to make the process of figuring out what they
> should do as simple as we can.

Mark, I have always viewed alsa drivers as split to two parts

1. the "PC world" where mostly individual often amateur developers post 
patches improving support of the hardware they own.

2. the ASoC world of embedded solutions, where mostly vendors contribute 
patches for the hardware they produce. All ASoC posts are prefixed by 
ASoC and I have always viewed them as something I do not have to care 
about when fixing and developing stuff for PCI.

Even the until recently highly active intel-hda section does not use any 
of the ASoC infrastructure. If you read the ASoC documentation 
http://alsa-project.org/main/index.php/ASoC, it would not occur to me I 
should be using asoc codecs infrastructure for ice1724 card.

If you want these independent contributors to start using the kernel 
infrastructure common in the ASoC "tree", please tell them clearly on 
the alsa-project.org website, at best directly at 
http://alsa-project.org/main/index.php/Developer_Zone

Working hard on series of patches and being met with cold attitude as 
for not adhering to ASoC standards (quoting the alsa-project.org: "The 
overall project goal of the ALSA System on Chip (ASoC) layer is to 
provide better ALSA support for embedded system on chip procesors") the 
developer had no idea he was supposed to follow is not really 
motivating. And I think every helpful hand and brain counts here.

I can understand the very active ASoC subproject is defining current 
standards for the rest of alsa tree but please tell the currently valid 
rules to all the developers.

Thanks a lot for understanding,

Pavel.

  reply	other threads:[~2012-04-17 20:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 21:18 [RFC PATCH 0/4] snd-ice1712: Add Philips PSC724 Ultimate Edge Ondrej Zary
2012-04-16 21:18 ` [PATCH 1/4] snd-ice1712: add chip_exit callback Ondrej Zary
2012-04-16 21:18 ` [PATCH 2/4] Add Wolfson Microelectronics WM8766 codec ALSA driver Ondrej Zary
2012-04-17 14:59   ` Mark Brown
2012-04-17 16:35     ` Ondrej Zary
2012-04-17 16:54       ` Mark Brown
2012-04-16 21:18 ` [PATCH 3/4] Add Wolfson Microelectronics WM8776 " Ondrej Zary
2012-04-17 15:02   ` Mark Brown
2012-04-17 16:13     ` Ondrej Zary
2012-04-17 16:18       ` Mark Brown
2012-04-17 16:32         ` Takashi Iwai
2012-04-17 16:32           ` [alsa-devel] " Takashi Iwai
2012-04-17 16:50           ` Mark Brown
2012-04-17 16:52             ` Takashi Iwai
2012-04-17 16:52               ` [alsa-devel] " Takashi Iwai
2012-04-17 17:04               ` Mark Brown
2012-04-17 18:06                 ` Takashi Iwai
2012-04-17 18:15                   ` Ondrej Zary
2012-04-17 18:15                     ` [alsa-devel] " Ondrej Zary
2012-04-17 18:22                     ` Mark Brown
2012-04-17 18:22                       ` [alsa-devel] " Mark Brown
2012-04-17 19:14                       ` Takashi Iwai
2012-04-17 19:43                         ` Mark Brown
2012-04-17 19:43                           ` [alsa-devel] " Mark Brown
2012-04-17 20:16                           ` Pavel Hofman [this message]
2012-04-17 21:29                             ` Mark Brown
2012-04-18  9:06                               ` Mark Brown
2012-04-18  9:27                                 ` Pavel Hofman
2012-04-18 10:34                                   ` Mark Brown
2012-04-17 19:12                     ` [alsa-devel] " Takashi Iwai
2012-04-17 21:07                       ` Ondrej Zary
2012-04-17 21:07                         ` [alsa-devel] " Ondrej Zary
2012-04-18  5:54                         ` Takashi Iwai
2012-04-18  5:54                           ` [alsa-devel] " Takashi Iwai
2012-04-18  6:52                           ` Clemens Ladisch
2012-04-18  6:52                             ` [alsa-devel] " Clemens Ladisch
2012-04-16 21:18 ` [PATCH 4/4] snd-ice1712: Add Philips PSC724 Ultimate Edge Ondrej Zary

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=4F8DCF81.4080508@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux@rainbow-software.org \
    --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 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.