Eric Lee / smarc-fsl-linux-kernel

27 Jan, 2009

1 commit

05 Jan, 2009

1 commit

18 Apr, 2008

2 commits

17 Oct, 2007

2 commits

10 Jul, 2007

1 commit

  • 53c96b417   ieee1394: remove old isochronous ABI ... Browse Code »

    Based on patch "the scheduled removal of RAW1394_REQ_ISO_{SEND,LISTEN}"
    from Adrian Bunk, November 20 2006.

    This patch also removes the underlying facilities in ohci1394 and
    disables them in pcilynx. That is, hpsb_host_driver.devctl() and
    hpsb_host_driver.transmit_packet() are no longer used for iso reception
    and transmission.

    Since video1394 and dv1394 only work with ohci1394 and raw1394's rawiso
    interface has never been implemented in pcilynx, pcilynx is now no
    longer useful for isochronous applications.

    raw1394 will still handle the request types but will complete the
    requests with errors that indicate API version conflicts.

    Signed-off-by: Stefan Richter

    Stefan Richter
     

14 Feb, 2007

1 commit

  • 12a917f69   i2c: Declare more i2c_adapter parent devices ... Browse Code »

    Declare the parent device of i2c_adapter devices each time we can
    easily do so. It makes the i2c_adapter appear at the right place in
    the device tree, rather than as a platform device.

    Signed-off-by: Jean Delvare
    Cc: David Brownell
    Cc: Len Brown
    Cc: Jordan Crouse
    Cc: Jody McIntyre
    Cc: Stefan Richter
    Cc: v4l-dvb-maintainer@linuxtv.org
    Cc: Petr Vandrovec

    Jean Delvare
     

11 Dec, 2006

1 commit

08 Dec, 2006

2 commits

05 Oct, 2006

1 commit

  • 7d12e780e   IRQ: Maintain regs pointer globally rather than passing to IRQ handlers ... Browse Code »

    Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

27 Sep, 2006

1 commit

  • a0d9c63d3   i2c-algo-bit: Discard the mdelay data struct member ... Browse Code »

    i2c-algo-bit: Discard the mdelay data struct member

    The i2c_algo_bit_data structure has an mdelay member, which is not
    used by the algorithm code (the code has always been ifdef'd out.)
    Let's discard it to save some code and memory.

    Signed-off-by: Jean Delvare
    Acked-by: Mauro Carvalho Chehab
    Cc: Adrian Bunk
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

03 Jul, 2006

1 commit

01 Jul, 2006

1 commit

20 Jun, 2006

1 commit

  • c6387a48c   [SPARC]: Kill __irq_itoa(). ... Browse Code »

    This ugly hack was long overdue to die.

    It was a way to print out Sparc interrupts in a more freindly format,
    since IRQ numbers were arbitrary opaque 32-bit integers which vectored
    into PIL levels. These 32-bit integers were not necessarily in the
    0-->NR_IRQS range, but the PILs they vectored to were.

    The idea now is that we will increase NR_IRQS a little bit and use a
    virtualreal IRQ number mapping scheme similar to PowerPC.

    That makes this IRQ printing hack irrelevant, and furthermore only a
    handful of drivers actually used __irq_itoa() making it even less
    useful.

    Signed-off-by: David S. Miller

    David S. Miller
     

07 Nov, 2005

1 commit

  • 8551158ab   kmalloc/kzalloc changes: ... Browse Code »

    dv1394, eth1394, ieee1394, ohci1394, pcilynx, raw1394, sbp2c, video1394:
    - use kzalloc
    - provide safer size arguments to kmalloc and kzalloc
    - omit some casts

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre

    Stefan Richter
     

06 Sep, 2005

1 commit

  • 386625f9f   [PATCH] I2C: Drop debug eeprom dump code in pcilynx ... Browse Code »
    86

    The pcilynx driver includes code to dump the contents of an i2c eeprom
    for debugging purposes. The same can be done from userspace using the
    i2cdump tool (part of the lm_sensors project) instead, in a more
    efficient and flexible way.

    Thus I would suggest that this functionality be simply dropped from the
    pcilynx driver.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

11 Jul, 2005

1 commit

  • 1934b8b65   [PATCH] Sync up ieee-1394 ... Browse Code »

    Lots of this patch is trivial code cleanups (static vars were being
    intialized to 0, etc).

    There's also some fixes for ISO transmits (max buffer handling).
    Aswell, we have a few fixes to disable IRM capabilites correctly. We've
    also disabled, by default some generally unused EXPORT symbols for the
    sake of cleanliness in the kernel. However, instead of removing them
    completely, we felt it necessary to have a config option that allowed
    them to be enabled for the many projects outside of the main kernel tree
    that use our API for driver development.

    The primary reason for this patch is to revert a MODE6->MODE10 RBC
    conversion patch from the SCSI maintainers. The new conversions handled
    directly in the scsi layer do not seem to work for SBP2. This patch
    reverts to our old working code so that users can enjoy using Firewire
    disks and dvd drives again.

    We are working with the SCSI maintainers to resolve this issue outside
    of the main kernel tree. We'll merge the patch once the SCSI layer's
    handling of the MODE10 conversion is working for us.

    Signed-off-by: Linus Torvalds

    Ben Collins
     

17 May, 2005

2 commits

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds