From: Rene Herman <rene.herman@keyaccess.nl>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/2] ad1848: separate header for registers definition
Date: Sun, 15 Jun 2008 18:07:02 +0200 [thread overview]
Message-ID: <48553E26.1070100@keyaccess.nl> (raw)
In-Reply-To: <20080615124121.781d8aff.krzysztof.h1@poczta.fm>
On 15-06-08 12:41, Krzysztof Helt wrote:
> This patch is a start combining ad1848_lib and cs4231_lib
> functionality. My approach is to make the cs4231_lib module
> use the ad1848_lib module. This should allow removing
> most of identical functions from the cs4231_lib and use
> the functions from the ad1848_lib directly.
>
> If this approach is not a good idea, please drop the patch.
>
> My current plan is to reuse the ad1848 register constants
> in the cs423x code and remove duplicated cs4231 constants.
> This should make the ad1848_lib and cs4231_lib easier to
> compare for differences.
>
> The next step is to use the snd_cs4231 structure instead of
> the snd_ad1848 structure inside the ad1848_lib. This will make
> functions from the ad1848_lib taking the same arguments
> as the functions in the cs4231_lib.
>
> The last step would be to export needed functions from the
> ad1848_lib and use them directly in the cs4231_lib.
>
> This should reduce the size of the cs4231_lib while preserving
> smaller the ad1848_lib for driver which uses only ad1848
> functionality.
I believe it would be going a bit overboard to actually make these two
dependent libs. Unification would seem a good plan probably but as far
as I'm concerned one lib to drive all these chips should do really.
cs4321_lib isn't all that much bigger. The seperation does make sense at
the source level, but I'd personally go for a single library module (*)
built from multiple source files. These chips aren't used by embedded
these days and even if they were the sizes we are talking about are
laughable in today's terms.
At a later stage, cs4236_lib could be folded in as well...
(*) perhaps under sound/drivers/wss, or sound/isa/lib/wss (or if you
don't care for the wss name, something else; the location is more the
point).
Rene.
next prev parent reply other threads:[~2008-06-15 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 10:41 [PATCH 1/2] ad1848: separate header for registers definition Krzysztof Helt
2008-06-15 16:07 ` Rene Herman [this message]
2008-06-15 17:26 ` Krzysztof Helt
2008-06-16 10:40 ` Takashi Iwai
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=48553E26.1070100@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=krzysztof.h1@poczta.fm \
/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.