From: Pavel Hofman <pavel.hofman@insite.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Rainer Zimmermann <mail@lightshed.de>
Subject: Re: PATCH - ESI Juli driver
Date: Mon, 17 Mar 2008 09:57:49 +0100 [thread overview]
Message-ID: <47DE328D.1080009@insite.cz> (raw)
In-Reply-To: <s5hod9du6gb.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Sun, 16 Mar 2008 13:57:24 +0100,
> Pavel Hofman wrote:
>> Hi Takashi,
>
> I feel there are too many additional callbacks in your patch.
> Since we don't need too subtle tuning, can we simplify this?
There are only two callbacks which Juli does not redefine. These could
be removed. Though I felt it was cleaner to have all the clock-specific
stuff potentially redefinable for other cards.
I did not want to copy/paste any algorithmical code from ice1724.c to
juli.c as it complicates future maintenance. Now, the vt1724 code in
ice1724.c is pretty much about general algorhitms, specific routines are
in stdclock_... I tested the original clock with Prodigy192 which
provided testing analog/SPDIF signals. There are no functional changes.
>
> Regarding the separate rate setting for each stream, we should
> consider about Maya44 support, too.
I have been following the discussion. Unfortunately, I did not get to
see any patch of ice1724.c, iirc the last patch included the whole
modified ice1724.c copied to alsa-driver.
Rainer, what are the changes?
Now each card can specify its own stream parameters. E.g. Juli has a
modified list of available frequencies for analog streams.
>
>> The driver is tested, only analog-in and digital-in monitors are not
>> working. I have coded according to manufacturer's documentation, the
>> same procedure is in OSS Juli driver. I described the issue in detail in
>> the code, perhaps someone will do more research.
>>
>> The card itself has no HW master volume control. It would have to be
>> implemented as a virtual control manipulating internal values of PCM and
>> monitor volume controls. I will take a look at it later. For now,
>> perhaps we could rename the PCM Volume to Master Volume, as most people
>> will not need the monitoring anyway. I will leave it to your decision.
>>
>> Signed-off-by: Pavel Hofman <dustin@seznam.cz>
>>
>> * moving all clock-specific code to card-specific routines
>> * support for ESI Juli
>> * to-be-researched - monitoring of analog/digital inputs
>> * missing - master volume control, will have to be implemented as
>> virtual, no HW support.
>
> vmaster can be used for this now. It was moved to core directory
> after 1.0.16 release.
Thanks, I did not know about vmaster. I will try to implement it tonight.
The Juli support is one of the very called-for features, I guess it
would be a pitty to keep a functional patch out of repository.
Thanks,
Pavel.
next prev parent reply other threads:[~2008-03-17 8:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 12:57 PATCH - ESI Juli driver Pavel Hofman
2008-03-17 7:59 ` Takashi Iwai
2008-03-17 8:57 ` Pavel Hofman [this message]
2008-03-17 9:24 ` Takashi Iwai
2008-03-17 9:37 ` Pavel Hofman
2008-03-17 13:04 ` Takashi Iwai
2008-03-17 14:08 ` Pavel Hofman
2008-03-17 15:17 ` Takashi Iwai
2008-03-17 15:50 ` Pavel Hofman
2008-03-17 15:59 ` Takashi Iwai
2008-03-17 16:39 ` Pavel Hofman
2008-03-17 23:28 ` Pavel Hofman
2008-03-18 6:56 ` PATCH - ESI Juli driver - removed debugs Pavel Hofman
2008-03-18 14:59 ` Takashi Iwai
2008-03-18 15:59 ` Pavel Hofman
2008-03-20 14:20 ` Pavel Hofman
2008-03-20 21:49 ` PATCH - ESI Juli driver - OK Pavel Hofman
2008-03-18 19:24 ` PATCH - ESI Juli driver - works OK Pavel Hofman
2008-03-20 11:37 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2008-03-17 17:08 PATCH - ESI Juli driver Demian Martin
2008-03-21 16:02 ` Pavel Hofman
2008-03-25 6:30 Demian Martin
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=47DE328D.1080009@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=mail@lightshed.de \
--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