From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [RFC] Break up the patch_sigmatel.c
Date: Thu, 13 Aug 2009 10:34:37 +0300 [thread overview]
Message-ID: <1250148877.8641.19.camel@localhost.localdomain> (raw)
In-Reply-To: <s5hd47046zr.wl%tiwai@suse.de>
On Thu, 2009-08-13 at 07:28 +0200, Takashi Iwai wrote:
> At Wed, 12 Aug 2009 23:35:45 +0300,
> Maxim Levitsky wrote:
> >
> > Hi folks,
> >
> > I own an stac9227 and with latest kernel, it doesn't output any sound
> > via front headphones. (this a is desktop)
>
> OK, that could be my recent changes.
> Could you give alsa-info.sh output, at best, on the working and
> non-working states?
Oh, its was my mistake.
in short I thought that I installed the alsa git tree, but it turns out
that I was using the kernel drivers. alsa git drivers doesn't have this
bug anymore.
The long explanation of this my mistake was that I first installed alsa
drivers, but forgot, and installed kernel, which overwrite them.
>
> > I don't want to bother you with details, etc, I will fix that myself. I
> > have good knowledge of the device.
> >
> > However, the mess that is patch_sigmatel.c seems to be doubled.
> > its huge file, and there are loads on new codecs added.
> >
> > I have a suggestion, to break it up into smaller files.
> > I especially want to move all 'data' from it to header file, and sort it
> > by model.
>
> The "data" shouldn't be in header files in general...
>
> > Maybe move pin configs to separate file.
>
> This could be good.
>
> > Also I know that stac9200 is quite old, and uses many different support
> > functions. I could move these in another file as well.
> >
> > In other words, I want to break it up into several (5 maybe) files,
> > while not touching the code itself (I so that later maybe)
> >
> > Since it is quite dirty and hard work, I want to ask if you agree.
>
> It's open source, feel free to do it.
nice, I actually asked about this just for one reason, back when I send
my patches to this driver, I think I tried to do something similar, but
it was rejected or so.
And another note.
Back in time, when I knew that driver well, back and front outputs were
handled by same DAC, and it happened to be DAC0. This DAC is connected
via analog loopback to ADC0.
Now front output is connected to another DAC, so loopback works only for
back output. However I can control the volume of front and back channels
separately, and don't know which feature I need more now (I don't use my
tv card often any more nowadays)
Maybe add a codec hint for that?
>
> > Btw, half of static data can be retrieved from codec by querying it
> > (like dac,adc,pin node ids)
>
> Yes.
>
Indeed.
I think that the best solution to all hda problems, it once and for all
write a generic driver for all codecs, and put pin configs in, a
'firmware' file (this is already done?)
Most of things can be retrieved from verb responses + pin configs
Why not?
Thanks,
Best regards,
Maxim Levitsky
>
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2009-08-13 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:35 [RFC] Break up the patch_sigmatel.c Maxim Levitsky
2009-08-12 20:45 ` Daniel Chen
2009-08-12 20:50 ` Maxim Levitsky
2009-08-13 5:28 ` Takashi Iwai
2009-08-13 7:34 ` Maxim Levitsky [this message]
2009-08-13 7:55 ` Takashi Iwai
2009-08-13 15:05 ` Maxim Levitsky
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=1250148877.8641.19.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=alsa-devel@alsa-project.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.