https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y2018-09-13T03:54:07Zfirmware: meson_sm: Add serial number sysfs entry2018-09-13T03:54:07ZNeil Armstrongnarmstrong@baylibre.com2018-07-26T13:59:16Zurn:sha1:0789724f86a59fa7078d67dfeb1ee4a15ae3c693
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 <narmstrong@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
firmware: meson-sm: rework meson_sm_init to use module_platform_driver_probe2018-03-08T01:33:52ZSudeep Hollasudeep.holla@arm.com2018-03-06T11:47:49Zurn:sha1:e0270c8089ae65f7e5180b56a9fe1fdc7435a326
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 <carlo@caione.org>
Cc: Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
firmware: meson-sm: Allow 0 as valid return value2017-03-23T19:22:40ZCarlo Caionecarlo@endlessm.com2017-03-03T15:17:59Zurn:sha1:7a9bc330df9b8fb3245d50a198b5c6d4d634b06f
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 <carlo@endlessm.com>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
firmware: meson-sm: Check for buffer output size2017-03-23T19:22:32ZCarlo Caionecarlo@endlessm.com2017-03-03T15:17:58Zurn:sha1:83e007a0c6a3f4bfdf8f3f8d0fc266cda189b3d6
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 <carlo@endlessm.com>
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> # for nvmem
Acked-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
firmware: Amlogic: Add secure monitor driver2016-09-01T21:23:39ZCarlo Caionecarlo@endlessm.com2016-08-27T13:43:43Zurn:sha1:2c4ddb215521d5dfb30f72123ef966ac6bdd16d7
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 <mark.rutland@arm.com>
Signed-off-by: Carlo Caione <carlo@endlessm.com>
[khilman: add in SZ_4K cleanup]
Signed-off-by: Kevin Hilman <khilman@baylibre.com>