On September 2, 2024 thus sayeth Dhruva Gole:
> Since the efuse_offset is basically derived from the syscon node, we no
> longer need to use any efuse_offset for AM625. This is in line with how
> the AM62Ax and AM62Px are already doing.
>
> Signed-off-by: Dhruva Gole <d-gole@xxxxxx>
> ---
> drivers/cpufreq/ti-cpufreq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c
> index ba621ce1cdda..98e320832f78 100644
> --- a/drivers/cpufreq/ti-cpufreq.c
> +++ b/drivers/cpufreq/ti-cpufreq.c
> @@ -313,7 +313,7 @@ static const struct soc_device_attribute k3_cpufreq_soc[] = {
>
> static struct ti_cpufreq_soc_data am625_soc_data = {
> .efuse_xlate = am625_efuse_xlate,
> - .efuse_offset = 0x0018,
> + .efuse_offset = 0x0,
> .efuse_mask = 0x07c0,
> .efuse_shift = 0x6,
> .rev_offset = 0x0014,
This may work but it really shouldn't. Unfortunately when I sent out the
am62ax and am62px support I missed the .rev_offset and now it's pointed
to some random spot in the WKUP_CTRL_MMR space. How it worked on my
bench was complete luck (or bad luck depending on how we view this).
We'll need to pull out a OMAP3 chip and try to separate the OMAP and K3
OPN decoding before we can move the .efuse_offset
~Bryan
