From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: <linux-rockchip@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: (subset) [PATCH v2 0/4] rockchip: Fix several DT validation errors
Date: Fri, 18 Oct 2024 12:01:29 +0200 [thread overview]
Message-ID: <D4YUFQSAR6RX.LS5RY03XCV3J@cknow.org> (raw)
In-Reply-To: <4604343.LvFx2qVVIh@diego>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Hi,
On Fri Oct 18, 2024 at 11:37 AM CEST, Heiko Stübner wrote:
> Am Freitag, 18. Oktober 2024, 11:35:51 CEST schrieb Diederik de Haas:
> > On Wed Oct 16, 2024 at 2:35 PM CEST, Diederik de Haas wrote:
> > > On Wed Oct 16, 2024 at 11:41 AM CEST, Diederik de Haas wrote:
> > > > Please revert the 4th patch.
> > > >
> > > > I must have messed up my testing previously, but BT does not work on the
> > > > PineNote with the 4th patch applied and does work with it reverted.
> > >
> > > FWIW, I figured out what went wrong.
> > > My testing was correct, but redo-ing the implementation to make it ready
> > > for submission wasn't very smart.
> > >
> > > With ``shutdown-gpios = <&gpio0 RK_PC4 GPIO_ACTIVE_HIGH>;``
> > > it does work correctly, but I forgot to change GPIO_ACTIVE_LOW to
> > > GPIO_ACTIVE_HIGH before submitting.
> > >
> > > I'll first figure out a better procedure before making a new submission,
> > > so the revert is still the best approach IMO.
> >
> > I've now done a new submission:
> > https://lore.kernel.org/linux-rockchip/20241018092237.6774-1-didi.debian@cknow.org/
> >
> > So please don't revert the 4th patch now.
>
> hehe ok :-) .
> I meant to ask if the fix wasn't simply toggling the gpio polarity, and
> I guess with your patch you were faster than my question.
I already knew that was the fix the moment I opened the other dts(i)
files with the same wireless+bt module.
While it was tempting to immediately sent the fix, I realized that
being (too) eager to sent it out would be a recipe for another screw up.
And I wanted to think through why it happened in the first place and
that's because my submission process is all manual with an 'insane' long
`git send-email` command, hand-crafted.
So I better learn `b4` (properly) so my focus can be on the patches and
less on the submission process.
Making a mistake/screw up sucks, but not learning from them is bad.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-10-18 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 11:15 [PATCH v2 0/4] rockchip: Fix several DT validation errors Diederik de Haas
2024-10-08 11:15 ` [PATCH v2 1/4] arm64: dts: rockchip: Add PD to csi dphy node on rk356x Diederik de Haas
2024-10-08 12:32 ` Michael Riesch
2024-10-08 18:55 ` Diederik de Haas
2024-10-08 11:15 ` [PATCH v2 2/4] arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328 Diederik de Haas
2024-10-08 11:15 ` [PATCH v2 3/4] arm64: dts: rockchip: Fix wakeup prop names on PineNote BT node Diederik de Haas
2024-10-08 11:15 ` [PATCH v2 4/4] arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes Diederik de Haas
2024-10-08 19:28 ` (subset) [PATCH v2 0/4] rockchip: Fix several DT validation errors Heiko Stuebner
2024-10-16 9:41 ` Diederik de Haas
2024-10-16 12:35 ` Diederik de Haas
2024-10-18 9:35 ` Diederik de Haas
2024-10-18 9:37 ` Heiko Stübner
2024-10-18 10:01 ` Diederik de Haas [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=D4YUFQSAR6RX.LS5RY03XCV3J@cknow.org \
--to=didi.debian@cknow.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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