All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artur Weber <aweber.kernel@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ray Jui <rjui@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Markus Mayer <markus.mayer@linaro.org>,
	Tim Kryger <tim.kryger@linaro.org>,
	Matt Porter <matt.porter@linaro.org>,
	Markus Mayer <mmayer@broadcom.com>,
	Christian Daudt <csd@broadcom.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 0/3] gpio: bcm-kona: Various GPIO fixups
Date: Thu, 6 Feb 2025 18:48:36 +0100	[thread overview]
Message-ID: <50371e83-917d-4b0c-af4e-ec1afa7e8c94@gmail.com> (raw)
In-Reply-To: <981d534a-a439-40c2-bd24-2e518846580e@gmail.com>

On 6.02.2025 16:37, Artur Weber wrote:
> On 6.02.2025 10:34, Linus Walleij wrote:
>> Hi Artur,
>>
>> On Thu, Jan 30, 2025 at 6:10 PM Artur Weber <aweber.kernel@gmail.com> 
>> wrote:
>>
>>> Fixes two issues that were preventing GPIO from working correctly:
>>>
>>> - Lock/unlock functions tried to write the wrong bit to the unlock
>>>    registers for GPIOs with numbers larger than 32
>>>
>>> - GPIOs only initialized as IRQs did not unlock the configuration
>>>    registers, causing IRQ-related configuration (e.g. setting the IRQ
>>>    type) to fail.
>>>
>>> Also includes a minor fix to add a missing newline to an error message.
>>>
>>> Tested on a Samsung Galaxy Grand Neo (baffinlite rev02) with a BCM23550
>>> (DTS not yet in mainline).
>>>
>>> Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
>>
>> Looks good to me, do you want to resend the patches picking up the
>> Acks or do you want me to apply as-is?
> 
> I'll send a v2 in a second with the style fixes suggested by Markus[1].
> After that, it should be good to go.
> 
>> Should this go in as urgent fixes (-rcN) or as nonurgent?
>>
>> The DTS not being mainline suggests nonurgent but are there
>> other systems suffering?
> 
> Non-urgent is fine. AFAICT the only upstream-supported Broadcom Kona
> devices at the moment are old Broadcom dev boards; while they
> technically are also affected by the bug, I doubt anyone's actively
> using them. As for the devices I'm testing with, there's still quite
> a few fixups I plan to make before I consider them ready to upstream.
> 
> Best regards
> Artur
> 
> [1] https://lore.kernel.org/lkml/ 
> CAGt4E5sqd_Aojk+boD5K5EiRfOsiU+jYY5EV0DP6TFut291HnQ@mail.gmail.com/

v2 sent: https://lore.kernel.org/lkml/20250206-kona-gpio-fixes-v2-0-409135eab780@gmail.com/T/#t

Best regards
Artur

      reply	other threads:[~2025-02-06 17:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 17:10 [PATCH 0/3] gpio: bcm-kona: Various GPIO fixups Artur Weber
2025-01-30 17:10 ` [PATCH 1/3] gpio: bcm-kona: Fix GPIO lock/unlock for banks above bank 0 Artur Weber
2025-01-30 21:33   ` Florian Fainelli
2025-01-30 22:00     ` Markus Mayer
2025-01-30 17:10 ` [PATCH 2/3] gpio: bcm-kona: Make sure GPIO bits are unlocked when requesting IRQ Artur Weber
2025-01-30 21:35   ` Florian Fainelli
2025-01-30 21:46     ` Artur Weber
2025-01-30 22:07       ` Florian Fainelli
2025-01-30 22:13   ` Florian Fainelli
2025-01-30 22:36   ` Markus Mayer
2025-01-30 17:10 ` [PATCH 3/3] gpio: bcm-kona: Add missing newline to dev_err format string Artur Weber
2025-01-30 18:41   ` Florian Fainelli
2025-01-30 22:08     ` Markus Mayer
2025-02-06  9:34 ` [PATCH 0/3] gpio: bcm-kona: Various GPIO fixups Linus Walleij
2025-02-06  9:36   ` Linus Walleij
2025-02-06 15:37   ` Artur Weber
2025-02-06 17:48     ` Artur Weber [this message]

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=50371e83-917d-4b0c-af4e-ec1afa7e8c94@gmail.com \
    --to=aweber.kernel@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=brgl@bgdev.pl \
    --cc=csd@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.mayer@linaro.org \
    --cc=matt.porter@linaro.org \
    --cc=mmayer@broadcom.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=tim.kryger@linaro.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.