From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755222AbcCXH2b (ORCPT ); Thu, 24 Mar 2016 03:28:31 -0400 Received: from regular1.263xmail.com ([211.150.99.131]:40683 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751454AbcCXH2V (ORCPT ); Thu, 24 Mar 2016 03:28:21 -0400 X-Greylist: delayed 157926 seconds by postgrey-1.27 at vger.kernel.org; Thu, 24 Mar 2016 03:28:20 EDT X-263anti-spam: KSV:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-ADDR-CHECKED: 0 X-MAE-MAIL_UID: 0056f3970b008e83@maes@3a3c7e927b5c437e X-MAE-ID: 223.6.254.61 X-RL-SENDER: andy.yan@rock-chips.com X-LOGIN-NAME: andy.yan@rock-chips.com X-SENDER-IP: 121.15.173.1 Subject: Re: [PATCH v6 1/4] dt-bindings: power: reset: add document for reboot-mode driver To: Krzysztof Kozlowski References: <1458646525-491-1-git-send-email-andy.yan@rock-chips.com> <1458646592-540-1-git-send-email-andy.yan@rock-chips.com> Cc: robh+dt@kernel.org, sre@kernel.org, heiko@sntech.de, john.stultz@linaro.org, arnd@arndb.de, galak@codeaurora.org, ijc+devicetree@hellion.org.uk, catalin.marinas@arm.com, olof@lixom.net, alexandre.belloni@free-electrons.com, dbaryshkov@gmail.com, jun.nie@linaro.org, pawel.moll@arm.com, will.deacon@arm.com, linux-rockchip@lists.infradead.org, matthias.bgg@gmail.com, devicetree@vger.kernel.org, linux-pm@vger.kernel.org, f.fainelli@gmail.com, linux@arm.linux.org.uk, mbrugger@suse.com, linux-arm-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com, moritz.fischer@ettus.com, linux-kernel@vger.kernel.org, wxt@rock-chips.com, dwmw2@infradead.org, mark.rutland@arm.com From: Andy Yan Message-ID: <56F396FB.8030402@rock-chips.com> Date: Thu, 24 Mar 2016 15:27:55 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Krzysztof: On 2016年03月24日 10:27, Krzysztof Kozlowski wrote: > Interesting idea. While looking at the code I stumped over few things below: > > On Tue, Mar 22, 2016 at 8:36 PM, Andy Yan wrote: >> add device tree bindings document for reboot-mode driver > s/add/Add/ > Plus a full-stop at the end of sentence. okay, I will do it in next version. >> Signed-off-by: Andy Yan >> Acked-by: Rob Herring >> >> binding > What is that? This will be removed > >> --- >> >> Changes in v6: >> - fix a typo with "property" >> - describe property "mask" more clear >> >> Changes in v5: >> - delete a unnecessary blank line in syscon-reboot-mode.txt >> - rename mode-fastoboot to mode-bootloader in syscon-reboot-mode.txt >> - rename macro BOOT_LOADER to BOOT_BL_DOWNLOAD, which gives a more clear mean >> >> Changes in v4: >> - remove mode-maskrom >> - rename mode-fastboot to mode-bootloader to keep compatible with the exiting Android device >> >> Changes in v3: >> - descirbe all reboot mode as properity instead of subnode >> >> Changes in v2: None >> Changes in v1: None >> >> .../bindings/power/reset/reboot-mode.txt | 24 +++++++++++++++ >> .../bindings/power/reset/syscon-reboot-mode.txt | 35 ++++++++++++++++++++++ >> 2 files changed, 59 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> create mode 100644 Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> >> diff --git a/Documentation/devicetree/bindings/power/reset/reboot-mode.txt b/Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> new file mode 100644 >> index 0000000..3457949 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> @@ -0,0 +1,24 @@ >> +Generic reboot mode core map driver >> + >> +This driver get reboot mode arguments and call the write >> +interface to stores the magic value in special register > s/stores/store/ >> +or ram . Then the bootloader can read it and take different > s/ram ./ram./ > >> +action according the argument stored. > according to > >> + >> +All mode properties are vendor specific, it is a indication to tell >> +the bootloder what to do when the system reboot, and should be named > s/bootloder/bootloader/ > s/reboot/reboots/ > >> +as mode-xxx = (xxx is mode name). >> + > These are examples? If yes then add a note, like: > > +For example modes common on Android platform: Thanks for your carefully review, all these will be fixed in next version. >> +- mode-normal: Normal reboot mode, system reboot with command "reboot". >> +- mode-recovery: Android Recovery mode, it is a mode to format the device or update a new image. >> +- mode-bootloader: Android fastboot mode, it's a mode to re-flash partitions on the Android based device. >> +- mode-loader: A bootloader mode, it's a mode used to download image on Rockchip platform, >> + usually used in development. > The "bootloader" and "loader" examples are very confusing. Maybe just > name the first one as "mode-fastboot" and second as > "rockchip-download"? The term "loader" does not look for me as > anything related to uploading/downloading new firmware. About these two modes, we have a long discussion with Rob and John [0] We keep them as what you see now to keep compatibility with exiting devices. [0] https://lkml.org/lkml/2016/2/2/128 > >> + >> +Example: >> + reboot-mode { >> + mode-normal = ; >> + mode-recovery = ; >> + mode-bootloader = ; >> + mode-loader = ; >> + } >> diff --git a/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> new file mode 100644 >> index 0000000..eb28469 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> @@ -0,0 +1,35 @@ >> +SYSCON reboot mode driver >> + >> +This driver get reboot mode magic value form reboot-mode driver > s/get/gets/ > >> +and stores it in a SYSCON mapped register. Then the bootloader >> +can read it and take different action according to the magic >> +value stored. >> + >> +This DT node should be represented as a sub-node of a "syscon", "simple-mfd" >> +node. >> + >> +Required properties: >> +- compatible: should be "syscon-reboot-mode" >> +- offset: offset in the register map for the storage register (in bytes) >> + >> +Optional property: >> +- mask: bits mask of the bits in the register to store the reboot mode magic value, >> + default set to 0xffffffff if missing. >> + >> +The rest of the properties should follow the generic reboot-mode discription > s/discription/description/ > > Please, run the spell check... > > Best regards, > Krzysztof > > > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: andy.yan@rock-chips.com (Andy Yan) Date: Thu, 24 Mar 2016 15:27:55 +0800 Subject: [PATCH v6 1/4] dt-bindings: power: reset: add document for reboot-mode driver In-Reply-To: References: <1458646525-491-1-git-send-email-andy.yan@rock-chips.com> <1458646592-540-1-git-send-email-andy.yan@rock-chips.com> Message-ID: <56F396FB.8030402@rock-chips.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Krzysztof: On 2016?03?24? 10:27, Krzysztof Kozlowski wrote: > Interesting idea. While looking at the code I stumped over few things below: > > On Tue, Mar 22, 2016 at 8:36 PM, Andy Yan wrote: >> add device tree bindings document for reboot-mode driver > s/add/Add/ > Plus a full-stop at the end of sentence. okay, I will do it in next version. >> Signed-off-by: Andy Yan >> Acked-by: Rob Herring >> >> binding > What is that? This will be removed > >> --- >> >> Changes in v6: >> - fix a typo with "property" >> - describe property "mask" more clear >> >> Changes in v5: >> - delete a unnecessary blank line in syscon-reboot-mode.txt >> - rename mode-fastoboot to mode-bootloader in syscon-reboot-mode.txt >> - rename macro BOOT_LOADER to BOOT_BL_DOWNLOAD, which gives a more clear mean >> >> Changes in v4: >> - remove mode-maskrom >> - rename mode-fastboot to mode-bootloader to keep compatible with the exiting Android device >> >> Changes in v3: >> - descirbe all reboot mode as properity instead of subnode >> >> Changes in v2: None >> Changes in v1: None >> >> .../bindings/power/reset/reboot-mode.txt | 24 +++++++++++++++ >> .../bindings/power/reset/syscon-reboot-mode.txt | 35 ++++++++++++++++++++++ >> 2 files changed, 59 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> create mode 100644 Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> >> diff --git a/Documentation/devicetree/bindings/power/reset/reboot-mode.txt b/Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> new file mode 100644 >> index 0000000..3457949 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/power/reset/reboot-mode.txt >> @@ -0,0 +1,24 @@ >> +Generic reboot mode core map driver >> + >> +This driver get reboot mode arguments and call the write >> +interface to stores the magic value in special register > s/stores/store/ >> +or ram . Then the bootloader can read it and take different > s/ram ./ram./ > >> +action according the argument stored. > according to > >> + >> +All mode properties are vendor specific, it is a indication to tell >> +the bootloder what to do when the system reboot, and should be named > s/bootloder/bootloader/ > s/reboot/reboots/ > >> +as mode-xxx = (xxx is mode name). >> + > These are examples? If yes then add a note, like: > > +For example modes common on Android platform: Thanks for your carefully review, all these will be fixed in next version. >> +- mode-normal: Normal reboot mode, system reboot with command "reboot". >> +- mode-recovery: Android Recovery mode, it is a mode to format the device or update a new image. >> +- mode-bootloader: Android fastboot mode, it's a mode to re-flash partitions on the Android based device. >> +- mode-loader: A bootloader mode, it's a mode used to download image on Rockchip platform, >> + usually used in development. > The "bootloader" and "loader" examples are very confusing. Maybe just > name the first one as "mode-fastboot" and second as > "rockchip-download"? The term "loader" does not look for me as > anything related to uploading/downloading new firmware. About these two modes, we have a long discussion with Rob and John [0] We keep them as what you see now to keep compatibility with exiting devices. [0] https://lkml.org/lkml/2016/2/2/128 > >> + >> +Example: >> + reboot-mode { >> + mode-normal = ; >> + mode-recovery = ; >> + mode-bootloader = ; >> + mode-loader = ; >> + } >> diff --git a/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> new file mode 100644 >> index 0000000..eb28469 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt >> @@ -0,0 +1,35 @@ >> +SYSCON reboot mode driver >> + >> +This driver get reboot mode magic value form reboot-mode driver > s/get/gets/ > >> +and stores it in a SYSCON mapped register. Then the bootloader >> +can read it and take different action according to the magic >> +value stored. >> + >> +This DT node should be represented as a sub-node of a "syscon", "simple-mfd" >> +node. >> + >> +Required properties: >> +- compatible: should be "syscon-reboot-mode" >> +- offset: offset in the register map for the storage register (in bytes) >> + >> +Optional property: >> +- mask: bits mask of the bits in the register to store the reboot mode magic value, >> + default set to 0xffffffff if missing. >> + >> +The rest of the properties should follow the generic reboot-mode discription > s/discription/description/ > > Please, run the spell check... > > Best regards, > Krzysztof > > > >