26 May, 2008

1 commit


20 May, 2008

1 commit

  • Change HRTIMER_CB_IRQSAFE to HRTIMER_CB_SOFTIRQ,
    as suggested by Thomas Gleixner.
    That solves the lock dependancy reported in
    Bug #10701.
    That also allows to call hrtimer_start()
    directly, tasklet "stupid hack" removed.

    Signed-off-by: Stas Sergeev
    Acked-by: Thomas Gleixner
    Signed-off-by: Takashi Iwai

    Stas Sergeev
     

19 May, 2008

4 commits


07 May, 2008

1 commit

  • fix pcspkr dependancies: make the pcspkr platform
    drivers to depend on a platform device, and
    not the other way around.

    Signed-off-by: Stas Sergeev
    Acked-by: Thomas Gleixner
    Acked-by: Dmitry Torokhov
    CC: Vojtech Pavlik
    CC: Michael Opdenacker
    [fixed for 2.6.26-rc1 by tiwai]
    Signed-off-by: Takashi Iwai

    Stas Sergeev
     

05 May, 2008

1 commit


30 Apr, 2008

2 commits


24 Apr, 2008

15 commits


23 Feb, 2008

1 commit


01 Feb, 2008

12 commits

  • Fix section mismatches in mts64 by making a static variable __devinitdata.
    WARNING: vmlinux.o(.data+0x2e33f0): Section mismatch: reference to .init.data:mts64_ctl_smpte_switch (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')
    WARNING: vmlinux.o(.data+0x2e33f8): Section mismatch: reference to .init.data:mts64_ctl_smpte_time_hours (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')
    WARNING: vmlinux.o(.data+0x2e3400): Section mismatch: reference to .init.data:mts64_ctl_smpte_time_minutes (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')
    WARNING: vmlinux.o(.data+0x2e3408): Section mismatch: reference to .init.data:mts64_ctl_smpte_time_seconds (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')
    WARNING: vmlinux.o(.data+0x2e3410): Section mismatch: reference to .init.data:mts64_ctl_smpte_time_frames (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')
    WARNING: vmlinux.o(.data+0x2e3418): Section mismatch: reference to .init.data:mts64_ctl_smpte_fps (between 'control.19929' and 'snd_mts64_rawmidi_output_ops')

    Signed-off-by: Randy Dunlap
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Randy Dunlap
     
  • This header file exists only for some hacks to adapt alsa-driver
    tree. It's useless for building in the kernel. Let's move a few
    lines in it to sound/core.h and remove it.
    With this patch, sound/driver.h isn't removed but has just a single
    compile warning to include it. This should be really killed in
    future.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • The functions time_before, time_before_eq, time_after, and time_after_eq
    are more robust for comparing jiffies against other values.
    A simplified version of the semantic patch making this change is as follows:
    (http://www.emn.fr/x-info/coccinelle/)
    //
    @ change_compare_np @
    expression E;
    @@
    (
    - jiffies = E
    + time_after_eq(jiffies,E)
    |
    - jiffies < E
    + time_before(jiffies,E)
    |
    - jiffies > E
    + time_after(jiffies,E)
    )
    @ include depends on change_compare_np @
    @@
    #include
    @ no_include depends on !include && change_compare_np @
    @@
    #include
    + #include
    //

    Signed-off-by: Julia Lawall
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Julia Lawall
     
  • Signed-off-by: Joe Perches
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Joe Perches
     
  • Added the missing call of snd_card_set_dev() in drivers/*

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • Check the value ranges in ctl put callbacks properly (in the rest drivers).

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • Check the value ranges in ctl put callbacks in vxpocket driver.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • We have to do fairly accurate counting of the minimal periods, instead
    of being lazy and just setting the number to zero as soon as one period
    elapses.

    Signed-off-by: Joachim Foerster
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Joachim Foerster
     
  • Add ALSA support for the opb_ac97_controller_ref_v1_00_a ip core found
    in Xilinx' ML403 reference design.
    Known issue: Currently this driver hits a WARN_ON_ONCE(1) statement in
    kernel/irq/resend.c (line 70). According to Linus
    (http://lkml.org/lkml/2007/8/5/5) this may be ignored, right? I haven't
    had a look into this 'problem' yet.

    Signed-off-by: Joachim Foerster
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Joachim Foerster
     
  • I applied a wrong patch for 'opl3 - simplify exclusive access lock'.
    Fixed now.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • Use the exclusive access lock in hwdep instead of the own one.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     
  • Use the hwdep device for loading OPL2/3 patch data instead of the
    messy sequencer instrument layer.
    Due to this change, the sbiload program should be updated, too.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     

21 Nov, 2007

1 commit

  • Reported by Ingo Molnar,
    when booting an allyesconfig bzImage kernel the bootup hangs in the
    portman2x4 driver (on a box that does not have this hardware), at:
    Pid: 1, comm: swapper
    EIP: 0060:[] CPU: 0
    EIP is at parport_pc_read_status+0x4/0x8
    EFLAGS: 00000202 Not tainted (2.6.23-rc9 #904)
    EAX: f7e57a7f EBX: 00000010 ECX: c2b808c0 EDX: 00000379
    ESI: f7cb8230 EDI: 00000010 EBP: f7cb8230 DS: 007b ES: 007b FS: 0000
    CR0: 8005003b CR2: fff9c000 CR3: 007ec000 CR4: 00000690
    DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
    DR6: ffff0ff0 DR7: 00000400
    [] portman_flush_input+0xde/0x12c
    [] snd_portman_probe+0x368/0x484
    [] __device_attach+0x0/0x8
    [] platform_drv_probe+0xc/0x10
    [] driver_probe_device+0x74/0x194
    [] klist_next+0x38/0x70
    [] __device_attach+0x0/0x8
    [] bus_for_each_drv+0x35/0x68
    [] device_attach+0x72/0x78
    the reason is due to an inconsistent error return code of 1 or 2, while
    snd_portman_probe only realizes negative error codes.

    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Takashi Iwai
     

20 Nov, 2007

1 commit