From: "Heiko Stübner" <heiko@sntech.de>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH 1/2] arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E
Date: Wed, 19 Jun 2024 23:25:27 +0200 [thread overview]
Message-ID: <1938148.VZ3vTMCxA0@diego> (raw)
In-Reply-To: <793B93C3DF509ADC+f2b62f2b-bc05-4573-b783-ac0a6083a21e@radxa.com>
Am Mittwoch, 19. Juni 2024, 22:07:25 CEST schrieb FUKAUMI Naoki:
> Hello,
>
> On 6/20/24 04:31, Heiko Stuebner wrote:
> > On Wed, 19 Jun 2024 14:00:46 +0900, FUKAUMI Naoki wrote:
> >> use GPIO0_A2 as interrupt pin for PMIC. GPIO2_A6 was used for
> >> pre-production board.
> >>
> >>
> >
> > Applied, thanks!
> >
> > [1/2] arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E
> > commit: 02afd3d5b9fa4ffed284c0f7e7bec609097804fc
> >
> >
> > Patch 2 is not appropriate, sorry.
> >
> > The aliases are sorted this way since 2021 and the order is userspace-
> > facing. So for the last 3 years people have boards with the sdmmc as
> > mmc0 and changing this now would possibly break a number of boards.
>
> this is the reason I didn't add Fixes tag. I think this change in next
> major release is acceptable... but it's wrong?
Correct.
Because with that change, all people mounting /dev/mmcblk0p1 or
whatever in their system would break their userspace after a simple
kernel update.
And that falls under the "we don't break userspace" mantra.
People should be able to expect their system to keep booting with kernel
updates, without neededing to meticulously validate each kernel release.
Hence that mmc order needs to stay that way.
Heiko
prev parent reply other threads:[~2024-06-19 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 5:00 [PATCH 1/2] arm64: dts: rockchip: fix PMIC interrupt pin on ROCK Pi E FUKAUMI Naoki
2024-06-19 5:00 ` [PATCH 2/2] arm64: dts: rockchip: reorder mmc aliases for " FUKAUMI Naoki
2024-06-19 19:31 ` (subset) [PATCH 1/2] arm64: dts: rockchip: fix PMIC interrupt pin on " Heiko Stuebner
2024-06-19 20:07 ` FUKAUMI Naoki
2024-06-19 21:25 ` Heiko Stübner [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=1938148.VZ3vTMCxA0@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
/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).