[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241213232933.4661-1-johnliu@nvidia.com>
Date: Fri, 13 Dec 2024 15:29:33 -0800
From: Johnny Liu <johnliu@...dia.com>
To: <krzk@...nel.org>
CC: <airlied@...il.com>, <conor+dt@...nel.org>, <devicetree@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>, <johnliu@...dia.com>,
<jonathanh@...dia.com>, <krzk+dt@...nel.org>, <linux-kernel@...r.kernel.org>,
<linux-media@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
<luca.ceresoli@...tlin.com>, <maarten.lankhorst@...ux.intel.com>,
<mperttunen@...dia.com>, <mripard@...nel.org>, <robh@...nel.org>,
<simona@...ll.ch>, <skomatineni@...dia.com>, <thierry.reding@...il.com>,
<tzimmermann@...e.de>
Subject: Re: [PATCH v1 1/5] dt-bindings: display: tegra: Add actmon information
> On Tue, Dec 10, 2024 at 09:45:50AM -0800, Johnny Liu wrote:
> > An activity monitor (actmon) is used to measure the device runtime
> > utilization to help drive software power management policies.
> >
> > Extend the reg space to include actmon aperture for actmon configuration
> > through host1x.
>
> We kind of see that from the diff. Say what we do not see, e.g. ABI
> impact or why this is flexible/optional for existing devices.
Since actmon is not well-supported for the previous chips (e.g. T210,
T186, T194, and etc) in this patch series, it's essential to make the
specification of regs property optional for the previous chips.
Enablement/Disablement of actmon won't affect the host1x main functionality.
Its main job is to monitor the engines behind the host1x and serve for
telemetry purpose.
I could update the commit message to include the above reason. Please
let me know if more information is required.
Thanks,
Johnny
Powered by blists - more mailing lists