Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1437834pxb; Thu, 28 Oct 2021 03:48:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzhHBvahrJRLKOJ8CfVEebHbrJ9I1+HwMok8DxsMLFE/qgoFyzSxU9lHUXERq6EmAbfkfrK X-Received: by 2002:a63:6ac2:: with SMTP id f185mr2640359pgc.326.1635418088126; Thu, 28 Oct 2021 03:48:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635418088; cv=none; d=google.com; s=arc-20160816; b=sCkeml5hhYLdnhoepSqx/g9jjyXhnGhsOJT+KyjmXQkxHUch9zeMqSjwIbSFE5uk4r xWkQ05Vm6VoPclIMD0xQJTi4tD9V7OXrAV2ILqRT/3Q9Qg73v8O10cH6SYB4+E6PL8Z9 l0jZMxxm4G4Bfr1mCRhXvFEG893npVJ23RGnkHJpGb090dfvkXu/V5NwOJPUg7BAl0NI lrsetWTTaAJZUqyFlAokKOIeG6LHqiiMvdZ8Kl4lesq2TCD8cDeMwplgXHi2FoNLAQix qSd/w+OLSnWmdiDUEyiqy+4rbUBAEQYFnaS8ZikW/1Rxvf7pdxKqUJQOmgs3iimM2XWf 8nkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dmarc-filter:sender:dkim-signature; bh=vaoUxaT5Jgj5fVGRcreSc6OdEp2mBWTsrQrE8jtHySY=; b=Gw++yggDtbYuta+bemHAC2QnD7wLufOzWb48Ct2eAsCYDXZz2IeKzetDibvpJVGplg FqB/L696UclPTbaoqNWYtmbMVFyySmHzgqI/X/07XzfOVWHKnhbNfwzh8lLQhLnXZS5g AQ3xTZAZclnDJusqdrDhWmXAqynRTm/FXutIjpZ8gXTavvXCM3RQbybw0LRKauwCnug6 91GieFpCXC78AHE7RwiC74rshbPnqW+/wPULr4gi2BsFwr/DU3afWAoaaDDqA7BliGio a9z3D+E2mZ4Y2k2TEky1uxfyt8weHWgS/VDvQdwZ7QAjr1aLd39CzahJE/s9R8AvyTMU cCpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=YRV6LS2u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n25si3658083pgm.224.2021.10.28.03.47.55; Thu, 28 Oct 2021 03:48:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=YRV6LS2u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230110AbhJ1KtZ (ORCPT + 99 others); Thu, 28 Oct 2021 06:49:25 -0400 Received: from m43-7.mailgun.net ([69.72.43.7]:60387 "EHLO m43-7.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230059AbhJ1KtY (ORCPT ); Thu, 28 Oct 2021 06:49:24 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1635418018; h=Content-Transfer-Encoding: Content-Type: In-Reply-To: MIME-Version: Date: Message-ID: From: References: Cc: To: Subject: Sender; bh=vaoUxaT5Jgj5fVGRcreSc6OdEp2mBWTsrQrE8jtHySY=; b=YRV6LS2ugEI7xhSvHEJnfOO4c+AMH8zDXFoI3MbtlUKq1+UpiGXCxP7/jlkxjNoySJxp74rM BeiuUImdLMyRvI5fQytlGy/y/xiYye6Oo5x/VHoCS0HfMHlXXXUWX+EM96MB4JzqEL5cMc5i 6ItkkuEcXsa/iCB8XT5bZSFMBY0= X-Mailgun-Sending-Ip: 69.72.43.7 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n01.prod.us-east-1.postgun.com with SMTP id 617a7f94545d7d365f16e5b0 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Thu, 28 Oct 2021 10:46:44 GMT Sender: rnayak=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 3BF4CC4360D; Thu, 28 Oct 2021 10:46:44 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, NICE_REPLY_A,SPF_FAIL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from [192.168.1.100] (unknown [49.207.214.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rnayak) by smtp.codeaurora.org (Postfix) with ESMTPSA id AEE5AC4338F; Thu, 28 Oct 2021 10:46:38 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 smtp.codeaurora.org AEE5AC4338F Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; spf=fail smtp.mailfrom=codeaurora.org Subject: Re: [PATCH v2 1/3] dt-bindings: usb: qcom,dwc3: Add multi-pd bindings for dwc3 qcom To: Ulf Hansson Cc: Bjorn Andersson , Stephen Boyd , Viresh Kumar , Sandeep Maheswaram , Rob Herring , Andy Gross , Greg Kroah-Hartman , Felipe Balbi , Doug Anderson , Matthias Kaehlcke , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, quic_pkondeti@quicinc.com, quic_ppratap@quicinc.com References: <1635152851-23660-1-git-send-email-quic_c_sanm@quicinc.com> <1635152851-23660-2-git-send-email-quic_c_sanm@quicinc.com> From: Rajendra Nayak Message-ID: Date: Thu, 28 Oct 2021 16:16:36 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/28/2021 4:05 PM, Ulf Hansson wrote: > [...] > >>>>> Got it. So in this case we could have the various display components >>>>> that are in the mdss gdsc domain set their frequency via OPP and then >>>>> have that translate to a level in CX or MMCX. How do we parent the power >>>>> domains outside of DT? I'm thinking that we'll need to do that if MMCX >>>>> is parented by CX or something like that and the drivers for those two >>>>> power domains are different. Is it basic string matching? >>>> >>>> In one way or another we need to invoke pm_genpd_add_subdomain() to link >>>> the two power-domains (actually genpds) together, like what was done in >>>> 3652265514f5 ("clk: qcom: gdsc: enable optional power domain support"). >>>> >>>> In the case of MMCX and CX, my impression of the documentation is that >>>> they are independent - but if we need to express that CX is parent of >>>> MMCX, they are both provided by rpmhpd which already supports this by >>>> just specifying .parent on mmcx to point to cx. >>> >>> I was trying to follow the discussion, but it turned out to be a bit >>> complicated to catch up and answer all things. In any case, let me >>> just add a few overall comments, perhaps that can help to move things >>> forward. >>> >>> First, one domain can have two parent domains. Both from DT and from >>> genpd point of view, just to make this clear. >>> >>> Although, it certainly looks questionable to me, to hook up the USB >>> device to two separate power domains, one to control power and one to >>> control performance. Especially, if it's really the same piece of HW >>> that is managing both things. >> [].. >>> Additionally, if it's correct to model >>> the USB GDSC power domain as a child to the CX power domain from HW >>> point of view, we should likely do that. >> >> I think this would still require a few things in genpd, since >> CX and USB GDSC are power domains from different providers. >> Perhaps a pm_genpd_add_subdomain_by_name()? >> > > I think of_genpd_add_subdomain() should help to address this. No? We only describe the provider nodes in DT and not the individual power domains. For instance GCC is the power domain provider which is in DT, and USB GDSC is one of the many power domains it supports, similarly RPMHPD is the provider node in DT and CX is one of the many power domains it supports. So we would need some non-DT way of hooking up power domains from two different providers as parent/child. -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation