linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Elwell <phil@raspberrypi.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Herve Codina <herve.codina@bootlin.com>,
	Andrea della Porta <andrea.porta@suse.com>,
	 Arnd Bergmann <arnd@arndb.de>,
	 "maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
	<bcm-kernel-feedback-list@broadcom.com>,
	bhelgaas@google.com, brgl@bgdev.pl,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Conor Dooley <conor+dt@kernel.org>,
	derek.kiernan@amd.com,  devicetree@vger.kernel.org,
	dragan.cvetic@amd.com,
	 Florian Fainelli <florian.fainelli@broadcom.com>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	krzk+dt@kernel.org, kw@linux.com,
	 Linus Walleij <linus.walleij@linaro.org>,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-clk@vger.kernel.org,  linux-gpio@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	 "open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
	<linux-pci@vger.kernel.org>,
	 "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-rpi-kernel@lists.infradead.org>,
	lpieralisi@kernel.org,  luca.ceresoli@bootlin.com,
	manivannan.sadhasivam@linaro.org,  masahiroy@kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	 Rob Herring <robh@kernel.org>,
	saravanak@google.com, Stephen Boyd <sboyd@kernel.org>,
	 thomas.petazzoni@bootlin.com, Stefan Wahren <wahrenst@gmx.net>,
	 Will Deacon <will@kernel.org>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: Re: [PATCH v6 00/10] Add support for RaspberryPi RP1 PCI device using a DT overlay
Date: Thu, 13 Feb 2025 17:57:37 +0000	[thread overview]
Message-ID: <CAMEGJJ0QbzCScfTRA_pw_8A=iMYMAAFs69zFNLwcOxF5Syugpw@mail.gmail.com> (raw)
In-Reply-To: <821d4c74-09b0-4c1b-b8ef-f8c08d0f6b5b@lunn.ch>

On Thu, 13 Feb 2025 at 17:45, Andrew Lunn <andrew@lunn.ch> wrote:
>
> > > Or do you mean a custom board, which has a CPU, RP1 and the button and
> > > fan are directly on this custom board? You then want a board DTS which
> > > includes all these pieces?
> >
> > That depends on whether you count the Raspberry Pi 5 as a custom board.
>
> So you mean the Pi 5 board would itself make use of the resources the
> RP1 device has? They are not simply connected to headers for plugin
> boards, but used by the main board? Hence you want to describe them in
> the board .DTS file.

That's correct. But even for plug-in devices, those which are on
non-discoverable buses need overlays to declare them, which causes a
problem when the overlay application happens before the kernel is
started.

Phil

  reply	other threads:[~2025-02-13 17:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 15:18 [PATCH v6 00/10] Add support for RaspberryPi RP1 PCI device using a DT overlay Phil Elwell
2025-02-13 16:14 ` Herve Codina
2025-02-13 16:26   ` Andrew Lunn
2025-02-13 16:30     ` Phil Elwell
2025-02-13 17:07       ` Herve Codina
2025-02-13 17:29         ` Phil Elwell
2025-02-13 17:50           ` Andrew Lunn
2025-02-13 18:00             ` Phil Elwell
2025-02-13 17:45       ` Andrew Lunn
2025-02-13 17:57         ` Phil Elwell [this message]
2025-02-13 18:53           ` Herve Codina
2025-02-13 20:15             ` Phil Elwell
2025-02-13 21:06               ` Herve Codina
2025-02-13 21:12                 ` Phil Elwell
2025-02-17 15:53                   ` Herve Codina
2025-02-17 17:03                     ` Phil Elwell
2025-02-17 17:55                       ` Herve Codina
2025-02-18 11:41                         ` Phil Elwell
2025-02-13 16:27   ` Phil Elwell
2025-03-10 13:59     ` Andrea della Porta
2025-03-10 14:21       ` Phil Elwell
2025-03-10 16:26         ` Andrea della Porta
  -- strict thread matches above, loose matches on Subject: below --
2025-01-13 14:57 Andrea della Porta

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='CAMEGJJ0QbzCScfTRA_pw_8A=iMYMAAFs69zFNLwcOxF5Syugpw@mail.gmail.com' \
    --to=phil@raspberrypi.com \
    --cc=andrea.porta@suse.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=brgl@bgdev.pl \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=derek.kiernan@amd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@amd.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herve.codina@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=kw@linux.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=masahiroy@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=sboyd@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wahrenst@gmx.net \
    --cc=will@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).