From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0AB53C3DA78 for ; Tue, 17 Jan 2023 17:42:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235194AbjAQRlz (ORCPT ); Tue, 17 Jan 2023 12:41:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33780 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232629AbjAQRkd (ORCPT ); Tue, 17 Jan 2023 12:40:33 -0500 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1C80521D2 for ; Tue, 17 Jan 2023 09:33:45 -0800 (PST) Received: by mail-wm1-x329.google.com with SMTP id l8so5739700wms.3 for ; Tue, 17 Jan 2023 09:33:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=p9X/E0nTuGg/ziYb/sqmkQprPxdu3YzscqPmDsFFV0A=; b=XL51Sdalg82WE+JbLXz2SEBksj+gjR62nkt4OBlAalqXk0EgjRcohyFDzhBxNcSjpP o83Z8TyUspsUYg7ojxlj/77unJED9W7maQDtSjFs6PqFtziXLzM5SydD5zLrE1edKgUL g6fE7WZ8R9oG4cqdG/Gd+lfL7j3pGG37+8TF04Xye8h5Si1afbg4UV0XySn27QxamMl9 QneAMxb1z2s6hQ83ZW+cRXQz0SD9teCbdlX1glNqfpo/tiO55hXoH8gMQvSWrakRO5rc 4ze35KGmUc7WLSUhxBosJVhWMdnwFrcffGd4fVSWb+CnJjEmKjRgBQ0M7ME8oZC5aw9h EZ2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=p9X/E0nTuGg/ziYb/sqmkQprPxdu3YzscqPmDsFFV0A=; b=VRwi3QDlWt4lX0gPcGAiRTdovAGH8R9p0h0aIjoT8qBoNTHD+7lMmgKqKYbl0KbH2c DhldvAMOaklp+MG8gf6ZC63j8EbwJ+nlEePrfMnWY2HjzaJubbpZBLc+Jz0ypyNMFdll evylQoJfhgLFFcBv6c1yLek9RQ+WjkCY1nxDE4LgyY3BrJrIsWJ0jsGDrQNyMJW1k37I xCWiVWwoorUHqe/iNjnVentUxpfJlIReRJdklzBTXD6HC2LNDaOtbWV2vyq3tZsd+Q8o 4/qqs+OgiOVievFM2zvxWiNa404YSAZMaiFvjMANsTEstOtLiFFKReF1lIpQL1/Q9izO 2ugQ== X-Gm-Message-State: AFqh2krsJyBumvg0Ev+QMnVDX2fS2PA+uhiNzRBCrkAAqD/uQyYLIsjl RfL56863CG1RxQgwO6DXajmiuA== X-Google-Smtp-Source: AMrXdXsv+55G5FnSXPMY9NBzuWWVoycH0E4lbFURb3YtiipIhLiTvNKCbWm0MGOZRJa7Bi5vFbDrOQ== X-Received: by 2002:a1c:7415:0:b0:3da:fd07:1e3 with SMTP id p21-20020a1c7415000000b003dafd0701e3mr3750361wmc.22.1673976824626; Tue, 17 Jan 2023 09:33:44 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id he12-20020a05600c540c00b003d9ddc82450sm36592707wmb.45.2023.01.17.09.33.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Jan 2023 09:33:43 -0800 (PST) Message-ID: <754f8193-09ec-8bbf-e0d4-898525dc242f@linaro.org> Date: Tue, 17 Jan 2023 18:33:41 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: sc7280: Add cpu and llcc BWMON (=> interconnect issue) Content-Language: en-US To: Matthias Kaehlcke Cc: Rajendra Nayak , Georgi Djakov , agross@kernel.org, andersson@kernel.org, konrad.dybcio@somainline.org, robh+dt@kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-pm@vger.kernel.org, Douglas Anderson , Stephen Boyd References: <20220902043511.17130-1-quic_rjendra@quicinc.com> <20220902043511.17130-5-quic_rjendra@quicinc.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/01/2023 18:27, Matthias Kaehlcke wrote: > >>> which would set the initially bandwidths to 0 and determine the actually >>> needed bandwidth. But since the driver isn't probed the initial >>> bandwidths stay at INT_MAX. >>> >>> This isn't actually an issue with this patch, but how the interconnect >>> framework deals with devices that are registered on the bus, but aren't >>> probed (yet). Not sure how this would be best fixed. Georgi, do you have >>> any ideas? >> >> Why the device is not probed (yet)? If it is registered, it will come >> soon during boot up. > > Because CONFIG_QCOM_ICC_BWMON is not enabled for the board in question (see > above). It could be enabled as a short term mitigtion, however we shouldn't > require drivers to be enabled just because the DT has a corresponding node. It's the same case as with all other interconnect leafs/consumers. The same behavior if you do not have it enabled, right? If not, I wonder what is here different? Best regards, Krzysztof