Linux clock framework development
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	Rob Herring (Arm) <robh@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] clk: keystone: syscon-clk: Do not use syscon helper to build regmap
Date: Fri, 24 Jan 2025 11:01:53 -0800	[thread overview]
Message-ID: <4b93a51bffd5ff7365d3998df92f0554.sboyd@kernel.org> (raw)
In-Reply-To: <20250123200209.lqdap6jdzz4ud37f@riveter>

Quoting Nishanth Menon (2025-01-23 12:02:09)
> On 12:19-20250123, Andrew Davis wrote:
> > The syscon helper device_node_to_regmap() is used to fetch a regmap
> > registered to a device node. It also currently creates this regmap
> > if the node did not already have a regmap associated with it. This
> > should only be used on "syscon" nodes. This driver is not such a
> > device and instead uses device_node_to_regmap() on its own node as
> > a hacky way to create a regmap for itself.
> > 
> > This will not work going forward and so we should create our regmap

Please reference the commit where this won't work anymore. It's hard to
know the urgency without this information.

> > the normal way by defining our regmap_config, fetching our memory
> > resource, then using the normal regmap_init_mmio() function.
> > 
> > Signed-off-by: Andrew Davis <afd@ti.com>
> 
> Tested-by: Nishanth Menon <nm@ti.com>
> 
> Could we get this routed to master as fixes asap please to get a sane 6.14?
> 

Sure. Can you resend with a Fixes tag?

> This is part of the fixes TI K3 platforms boot issues reported in
> https://lore.kernel.org/all/b2413460-ec8b-4c77-99b8-4c32b262439a@ti.com/
> 
> on the latest linus master v6.13-5001-gd0d106a2bd21 + linux
> next-20250123
> 
> Total set of patches tested with:
> https://lore.kernel.org/all/20250119182121.3956546-1-vaishnav.a@ti.com/
> https://lore.kernel.org/r/20250123181726.597144-1-afd@ti.com
> https://lore.kernel.org/r/20250123181913.597304-1-afd@ti.com
> https://lore.kernel.org/r/20250123182059.597491-1-afd@ti.com
> https://lore.kernel.org/r/20250123182234.597665-1-afd@ti.com
>

  reply	other threads:[~2025-01-24 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 18:19 [PATCH] clk: keystone: syscon-clk: Do not use syscon helper to build regmap Andrew Davis
2025-01-23 20:02 ` Nishanth Menon
2025-01-24 19:01   ` Stephen Boyd [this message]
2025-01-24 22:12     ` Nishanth Menon
2025-03-04 19:49 ` Stephen Boyd

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=4b93a51bffd5ff7365d3998df92f0554.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=afd@ti.com \
    --cc=lee@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=vigneshr@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