13 Sep, 2018

1 commit

• 0789724f8   firmware: meson_sm: Add serial number sysfs entry ... Browse Code »

  The Amlogic Meson SoC Secure Monitor implements a call to retrieve an unique
  SoC ID starting from the GX Family and all new families.

  The serial number is simply exposed as a sysfs entry under the firmware
  sysfs directory.

  Signed-off-by: Neil Armstrong
  Signed-off-by: Kevin Hilman

  Neil Armstrong

  2018-09-13 11:54:07 +0800  

08 Mar, 2018

1 commit

• e0270c808   firmware: meson-sm: rework meson_sm_init to use module_platform_driver_probe ... Browse Code »

  Commit 3aa0582fdb82 ("of: platform: populate /firmware/ node from
  of_platform_default_populate_init()") takes care of populating
  all the devices under the /firmware/ node in of_platform_default_populate_init()

  This patch reworks meson_sm_init to use module_platform_driver_probe as
  the platform device is populated.

  Cc: Carlo Caione
  Cc: Kevin Hilman
  Cc: linux-amlogic@lists.infradead.org
  Signed-off-by: Sudeep Holla
  Signed-off-by: Kevin Hilman

  Sudeep Holla

  2018-03-08 09:33:52 +0800  

24 Mar, 2017

2 commits

• 7a9bc330d   firmware: meson-sm: Allow 0 as valid return value ... Browse Code »

  Some special SMC calls (i.e. the function used to retrieve the serial
  number of the Amlogic SoCs) returns 0 in the register 0 also when the
  data was successfully read instead of using the register to hold the
  number of bytes returned in the bounce buffer as expected.

  With the current implementation of the driver this is seen as an error
  and meson_sm_call_read() returns an error even though the data was
  correctly read.

  To deal with this when we have no information about the amount of read
  data (that is 0 is returned by the SMC call) we return to the caller
  the requested amount of data and 0 as return value.

  Signed-off-by: Carlo Caione
  Acked-by: Mark Rutland
  Signed-off-by: Kevin Hilman

  Carlo Caione

  2017-03-24 03:22:40 +0800  
• 83e007a0c   firmware: meson-sm: Check for buffer output size ... Browse Code »

  After the data is read by the secure monitor driver it is being copied
  in the output buffer checking only the size of the bounce buffer but not
  the size of the output buffer.

  Fix this in the secure monitor driver slightly changing the API. Fix
  also the efuse driver that it is the only driver using this API to not
  break bisectability.

  Signed-off-by: Carlo Caione
  Acked-by: Srinivas Kandagatla # for nvmem
  Acked-by: Mark Rutland
  Signed-off-by: Kevin Hilman

  Carlo Caione

  2017-03-24 03:22:32 +0800  

02 Sep, 2016

1 commit

• 2c4ddb215   firmware: Amlogic: Add secure monitor driver ... Browse Code »

  Introduce a driver to provide calls into secure monitor mode.

  In the Amlogic SoCs these calls are used for multiple reasons: access to
  NVMEM, set USB boot, enable JTAG, etc...

  Acked-by: Mark Rutland
  Signed-off-by: Carlo Caione
  [khilman: add in SZ_4K cleanup]
  Signed-off-by: Kevin Hilman

  Carlo Caione

  2016-09-02 05:23:39 +0800