Devicetree
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-pm@vger.kernel.org>, Andrew Davis <afd@ti.com>,
	Bryan Brattlof <bb@ti.com>, Vishal Mahaveer <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Markus Schneider-Pargmann <msp@baylibre.com>
Subject: Re: [PATCH v7 0/6] ti: k3-am62{a,p}x-sk: add opp frequencies
Date: Fri, 27 Sep 2024 08:40:03 -0500	[thread overview]
Message-ID: <20240927134003.j73m4cqo6q2orxvt@stream> (raw)
In-Reply-To: <20240926-ti-cpufreq-fixes-v5-v7-0-3c94c398fe8f@ti.com>

On 14:04-20240926, Dhruva Gole wrote:
[...]

> Bryan Brattlof (4):
>   arm64: dts: ti: k3-am62a: add opp frequencies
>   arm64: dts: ti: k3-am62a7-sk: add 1.4ghz opp entry
>   arm64: dts: ti: k3-am62p: add opp frequencies
>   arm64: dts: ti: k3-am62p5-sk: add 1.4ghz opp entry
> 
> Dhruva Gole (2):
>   arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon
>   cpufreq: ti-cpufreq: Update efuse/rev offsets in AM62 family

Please drop the dt patches from the series - they are completely
un-related. just fix the driver for compatibility and we can attack the
am625 cpufreq support fixup separately. AM62a/62p etc are independent of
this completely - those need to go to the DT maintainer separately

am625: Just post the driver fixups for backward compatibility and get it
merged prior to dt fixup.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  parent reply	other threads:[~2024-09-27 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26  8:34 [PATCH v7 0/6] ti: k3-am62{a,p}x-sk: add opp frequencies Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 1/6] arm64: dts: ti: k3-am62a: " Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 2/6] arm64: dts: ti: k3-am62a7-sk: add 1.4ghz opp entry Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 3/6] arm64: dts: ti: k3-am62p: add opp frequencies Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 4/6] arm64: dts: ti: k3-am62p5-sk: add 1.4ghz opp entry Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 5/6] arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon Dhruva Gole
2024-09-26  8:34 ` [PATCH v7 6/6] cpufreq: ti-cpufreq: Update efuse/rev offsets in AM62 family Dhruva Gole
2024-09-27 13:27   ` Nishanth Menon
2024-09-27 13:40 ` Nishanth Menon [this message]
2024-09-30  5:05   ` [PATCH v7 0/6] ti: k3-am62{a,p}x-sk: add opp frequencies Dhruva Gole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240927134003.j73m4cqo6q2orxvt@stream \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=vigneshr@ti.com \
    --cc=viresh.kumar@linaro.org \
    --cc=vishalm@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox