Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Faber <faber@faberman.de>
To: alsa-devel@alsa-project.org
Subject: [PATCH 2/2] hdspm: modified include file
Date: Tue, 14 Apr 2009 17:48:53 +0200	[thread overview]
Message-ID: <1239724133.18545.8.camel@x200.watzmann.local> (raw)

Ckeaned up meter structure and modified the PEAK_RMS ioctl to reflect
the modifications.

diff a/sound/include/sound/hdspm.h b/sound/include/sound/hdspm.h

28,36d27
< /* peam rms level structure like we get from hardware 
<   
<    maybe in future we can memory map it so I just copy it
<    to user on ioctl call now an dont change anything
<    rms are made out of low and high values
<    where (long) ????_rms = (????_rms_l >> 8) + ((????_rms_h &
0xFFFFFF00)<<24)
<    (i asume so from the code)
< */
< 
37a29,35
>         uint32_t input_peaks[64];
>         uint32_t playback_peaks[64];
>         uint32_t output_peaks[64];
>   
>         uint64_t input_rms[64];
>         uint64_t playback_rms[64];
>         uint64_t output_rms[64];
39,56c37,38
< 	unsigned int level_offset[1024];
< 
< 	unsigned int input_peak[64];
< 	unsigned int playback_peak[64];
< 	unsigned int output_peak[64];
< 	unsigned int xxx_peak[64];	/* not used */
< 
< 	unsigned int reserved[256];	/* not used */
< 
< 	unsigned int input_rms_l[64];
< 	unsigned int playback_rms_l[64];
< 	unsigned int output_rms_l[64];
< 	unsigned int xxx_rms_l[64];	/* not used */
< 
< 	unsigned int input_rms_h[64];
< 	unsigned int playback_rms_h[64];
< 	unsigned int output_rms_h[64];
< 	unsigned int xxx_rms_h[64];	/* not used */
---
>         enum {ss, ds, qs} speed;
>         int status2;
59,61d40
< struct hdspm_peak_rms_ioctl {
< 	struct hdspm_peak_rms *peak;
< };
63d41
< /* use indirect access due to the limit of ioctl bit size */
65c43
< 	_IOR('H', 0x40, struct hdspm_peak_rms_ioctl)
---
> 	_IOR('H', 0x40, struct hdspm_peak_rms)

Flo
-- 
Machines can do the work, so people have time to think.
public key 6C002249          x-hkp://wwwkeys.eu.pgp.net

                 reply	other threads:[~2009-04-14 15:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1239724133.18545.8.camel@x200.watzmann.local \
    --to=faber@faberman.de \
    --cc=alsa-devel@alsa-project.org \
    /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