Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2288525pxb; Wed, 9 Feb 2022 15:15:15 -0800 (PST) X-Google-Smtp-Source: ABdhPJya2f8F5L+zZAfiPUSkLZvxGxA6IFGyZwoSLEYryOY4kwVd0ps7dXex+o+8kdx/uXBjYQBa X-Received: by 2002:a63:cd:: with SMTP id 196mr3781758pga.2.1644448515706; Wed, 09 Feb 2022 15:15:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644448515; cv=none; d=google.com; s=arc-20160816; b=LeG/o9fAybqAWslg07Q5OZtO7PZOUyUBzYZ2dwic5Jy6myEBfT40CxMgtK5BIrBzOQ a9Kb8wtgGYHT5ryWG5lnUWdsfkpwYvW8aTxWpVZCKAglSnWLhiWvk3jAoyt54zCm18Wk ejf96NndkD8h1T7kUHpAeFRFRToKxe0JnPV19SCkxmlaQ71SPpckekOn599oYDjzsqfL nnc4pBx74TOwXcwIpr7EGBy/au4nCmLymw4CDddNRzP7RZ1WZQMAqaBdiONehZi0Re9g OhOvh7u9f5CvUnDprkJsEx5tcS9eOdXBhcY8njCagZfYKJtnwqIHMu/YWDtwL/erC8VR SOTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=H8UvkuaPa9oG6MBcN88+EFcgU6RwUy+XLZ3L+fuvwWs=; b=ItcxACXadhKcHgdmqLI04gvXDFN3wtYR5nJw3swZc1GCRJfcpGgGU/7Ruq6XEZqgXn JNew0gfAm2HSXKHux7WfVUn26j9CPKLwkBwyZy6FAOOYL+OnAXWMF26GFY0TWxV6100j OEdbBYsiG266HfZyYKB30AFo0FqDzx2ENFL4zUaWRY7/GKk3+WsbOVpLANXrOUCw/luI isODfIjFcx9kDlmMglIHgltkkJiZ0aGjSfy7XtmwAwBrlfuCqfK8mv8Zz/GFeTwwLGk3 3hhzsquCQz7D7pj+SLYP8DVAeiYjKVQJTD7QX6H4GiNnnmaaYuV4pqTXRMu2xvMPOg2/ QnKw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=jLSqHONT; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id m14si355634plx.207.2022.02.09.15.15.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Feb 2022 15:15:15 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=jLSqHONT; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id AB173E051991; Wed, 9 Feb 2022 15:14:45 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231680AbiBIUa6 (ORCPT + 99 others); Wed, 9 Feb 2022 15:30:58 -0500 Received: from gmail-smtp-in.l.google.com ([23.128.96.19]:59944 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229946AbiBIUaz (ORCPT ); Wed, 9 Feb 2022 15:30:55 -0500 Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 14265C002B5D for ; Wed, 9 Feb 2022 12:30:57 -0800 (PST) Received: by mail-pf1-x42f.google.com with SMTP id r19so6370730pfh.6 for ; Wed, 09 Feb 2022 12:30:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=H8UvkuaPa9oG6MBcN88+EFcgU6RwUy+XLZ3L+fuvwWs=; b=jLSqHONTNlyEU0X36UjWm1OP1joipm2nCVWebcdjjAetYBRag2vvSJpPamuNKix4yP rwNNjw1RlAYXs2IL0B2gDrPemV4PSFexAl7LW4k/P83PpiO5dN+gxwb4Sgv+8t56Fa5i 8JaSKqWn+o/nkY2XIM+I2sBbvBFeL1MGcxdBNvYaOCU8YMQqtKpPPXc2VZmdawXxmy0S LJ2iCFCbGYdY+JVuIDZGIZ4SWKk7VLbnBFMyEooeL2WFWVKf30pucY+hBWoZcYcfTvor 296JPhFbIryEeulXN9SjrmIFNcQXBZf5goMqiW0G/5tE7Fu0gUSt4OOfY/492CjnIkzh IyQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=H8UvkuaPa9oG6MBcN88+EFcgU6RwUy+XLZ3L+fuvwWs=; b=yFGbVNJX492p5KuP/25CZJVfKX+mZZXXcH7W2ne5jx57SSLmF8F8UZIm5l2f9Aivvr 7Jxb/jWOCjhhu/79AM4/5vHcuPuA8FDxvbuglcJ8fcqGFCHHh43g9rtFIYiccHYwMs8n cHzEXDzgaI/FaFsQNAm1D7fHMY1A6TeeiM1z8oiEgiRLU5uyxaP4kQGwW/yYeqojaPM0 aNt30N3yXJL7C7bjDzZUOQLOVo4iCX6Go35HpE2kbD5/nqWHVhRk5i0F3FcF5D33e0io LatRDEY5PaVXDZJPf5bainAn7qGfgnO2uFRX2otPYruPjpl3YUoWiM8XDe4j9q/YL4Kj tOWg== X-Gm-Message-State: AOAM532A0tjcACgL8BHovDOkUb9Tebwo3DVranQPynqGiXnqqjicdFYr 3PNLdp6cye3ccOqINx2XA61ahlCFwVv4AQ== X-Received: by 2002:a63:844a:: with SMTP id k71mr3226964pgd.559.1644438656578; Wed, 09 Feb 2022 12:30:56 -0800 (PST) Received: from localhost (c-71-197-186-152.hsd1.wa.comcast.net. [71.197.186.152]) by smtp.gmail.com with ESMTPSA id d10sm20577340pfl.16.2022.02.09.12.30.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Feb 2022 12:30:55 -0800 (PST) From: Kevin Hilman To: "shunzhou.jiang@amlogic.com" , linux-arm-kernel , linux-amlogic , linux-kernel Cc: Neil Armstrong , jbrunet , Martin Blumenstingl , "jianxin.pan" Subject: Re: Re: [PATCH 2/2] soc: s4: Add support for power domains controller In-Reply-To: <202202091001287547451@amlogic.com> References: <20220126061018.705338-1-shunzhou.jiang@amlogic.com> <20220126061018.705338-3-shunzhou.jiang@amlogic.com> <7hzgnal5yu.fsf@baylibre.com> <202202091001287547451@amlogic.com> Date: Wed, 09 Feb 2022 12:30:55 -0800 Message-ID: <7hee4bok8w.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "shunzhou.jiang@amlogic.com" writes: > Hi Kevin: > Thanks your reply. > Please refer to below comment, >> S4_VPU_HDMI: for vpu domain, this domain provide power to many moudles(osd, vpp, hdr, dv, di), if close, will cause system crash >> S4_USB_COMB domain: for usb, if not always on, all usb status will clear to 0, that's not right status for usb Yes, I understand, this is teh same as for other SoCs (e.g. A1.) The solution is not to set the domain to always on. The solution is for the drivers for the devices in these domains use runtime PM so that when the drivers are active, the power domain does not get shut off. >> S4_ETH: for ethernet online wakeup, and if power down, status also not right OK, this one makes sense for "always on" since it used by firmware for wakeup. Kevin