08 Mar, 2011

2 commits

  • container_of() should refer to the struct created in the example.

    Signed-off-by: Javi Merino
    Cc: Randy Dunlap
    Signed-off-by: Greg Kroah-Hartman

    Javi Merino
     
  • This patch implements PRUSS (Programmable Real-time Unit Sub System)
    UIO driver which exports SOC resources associated with PRUSS like
    I/O, memories and IRQs to user space. PRUSS is dual 32-bit RISC
    processors which is efficient in performing embedded tasks that
    require manipulation of packed memory mapped data structures and
    handling system events that have tight real time constraints. This
    driver is currently supported on Texas Instruments DA850, AM18xx and
    OMAP-L138 devices.
    For example, PRUSS runs firmware for real-time critical industrial
    communication data link layer and communicates with application stack
    running in user space via shared memory and IRQs.

    Signed-off-by: Pratheesh Gangadhar
    Reviewed-by: Thomas Gleixner
    Reviewed-by: Arnd Bergmann
    Signed-off-by: Hans J. Koch
    Signed-off-by: Greg Kroah-Hartman

    Pratheesh Gangadhar
     

01 Mar, 2011

1 commit


26 Feb, 2011

6 commits

  • DMI entries are arranged in memory back to back with no alignment
    guarantees. This means that the struct dmi_header passed to callbacks
    from dmi_walk() itself isn't byte aligned. This causes problems on
    architectures that expect aligned data, such as IA64.

    The dmi-sysfs patchset introduced structure member accesses through this
    passed in dmi_header. Fix this by memcpy()ing the structures to
    temporary locations on stack when inspecting/copying them.

    Signed-off-by: Mike Waychison
    Tested-by: Tony Luck
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     
  • Document the new ABI added by the dmi-sysfs module.

    Signed-off-by: Mike Waychison
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     
  • The System Event Log described by DMI entry type 15 may be backed by
    either memory or may be indirectly accessed via an IO index/data
    register pair.

    In order to get read access to this log, expose it in the
    "system_event_log" sub-directory of type 15 DMI entries, ie:
    /sys/firmware/dmi/entries/15-0/system_event_log/raw_event_log.

    This commit handles both IO accessed and memory access system event
    logs. OEM specific access and GPNV support is explicitly not handled
    and we error out in the logs when we do not recognize the access method.

    Signed-off-by: Mike Waychison
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     
  • The optional type 15 entry of the DMI table describes a non-volatile
    storage-backed system event log.

    In preparation for the next commit which exposes the raw bits of the
    event log to userland, create a new sub-directory within the dmi entry
    called "system_event_log" and expose attribute files that describe the
    event log itself.

    Currently, only a single child object is permitted within a
    dmi_sysfs_entry. We simply point at this child from the dmi_sysfs_entry
    if it exists.

    Signed-off-by: Mike Waychison
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     
  • Introduce a new module "dmi-sysfs" that exports the broken out entries
    of the DMI table through sysfs.

    Entries are enumerated via dmi_walk() on module load, and are populated
    as kobjects rooted at /sys/firmware/dmi/entries.

    Entries are named "-", where:
    : is the type of the entry, and
    : is the ordinal count within the DMI table of that
    entry type. This instance is used in lieu the DMI
    entry's handle as no assurances are made by the kernel
    that handles are unique.

    All entries export the following attributes:
    length : The length of the formatted portion of the entry
    handle : The handle given to this entry by the firmware
    raw : The raw bytes of the entire entry, including the
    formatted portion, the unformatted (strings) portion,
    and the two terminating nul characters.
    type : The DMI entry type
    instance : The ordinal instance of this entry given its type.
    position : The position ordinal of the entry within the table in
    its entirety.

    Entries in dmi-sysfs are kobject backed members called "struct
    dmi_sysfs_entry" and belong to dmi_kset. They are threaded through
    entry_list (protected by entry_list_lock) so that we can find them at
    cleanup time.

    Signed-off-by: Mike Waychison
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     
  • In preparation for the upcoming commits, introduce the DMI entry types to
    the headers. These type names are based on those specified in the DMTF
    SMBIOS specification version 2.7.1.

    Signed-off-by: Mike Waychison
    Signed-off-by: Greg Kroah-Hartman

    Mike Waychison
     

19 Feb, 2011

5 commits


05 Feb, 2011

8 commits

  • TI shared transport driver previously intended to expose rfkill
    entries for each of the protocol gpio that the chip would have.
    However now in case such gpios exist, which requires to be enabled
    for a specific protocol, the responsibility lay on protocol driver.
    This patch removes the request/free of multiple gpios, rfkill struct
    references and also removes the chip_toggle function.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • Where file-transfer stops/pauses in between, is
    result of a HCI-LL anamoly in ST LL driver.
    ST LL did not copy the contents of WaitQ into the TxQ, when a WAKEUP_IND
    collision happened.
    Make also sure, that the copying mechanism is safe, by wrapping it around
    spin locks inside st_int_recv().
    This was easily reproduced when the sleep timeout was reduced to 100ms
    for HCI-LL.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • To fasten the process of firmware download, the chip allows
    disabling of the command complete event generation from host.
    In these cases, only few very essential commands would have
    the command complete events and hence the wait associated with
    them.

    So now the driver would wait for a command complete event, only
    when it comes across a wait event during firmware parsing.
    This would also mean we need to skip not just the change baud
    rate command but also the wait for it.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • pr_debug-ing few pr_infos from the data paths such as tty receive and
    write so as to reduce debugs when we have higher logging levels enabled
    undef VERBOSE in receive to avoid huge logs when log level 8 is set.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • set-right the error codes that the shared transport driver
    returns.
    Instead of magic numbers like -1, return relevant codes such as
    ETIMEDOUT or EIO, EAGAIN when wait times out or uart write bytes don't
    match expected value or when registration fails and needs to be
    attempted again.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • The communication between ST KIM and UIM was interfaced
    over the /dev/rfkill device node.
    Move the interface to a simpler less abusive sysfs entry
    mechanism and document it in Documentation/ABI/testing/
    under sysfs-platform-kim.

    Shared transport driver would now read the UART details
    originally received by bootloader or firmware as platform
    data.
    The data read will be shared over sysfs entries for the user-space
    UIM or other n/w manager/plugins to be read, and assist the driver
    by opening up the UART, setting the baud-rate and installing the
    line discipline.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • The architecture of shared transport had begun with individual
    protocols like bluetooth, fm and gps telling the shared transport
    what sort of protocol they are and then expecting the ST driver
    to parse the incoming data from chip and forward data only
    relevant to the protocol drivers.

    This change would mean each protocol drivers would also send
    information to ST driver as to how to intrepret their protocol
    data coming out of the chip.

    Signed-off-by: Pavan Savoy
    Signed-off-by: Greg Kroah-Hartman

    Pavan Savoy
     
  • When i see the file linux-2.6.37/Documentation/zh_CN/SubmittingPatches ,
    i find a mistake Chinese character in it. So i give a patch for
    correcting this error.

    Signed-off-by: Harry Wei
    Signed-off-by: Greg Kroah-Hartman

    Harry Wei
     

04 Feb, 2011

18 commits

  • Signed-off-by: Ferenc Wagner
    Signed-off-by: Greg Kroah-Hartman

    Ferenc Wagner
     
  • The original macro worked only when applied to variables named 'dev'.
    While this could have been fixed by simply renaming the macro argument,
    a more type-safe replacement by an inline function is preferred.

    Signed-off-by: Ferenc Wagner
    Signed-off-by: Greg Kroah-Hartman

    Ferenc Wagner
     
  • As a follow-on to the recent patches I submitted that allowed for a sysfs
    memory block to span multiple memory sections, we should also update the
    probe routine to online all of the memory sections in a memory block. Without
    this patch the current code will only add a single memory section. I think
    the probe routine should add all of the memory sections in the specified memory
    block so that its behavior is in line with memory hotplug actions through
    the sysfs interfaces.

    This patch applies on top of the previous sysfs memory updates to allow
    a sysfs directory o span multiple memory sections.

    https://lkml.org/lkml/2011/1/20/245

    Signed-off-by: Nathan Fontenot
    Signed-off-by: Greg Kroah-Hartman

    Nathan Fontenot
     
  • Define a version of memory_block_size_bytes for x86_64 when CONFIG_X86_UV is
    set.

    Signed-off-by: Robin Holt
    Signed-off-by: Jack Steiner
    Signed-off-by: Nathan Fontenot
    Signed-off-by: Greg Kroah-Hartman

    Nathan Fontenot
     
  • Define a version of memory_block_size_bytes() for powerpc/pseries such that
    a memory block spans an entire lmb.

    Signed-off-by: Nathan Fontenot
    Reviewed-by: Robin Holt
    Signed-off-by: Greg Kroah-Hartman

    Nathan Fontenot
     
  • Update the 'phys_index' property of a the memory_block struct to be
    called start_section_nr, and add a end_section_nr property. The
    data tracked here is the same but the updated naming is more in line
    with what is stored here, namely the first and last section number
    that the memory block spans.

    The names presented to userspace remain the same, phys_index for
    start_section_nr and end_phys_index for end_section_nr, to avoid breaking
    anything in userspace.

    This also updates the node sysfs code to be aware of the new capability for
    a memory block to contain multiple memory sections and be aware of the memory
    block structure name changes (start_section_nr). This requires an additional
    parameter to unregister_mem_sect_under_nodes so that we know which memory
    section of the memory block to unregister.

    Signed-off-by: Nathan Fontenot
    Reviewed-by: Robin Holt
    Reviewed-by: KAMEZAWA Hiroyuki
    Signed-off-by: Greg Kroah-Hartman

    Nathan Fontenot
     
  • Update the memory sysfs code such that each sysfs memory directory is now
    considered a memory block that can span multiple memory sections per
    memory block. The default size of each memory block is SECTION_SIZE_BITS
    to maintain the current behavior of having a single memory section per
    memory block (i.e. one sysfs directory per memory section).

    For architectures that want to have memory blocks span multiple
    memory sections they need only define their own memory_block_size_bytes()
    routine.

    Update the memory hotplug documentation to reflect the new behaviors of
    memory blocks reflected in sysfs.

    Signed-off-by: Nathan Fontenot
    Reviewed-by: Robin Holt
    Reviewed-by: KAMEZAWA Hiroyuki
    Signed-off-by: Greg Kroah-Hartman

    Nathan Fontenot
     
  • This fixes a build breakage caused by
    8ba6ebf583f12da32036fc0f003ab4043e54692e "Dynamic debug: Add more flags"

    Cc: Bart Van Assche
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     
  • Add ML7213 device information.
    ML7213 is companion chip of Intel Atom E6xx series for IVI(In-Vehicle Infotainment).
    ML7213 is completely compatible for Intel EG20T PCH.

    Signed-off-by: Tomoya MORINAGA
    Signed-off-by: Greg Kroah-Hartman

    Tomoya MORINAGA
     
  • Signed-off-by: Harry Wei
    Signed-off-by: Greg Kroah-Hartman

    Harry Wei
     
  • When encountering an error while executing the driver's ->add method, we
    should cancel registration and unwind what we've regged so far. The low
    level ->add methods do return proper error codes but those aren't looked
    at in sysdev_driver_register(). Fix that by sharing the unregistering
    code.

    Signed-off-by: Borislav Petkov
    Signed-off-by: Greg Kroah-Hartman

    Borislav Petkov
     
  • debugfs can't be a module, so module_exit() is meaningless for it.

    Signed-off-by: WANG Cong
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Amerigo Wang
     
  • Use gcc's __func__ instead of the function name.

    Signed-off-by: Borislav Petkov
    Signed-off-by: Greg Kroah-Hartman

    Borislav Petkov
     
  • Some place in firmware_class.c using "int uevent" define, but others use "bool
    uevent".
    This patch replace all int uevent define to bool.

    Signed-off-by: Bob Liu
    Acked-by: Dmitry Torokhov
    Signed-off-by: Greg Kroah-Hartman

    Bob Liu
     
  • Add flags that allow the user to specify via debugfs whether or not the
    module name, function name, line number and/or thread ID have to be
    included in the printed message.

    Signed-off-by: Bart Van Assche
    Cc: Greg Banks
    Cc: Konrad Rzeszutek Wilk
    Signed-off-by: Greg Kroah-Hartman

    Bart Van Assche
     
  • Several functions in accept printf-style arguments.
    Some of these functions have been annotated with a format attribute
    declaration while others have not been annotated. Add a format attribute
    specification where it is missing.

    Signed-off-by: Bart Van Assche
    Signed-off-by: Greg Kroah-Hartman

    Bart Van Assche
     
  • Since snprintf() may return a value that exceeds its second argument,
    show() methods should use scnprintf() instead of snprintf(). This patch
    updates the example in the sysfs documentation accordingly.

    Signed-off-by: Bart Van Assche
    Cc: Tejun Heo
    Cc: Dmitry Torokhov
    Signed-off-by: Greg Kroah-Hartman

    Bart Van Assche
     
  • Some time ago the way how sysfs stores a pointer to a kobject
    corresponding to a directory was modified. This patch brings the
    documentation again in sync with the implementation.

    Signed-off-by: Bart Van Assche
    Cc: Tejun Heo
    Cc: Dmitry Torokhov
    Signed-off-by: Greg Kroah-Hartman

    Bart Van Assche