Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <6ec58e9c-0661-cb97-b133-cdcc40d4e4f0@ti.com>
Date:   Thu, 10 Aug 2023 19:49:28 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.14.0
Subject: Re: [PATCH 2/3] arm64: dts: ti: k3-j7200: Add the supported
 frequencies for A72
To:     Nishanth Menon <nm@ti.com>
CC:     Apurva Nandan <a-nandan@ti.com>,
        Vignesh Raghavendra <vigneshr@ti.com>,
        Tero Kristo <kristo@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Rafael J Wysocki <rafael@kernel.org>,
        Daniel Lezcano <daniel.lezcano@linaro.org>,
        Amit Kucheria <amitk@kernel.org>,
        Zhang Rui <rui.zhang@intel.com>,
        <linux-arm-kernel@lists.infradead.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <linux-pm@vger.kernel.org>, Keerthy J <j-keerthy@ti.com>,
        <u-kumar1@ti.com>
References: <20230809173905.1844132-1-a-nandan@ti.com>
 <20230809173905.1844132-3-a-nandan@ti.com>
 <20230809190943.unpcbrinyn5ppei7@hydrated>
 <ab69c4df-708f-8fff-a58b-a6531e15627b@ti.com>
 <20230810125327.pq2fxda7dpv2qf7t@seizing>
Content-Language: en-US
From:   "Kumar, Udit" <u-kumar1@ti.com>
In-Reply-To: <20230810125327.pq2fxda7dpv2qf7t@seizing>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 8/10/2023 6:23 PM, Nishanth Menon wrote:
> On 17:23-20230810, Kumar, Udit wrote:
> [..]
>>>> +		opp1-750000000 {
>>>> +			opp-hz = /bits/ 64 <750000000>;
>>>>    		};
>>>>    	};
>>>> -- 
>>>> 2.34.1
>>>>
>>> [..]
>>> This wont work:
>>>
>>> a) in u-boot's falcon boot mode and puts unrelated responsibility to
>>> bootloader (u-boot is not the only bootloader in the party here).
>>> b) Further, the reason for doing the opp detection in the kernel is
>>> due to the severity of consequence of attempting to run a lower rated
>>> chip at higher frequency - PoH (Power on Hours) or physical damage can
>>> result.
>>> c) Finally, in a virtualized environment: TISCI will get DM (Device
>>> Manager) to arbitrate between the each of the VM's request, but if
>>> the VM's are'nt self sufficient, we will have DM making wrong choices
>>> resulting in (b) condition again.
>>>
>>> This is the reason why drivers/cpufreq/ti-cpufreq.c exists and all SoCs
>>> that have OPPs from TI is handled in the kernel itself.

Thanks to pointing to this driver.