Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4192371ybl; Mon, 9 Dec 2019 06:57:35 -0800 (PST) X-Google-Smtp-Source: APXvYqyaB8umdn3H1iKlewEAReDgeQk55UrZN4WxBcrwzUDm8EJEw0LaGVPEzjsLa213xTcOgyAn X-Received: by 2002:a9d:7ac9:: with SMTP id m9mr20972156otn.80.1575903455908; Mon, 09 Dec 2019 06:57:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575903455; cv=none; d=google.com; s=arc-20160816; b=GILVBDO6W3oLc7WuTMVaEo5EUH9G9ipR45AbaEA2w4pAQqnQmfEq+lnT1yJa49VrVf u9RTSQaRdV0yaZ5u/ypL+qO11lIBVAmP9moicK5kvrJe6WuyKmz2rpodZzJCnZnccDvH vSrC+lRjgDBX1cU2DqUkDkIGwaz9tmacYzn6uppxf9hi6a30l+aFx1XC3yp192nYHt7S elB23KVmz2WER2q3ljz5ni6DZmCnDs8CtraPVSlyo3xD748x+fqU7dZFVzjrwd7Fzfku zsPF+NQV3yb/jfCjCV3HMuKIrIQD7kva5lbFjK3Kl6fA8LDNQQBGP+FnhogGdxs5Eue1 Og2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=GZjkca3Zp9sYYYIS/QPCEF0H2DGmE3kQodC7U7RI6jg=; b=W0lDRdSgUFQHQkeYQkaOGj+vfGai49I8PdTbn00zEIXum48cdpu5cnLfruwWMoOXun Gwuyi9V/tiPlz4YRvPyHsEOu5h2J2T47NZJQL6ESAMzWDDjHEzntWgbfbSrbcvD7rUKs ggtuhOmPJ9bKjOd6q8jFtQJd7V+z1NoK7UGPE4Wwbd29B0BtGIfRejQsQ+iU4tgXxuBx CmmXXoONCM6XbeyVSxllW7rqYHMLU4m4CKcJWqw1lOVwleSQOMgvhAxd2LCK/tGB2thZ XuShFTEjiihzBgozZXfA9EG/Tgq0lEyrc14B6QSKZzajdfz0mcEE9ez0oPWiZDSUrG/m 89AQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Jo1DFtbf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q26si11888779oij.38.2019.12.09.06.57.24; Mon, 09 Dec 2019 06:57:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Jo1DFtbf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726642AbfLIO4z (ORCPT + 99 others); Mon, 9 Dec 2019 09:56:55 -0500 Received: from mail-il1-f193.google.com ([209.85.166.193]:37693 "EHLO mail-il1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726310AbfLIO4z (ORCPT ); Mon, 9 Dec 2019 09:56:55 -0500 Received: by mail-il1-f193.google.com with SMTP id t9so12975433iln.4; Mon, 09 Dec 2019 06:56:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GZjkca3Zp9sYYYIS/QPCEF0H2DGmE3kQodC7U7RI6jg=; b=Jo1DFtbfEqbVJQq5XZ5LYzCv5LfIMXre5rs2IBqXAEswSM4ZyGHTOACUpAWl/JxobF HLX/pPfXm0RL9M3l645yavzaROmAbjPrumBgCxOs+qt0jECTLvAP2saRGhxDiE4oVabe x5ksCotFtF8bz+kAXYWj99jBeJUme6AdylQlFhZHK5Pd5Gk1t3eZiddRZuYK0LK40RxD YSVYDjyxUtLqzzIQK4xOZoi+glaFkyr5SiLcxWGHnk44UhVVdqwlxJe//NV2RaRGPTNP gl8tmVv118OmwBXVwaHHpaVbbEq1vi6cVvltYUcazpnix7+plbZ6LF5IODbwmjQ4/C3R 9miQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GZjkca3Zp9sYYYIS/QPCEF0H2DGmE3kQodC7U7RI6jg=; b=HGkTwBtNpfa0PsAvonHxJuAzOIxbuXF03Cfft+CY/0La5g/uYt4+7CnOehphaIlYAf oeVVf4hvIWtiwAV8s5Z29TaVHg0+9ptlOm1akBduHliIGI0nOWkFyawwi23sQAhGcrp5 M784IiwdijVdyyiJP05KvYzUrW5cB6ayAHEmvRFzhV+JcQ+8c4g3uuC+H2kJBACGGorh k6gAXLtw4YyHf2rxQnJg0tEkgbyF9itKdCruZWlqLsvb+Xzf98EsM+JYWl9TZEEdfyJA R9t1oB/NrFSVKWP/AE2RfY0ssvSrHX5YY9j/WFuGC+Bs3ef2OP5gex6vM3907pQ6ROM7 Al/A== X-Gm-Message-State: APjAAAXsKve5UM7kJ0xhJpWIDjOoQcCXi2/iZJ48/TC16wV2jlNNzNnh 6UrflmFgg8uYpJi46BVnYk0yzGhLQYid/1iMFwcOUGi6 X-Received: by 2002:a92:3919:: with SMTP id g25mr10786954ila.221.1575903414183; Mon, 09 Dec 2019 06:56:54 -0800 (PST) MIME-Version: 1.0 References: <20191206184536.2507-1-linux.amoon@gmail.com> <724aa7db-3838-16f9-d344-1789ae2a5746@arm.com> In-Reply-To: <724aa7db-3838-16f9-d344-1789ae2a5746@arm.com> From: Anand Moon Date: Mon, 9 Dec 2019 20:26:42 +0530 Message-ID: Subject: Re: [RFCv1 0/8] RK3399 clean shutdown issue To: Robin Murphy Cc: Rob Herring , Mark Rutland , Heiko Stuebner , Jagan Teki , Manivannan Sadhasivam , Daniel Schultz , devicetree , linux-arm-kernel , linux-rockchip@lists.infradead.org, Linux Kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Robin, On Mon, 9 Dec 2019 at 18:59, Robin Murphy wrote: > > On 06/12/2019 6:45 pm, Anand Moon wrote: > > Most of the RK3399 SBC boards do not perform clean > > shutdown and clean reboot. > > FWIW reboot problems on RK3399 have been tracked down to issues in > upstream ATF, and are unrelated to the PMIC. Yes I am aware of this changes. But, I have tired to study *RK808 datasheet V1.4* [0] below section *5.2.3 Power Channel Control/Monitor Registers* for clean reboot I was going to try disable some bit in below into reboot handle in the future patch. DCDC_EN_REG SLEEP_SET_OFF_REG1 SLEEP_SET_OFF_REG2 DCDC_UV_STS_REG I was going see if this helps to do clean reboot. further more use this in suspend/resume operation. [0] http://rockchip.fr/RK808%20datasheet%20V1.4.pdf But I feed that their is some more issue with related to mmc or PCIe not able to cleanly release the resources while reboot which caused then to disable after reboot. > > > These patches try to help resolve the issue with proper > > shutdown by turning off the PMIC. > > As mentioned elsewhere[1], although this is what the BSP kernel seems to > do, and in practice it's unlikely to matter for the majority of devboard > users like you and me, I still feel a bit uncomfortable with this > solution for systems using ATF as in principle the secure world might > want to know about orderly shutdowns, and this effectively makes every > shutdown an unexpected power loss from secure software's point of view. > > Robin. > > [1] > http://lists.infradead.org/pipermail/linux-rockchip/2019-December/028183.html > Yes I have follow the mailing list and I read this thread. I am not aware of ATF complete architecture. -Anand