Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: linus.walleij@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, florian.fainelli@broadcom.com,
	andrea.porta@suse.com, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/7] arm64: dts: broadcom: bcm2712: Add one more GPIO node
Date: Mon, 5 Aug 2024 12:37:48 +0300	[thread overview]
Message-ID: <20240805093748.zd4pkmtaepobwale@localhost.localdomain> (raw)
In-Reply-To: <12fd21d4-8061-41d0-b60f-d02102eca1c6@gmx.net>

Hi,

On 08-02 21:08, Stefan Wahren wrote:
> 
> Hi Ivan,
> 
> Am 31.07.24 um 08:28 schrieb Ivan T. Ivanov:
> > Add GPIO and related interrupt controller nodes and wire one
> > of the lines to power button.
> > 
> Since we enable the GPIO controller here, i think we should provide the
> relevant gpio-line-names for the Raspberry Pi 5 board. So gpioinfo works
> from the beginning. Doesn't need to be in this patch directly.
> 

Sure, I was planning to send this later to not make this patchest too large.

Regards,
Ivan



  reply	other threads:[~2024-08-05  9:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  6:28 [PATCH 0/7] Add pin control driver for BCM2712 SoC Ivan T. Ivanov
2024-07-31  6:28 ` [PATCH 1/7] dt-bindings: pinctrl: Add support for Broadcom STB pin controller Ivan T. Ivanov
2024-08-01  8:17   ` Krzysztof Kozlowski
2024-08-01  8:38     ` Ivan T. Ivanov
2024-08-01 14:19       ` Krzysztof Kozlowski
2024-08-05  9:27         ` Ivan T. Ivanov
2024-08-02 18:09   ` Stefan Wahren
2024-08-12 16:28     ` Dave Stevenson
2024-08-22 10:54       ` Stefan Wahren
2024-07-31  6:28 ` [PATCH 2/7] pinctrl: bcm: Add STB family pin controller driver Ivan T. Ivanov
2024-08-02 10:22   ` Phil Elwell
2024-08-02 18:36   ` Stefan Wahren
2024-08-05  9:13   ` Stefan Wahren
2024-07-31  6:28 ` [PATCH 3/7] arm64: dts: broadcom: Add support for BCM2712 Ivan T. Ivanov
2024-07-31 21:57   ` Florian Fainelli
2024-08-01  6:45     ` Ivan T. Ivanov
2024-07-31  6:28 ` [PATCH 4/7] arm64: dts: broadcom: bcm2712: Add pin controller nodes Ivan T. Ivanov
2024-08-02 19:16   ` Stefan Wahren
2024-07-31  6:28 ` [PATCH 5/7] arm64: dts: broadcom: bcm2712: Add one more GPIO node Ivan T. Ivanov
2024-07-31 22:11   ` Florian Fainelli
2024-08-01  7:19     ` Ivan T. Ivanov
2024-08-02 18:49   ` Stefan Wahren
2024-08-02 19:08   ` Stefan Wahren
2024-08-05  9:37     ` Ivan T. Ivanov [this message]
2024-07-31  6:28 ` [PATCH 6/7] arm64: dts: broadcom: bcm2712: Add second SDHCI controller node Ivan T. Ivanov
2024-08-02 19:01   ` Stefan Wahren
2025-05-12 13:42     ` Ivan T. Ivanov
2024-07-31  6:28 ` [PATCH 7/7] arm64: dts: broadcom: bcm2712: Add UARTA " Ivan T. Ivanov
2024-07-31 22:13   ` Florian Fainelli
2024-08-01  7:50     ` Ivan T. Ivanov
2024-08-02 19:12   ` Stefan Wahren
2024-07-31 14:25 ` [PATCH 0/7] Add pin control driver for BCM2712 SoC Rob Herring (Arm)

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=20240805093748.zd4pkmtaepobwale@localhost.localdomain \
    --to=iivanov@suse.de \
    --cc=andrea.porta@suse.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wahrenst@gmx.net \
    /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