linux-kernel - Re: [PATCH v3 0/5] Add reboot notifier driver for rockchip platform

Open Source and information security mailing list archives

Date:	Mon, 14 Dec 2015 18:30:31 +0800
From:	Andy Yan <andy.yan@...k-chips.com>
To:	Heiko Stübner <heiko@...ech.de>,
	John Stultz <john.stultz@...aro.org>,
	Arnd Bergmann <arnd@...db.de>
Cc:	mark.rutland@....com, devicetree@...r.kernel.org,
	khilman@...aro.org, linux@....linux.org.uk, pawel.moll@....com,
	ijc+devicetree@...lion.org.uk, benchan@...gle.com,
	sjg@...omium.org, linux-kernel@...r.kernel.org,
	linux-rockchip@...ts.infradead.org, robh+dt@...nel.org,
	galak@...eaurora.org, treding@...dia.com,
	linux-arm-kernel@...ts.infradead.org, wxt@...k-chips.com
Subject: Re: [PATCH v3 0/5] Add reboot notifier driver for rockchip platform

Hi John:

On 2015年12月12日 05:29, Heiko Stübner wrote:
> Am Mittwoch, 18. November 2015, 17:47:24 schrieb Andy Yan:
>> rockchip platform have a protocol to pass the kernel reboot
>> mode to bootloader by some special registers when system reboot.
>> By this way the bootloader can take different action according
>> to the different kernel reboot mode, for example, command
>> "reboot loader" will reboot the board to rockusb mode, this is
>> a very convenient way to get the board enter download mode.
>> And Android system also use this protocol to pass "recovery"、
>> “fastboot” reboot mode to bootloader. In upstream land, We found
>> tegra platform also use this mechanism.
>>
>> Before this version, I have sent two Series, which can be found
>> at [0] [1]
>> [0] https://patchwork.kernel.org/patch/7140751/
>> [1] https://patchwork.kernel.org/patch/7153531/
> just so it doesn't get lost, this ties into a slightly more generic approach,
> John Stultz is doing for the android reboot reasons:
>
> http://thread.gmane.org/gmane.linux.kernel/2103447
>
> The only difference is that we'd need to use the pmu syscon for it.
>
>
     Very glad to see your work on this. And your work is more generic 
than my.
      So hope we can share the code. As you can see, the rockchip 
platform use
      a GRF or PMU register to store the reboot reason. So maybe we need 
a phandle
      in the DT node to describe it.
>> Changes in v3:
>>   - rename a pinctrl node in rk3288-veyron, the original name will be
>>     used in the incoming reboot notifier driver
>>   - add dt binding
>>   - move from mach-rockchip to drivers/soc/rockchip, as the tegra does
>>   - use dts pass the related register
>>   - add DT node
>>
>> Changes in v2:
>>    - check cpu dt node
>>    - remove a unnecessary of_put_node in function rockchip_get_pmu_regmap
>>    - fix a align issue
>>    - use reboot_notifier instead of restart_handler
>>
>> Andy Yan (5):
>>    ARM: dts: rockchip: rk3288-veyron: rename pinctrl node reboot to reset
>>    dt-bindings: soc: add document for rockchip reboot notifier driver
>>    soc: rockchip: add reboot notifier driver
>>    ARM: dts: rockchip: add reboot node
>>    ARM64: dts: rockchip: add reboot node
>>
>>   .../bindings/soc/rockchip/rockchip-reboot.txt      | 18 ++++
>>   arch/arm/boot/dts/rk3288-veyron.dtsi               |  2 +-
>>   arch/arm/boot/dts/rk3288.dtsi                      |  6 ++
>>   arch/arm/boot/dts/rk3xxx.dtsi                      |  6 ++
>>   arch/arm64/boot/dts/rockchip/rk3368.dtsi           |  6 ++
>>   drivers/soc/rockchip/Kconfig                       |  7 ++
>>   drivers/soc/rockchip/Makefile                      |  1 +
>>   drivers/soc/rockchip/loader.h                      | 22 +++++
>>   drivers/soc/rockchip/reboot.c                      | 98
>> ++++++++++++++++++++++ 9 files changed, 165 insertions(+), 1 deletion(-)
>>   create mode 100644
>> Documentation/devicetree/bindings/soc/rockchip/rockchip-reboot.txt create
>> mode 100644 drivers/soc/rockchip/loader.h
>>   create mode 100644 drivers/soc/rockchip/reboot.c
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives