1. 31 Jan, 2018 1 commit
  2. 13 Dec, 2017 1 commit
  3. 12 Dec, 2017 1 commit
  4. 06 Dec, 2017 1 commit
  5. 05 Dec, 2017 1 commit
  6. 04 Dec, 2017 1 commit
    • Chris Metcalf's avatar
      arch/tile: mark as orphaned · 8ee5ad1d
      Chris Metcalf authored
      
      The chip family of TILEPro and TILE-Gx was developed by Tilera, which
      was eventually acquired by Mellanox.  The tile architecture was added to
      the kernel in 2010 and first appeared in 2.6.36.
      
      Now at Mellanox we are developing new chips based on the ARM64
      architecture; our last TILE-Gx chip (the Gx72) was released in 2013, and
      our customers using tile architecture products are not, as far as we
      know, looking to upgrade to newer kernel releases.  In the absence of
      someone in the community stepping up to take over maintainership, this
      commit marks the architecture as orphaned.
      
      Cc: Chris Metcalf <metcalf@alum.mit.edu>
      Signed-off-by: default avatarChris Metcalf <cmetcalf@mellanox.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      8ee5ad1d
  7. 03 Dec, 2017 1 commit
  8. 30 Nov, 2017 1 commit
  9. 29 Nov, 2017 2 commits
  10. 27 Nov, 2017 1 commit
  11. 20 Nov, 2017 1 commit
  12. 19 Nov, 2017 3 commits
  13. 16 Nov, 2017 2 commits
  14. 14 Nov, 2017 1 commit
  15. 10 Nov, 2017 2 commits
  16. 08 Nov, 2017 5 commits
  17. 06 Nov, 2017 4 commits
  18. 05 Nov, 2017 3 commits
  19. 04 Nov, 2017 1 commit
  20. 03 Nov, 2017 7 commits
    • Mario Limonciello's avatar
      tools/wmi: add a sample for dell smbios communication over WMI · 9d64fc08
      Mario Limonciello authored
      
      This application uses the character device /dev/wmi/dell-smbios
      to perform SMBIOS communications from userspace.
      
      It offers demonstrations of a few simple tasks:
       - Running a class/select command
       - Querying a token value
       - Activating a token
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      9d64fc08
    • Mario Limonciello's avatar
      platform/x86: wmi: create userspace interface for drivers · 44b6b766
      Mario Limonciello authored
      
      For WMI operations that are only Set or Query readable and writable sysfs
      attributes created by WMI vendor drivers or the bus driver makes sense.
      
      For other WMI operations that are run on Method, there needs to be a
      way to guarantee to userspace that the results from the method call
      belong to the data request to the method call.  Sysfs attributes don't
      work well in this scenario because two userspace processes may be
      competing at reading/writing an attribute and step on each other's
      data.
      
      When a WMI vendor driver declares a callback method in the wmi_driver
      the WMI bus driver will create a character device that maps to that
      function.  This callback method will be responsible for filtering
      invalid requests and performing the actual call.
      
      That character device will correspond to this path:
      /dev/wmi/$driver
      
      Performing read() on this character device will provide the size
      of the buffer that the character device needs to perform calls.
      This buffer size can be set by vendor drivers through a new symbol
      or when MOF parsing is available by the MOF.
      
      Performing ioctl() on this character device will be interpretd
      by the WMI bus driver. It will perform sanity tests for size of
      data, test them for a valid instance, copy the data from userspace
      and pass iton to the vendor driver to further process and run.
      
      This creates an implicit policy that each driver will only be allowed
      a single character device.  If a module matches multiple GUID's,
      the wmi_devices will need to be all handled by the same wmi_driver.
      
      The WMI vendor drivers will be responsible for managing inappropriate
      access to this character device and proper locking on data used by
      it.
      
      When a WMI vendor driver is unloaded the WMI bus driver will clean
      up the character device and any memory allocated for the call.
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      44b6b766
    • Mario Limonciello's avatar
      platform/x86: dell-smbios-wmi: Add new WMI dispatcher driver · 1a258e67
      Mario Limonciello authored
      
      The dell-smbios stack only currently uses an SMI interface which grants
      direct access to physical memory to the firmware SMM methods via a pointer.
      
      This dispatcher driver adds a WMI-ACPI interface that is detected by WMI
      probe and preferred over the SMI interface in dell-smbios.
      
      Changing this to operate over WMI-ACPI will use an ACPI OperationRegion
      for a buffer of data storage when SMM calls are performed.
      
      This is a safer approach to use in kernel drivers as the SMM will
      only have access to that OperationRegion.
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      1a258e67
    • Mario Limonciello's avatar
      platform/x86: dell-smbios: Introduce dispatcher for SMM calls · 549b4930
      Mario Limonciello authored
      
      This splits up the dell-smbios driver into two drivers:
      * dell-smbios
      * dell-smbios-smm
      
      dell-smbios can operate with multiple different dispatcher drivers to
      perform SMBIOS operations.
      
      Also modify the interface that dell-laptop and dell-wmi use align to this
      model more closely.  Rather than a single global buffer being allocated
      for all drivers, each driver will allocate and be responsible for it's own
      buffer. The pointer will be passed to the calling function and each
      dispatcher driver will then internally copy it to the proper location to
      perform it's call.
      
      Add defines for calls used by these methods in the dell-smbios.h header
      for tracking purposes.
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      549b4930
    • Mario Limonciello's avatar
      platform/x86: dell-smbios: Add a sysfs interface for SMBIOS tokens · 33b9ca1e
      Mario Limonciello authored
      
      Currently userspace tools can access system tokens via the dcdbas
      kernel module and a SMI call that will cause the platform to execute
      SMM code.
      
      With a goal in mind of deprecating the dcdbas kernel module a different
      method for accessing these tokens from userspace needs to be created.
      
      This is intentionally marked to only be readable as a process with
      CAP_SYS_ADMIN as it can contain sensitive information about the
      platform's configuration.
      
      While adding this interface I found that some tokens are duplicated.
      These need to be ignored from sysfs to avoid duplicate files.
      
      MAINTAINERS was missing for this driver.  Add myself and Pali to
      maintainers list for it.
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      33b9ca1e
    • Mario Limonciello's avatar
      platform/x86: dell-wmi-descriptor: split WMI descriptor into it's own driver · 92b8c540
      Mario Limonciello authored
      
      All communication on individual GUIDs should occur in separate drivers.
      Allowing a driver to communicate with the bus to another GUID is just
      a hack that discourages drivers to adopt the bus model.
      
      The information found from the WMI descriptor driver is now exported
      for use by other drivers.
      Signed-off-by: default avatarMario Limonciello <mario.limonciello@dell.com>
      Reviewed-by: default avatarEdward O'Callaghan <quasisec@google.com>
      Signed-off-by: default avatarDarren Hart (VMware) <dvhart@infradead.org>
      92b8c540
    • Paul Burton's avatar
      Update MIPS email addresses · fb615d61
      Paul Burton authored
      MIPS will soon not be a part of Imagination Technologies, and as such
      many @imgtec.com email addresses will no longer be valid. This patch
      updates the addresses for those who:
      
       - Have 10 or more patches in mainline authored using an @imgtec.com
         email address, or any patches dated within the past year.
      
       - Are still with Imagination but leaving as part of the MIPS business
         unit, as determined from an internal email address list.
      
       - Haven't already updated their email address (ie. JamesH) or expressed
         a desire to be excluded (ie. Maciej).
      
       - Acked v2 or earlier of this patch, which leaves Deng-Cheng, Matt &
         myself.
      
      New addresses are of the form firstname.lastname@mips.com, and all
      verified against an internal email address list.  An entry is added to
      .mailmap for each person such that get_maintainer.pl will report the new
      addresses rather than @imgtec.com addresses which will soon be dead.
      
      Instances of the affected addresses throughout the tree are then
      mechanica...
      fb615d61