mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nishanth Menon <nm@ti.com>
Cc: Andrew Davis <afd@ti.com>, Peter Rosin <peda@axentia.se>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-kernel@vger.kernel.org,
	"Rob Herring (Arm)" <robh@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] mux: mmio: Do not use syscon helper to build regmap
Date: Fri, 24 Jan 2025 06:26:16 +0100	[thread overview]
Message-ID: <2025012446-unturned-frugality-7a20@gregkh> (raw)
In-Reply-To: <20250123200412.6zuhlbz4zorazdhq@deport>

On Thu, Jan 23, 2025 at 02:04:12PM -0600, Nishanth Menon wrote:
> On 12:20-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
> > 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>
> 
> Greg, Peter,
> 
> 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
> 
> Could we get this routed to master as fixes asap please to get a sane 6.14?

Our trees are of course closed right now due to the merge window, you
know that :)

So we can take things after -rc1 is out, and route bugfixes for
6.14-final and new stuff for 6.15-rc1, like always.  It's hard to see
that this is just a bugfix, but if it is, it needs a Fixes: tag at the
very least, right?

thanks,

greg k-h

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 18:20 Andrew Davis
2025-01-23 20:04 ` Nishanth Menon
2025-01-24  5:26   ` Greg Kroah-Hartman [this message]
2025-01-24 14:33     ` Nishanth Menon
2025-01-24 22:16     ` Nishanth Menon
2025-05-01 17:56 ` Krzysztof Kozlowski

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=2025012446-unturned-frugality-7a20@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=afd@ti.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=peda@axentia.se \
    --cc=robh@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

all inboxes | Powered by JetHome®