public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ayush Singh <ayush@beagleboard.org>
Cc: Herve Codina <herve.codina@bootlin.com>,
	xypron.glpk@gmx.de, Jason Kridner <jkridner@beagleboard.org>,
	Deepak Khatri <lorforlinux@beagleboard.org>,
	Dhruva Gole <d-gole@ti.com>,
	Robert Nelson <robertcnelson@beagleboard.org>,
	Andrew Davis <afd@ti.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Pantelis Antoniou <pantelis.antoniou@gmail.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [Discussion] Global vs Local devicetree overlays for addon board + connector setups
Date: Sun, 4 May 2025 15:13:01 +0200	[thread overview]
Message-ID: <2025050426-expel-overarch-3454@gregkh> (raw)
In-Reply-To: <eefa06c1-478f-4670-80c7-4bde8c808e1b@beagleboard.org>

On Sun, May 04, 2025 at 06:30:24PM +0530, Ayush Singh wrote:
> 
> On 5/4/25 18:20, Greg Kroah-Hartman wrote:
> > On Sun, May 04, 2025 at 06:03:26PM +0530, Ayush Singh wrote:
> > > > It depends on the bus the device is added.
> > > > when an overlay is applied by the kernel, OF_RECONFIG_* events are
> > > > triggered. Some buses handle them:
> > > > 
> > > > 	$ git grep OF_RECONFIG_CHANGE
> > > > 	drivers/bus/imx-weim.c: case OF_RECONFIG_CHANGE_ADD:
> > > > 	drivers/bus/imx-weim.c: case OF_RECONFIG_CHANGE_REMOVE:
> > > > 	drivers/gpio/gpiolib-of.c:      case OF_RECONFIG_CHANGE_ADD:
> > > > 	drivers/gpio/gpiolib-of.c:      case OF_RECONFIG_CHANGE_REMOVE:
> > > > 	drivers/i2c/i2c-core-of.c:      case OF_RECONFIG_CHANGE_ADD:
> > > > 	drivers/i2c/i2c-core-of.c:      case OF_RECONFIG_CHANGE_REMOVE:
> > > > 	drivers/of/dynamic.c: * Return: OF_RECONFIG_CHANGE_REMOVE on device going from enabled to
> > > > 	drivers/of/dynamic.c: * disabled, OF_RECONFIG_CHANGE_ADD on device going from disabled to
> > > > 	drivers/of/dynamic.c:   return new_state ? OF_RECONFIG_CHANGE_ADD : OF_RECONFIG_CHANGE_REMOVE;
> > > > 	drivers/of/platform.c:  case OF_RECONFIG_CHANGE_ADD:
> > > > 	drivers/of/platform.c:  case OF_RECONFIG_CHANGE_REMOVE:
> > > > 	drivers/spi/spi.c:      case OF_RECONFIG_CHANGE_ADD:
> > > > 	drivers/spi/spi.c:      case OF_RECONFIG_CHANGE_REMOVE:
> > > > 	include/linux/of.h:     OF_RECONFIG_CHANGE_ADD,
> > > > 	include/linux/of.h:     OF_RECONFIG_CHANGE_REMOVE,
> > > 
> > > Well, if some bus does handle the event, I guess it is a bug in the
> > > subsystems that do not? Maybe Greg Kroah-Hartman can clarify the expected
> > > behavior here? Maybe we are in transition phase here.
> > Perhaps those other busses just do not have OF devices and so they never
> > needed to add that functionality to them?
> > 
> > If they do, then by all means add that code.  OF devices are not
> > possible for many bus types, so there shouldn't be a need to add this to
> > the driver core, right?
> > 
> > thanks,
> > 
> > greg k-h
> 
> 
> UART devices are pretty common in both Beagle capes and MikroBUS. So I think
> that will probably need to be added at some point.

uarts are not a bus, they are a type of device that is implemented by
many different bus drivers (pci, USB, etc.)

thanks,

greg k-h

  reply	other threads:[~2025-05-04 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 12:07 [Discussion] Global vs Local devicetree overlays for addon board + connector setups Ayush Singh
2025-04-30 14:09 ` Herve Codina
2025-04-30 14:31   ` Geert Uytterhoeven
2025-04-30 14:58     ` Herve Codina
2025-05-01  6:05   ` Ayush Singh
2025-05-04 12:33   ` Ayush Singh
2025-05-04 12:50     ` Greg Kroah-Hartman
2025-05-04 13:00       ` Ayush Singh
2025-05-04 13:13         ` Greg Kroah-Hartman [this message]
2025-05-05  6:43           ` Geert Uytterhoeven
2025-05-05 20:56             ` Rob Herring
2025-06-04 19:03 ` Andrew Davis
2025-06-05  7:22   ` Ayush Singh
2025-06-09 14:13     ` Luca Ceresoli

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=2025050426-expel-overarch-3454@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=afd@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=d-gole@ti.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=herve.codina@bootlin.com \
    --cc=jkridner@beagleboard.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorforlinux@beagleboard.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=pantelis.antoniou@gmail.com \
    --cc=robertcnelson@beagleboard.org \
    --cc=xypron.glpk@gmx.de \
    /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