From: "Sven Peter" <sven@svenpeter.dev>
To: "Hector Martin" <marcan@marcan.st>,
"Jassi Brar" <jassisinghbrar@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>
Cc: "Alyssa Rosenzweig" <alyssa@rosenzweig.io>,
"Mark Kettenis" <kettenis@openbsd.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] Apple mailbox fixup: switch to generic compatibles
Date: Thu, 09 Dec 2021 17:33:13 +0100 [thread overview]
Message-ID: <3fb087c1-2d67-4527-ad63-1f8ce54e6965@www.fastmail.com> (raw)
In-Reply-To: <20211209055049.99205-1-marcan@marcan.st>
On Thu, Dec 9, 2021, at 06:50, Hector Martin wrote:
> Hi folks,
>
> Just a quick fix for the Apple mailbox compatible. Similar to [1], we
> intend to use SoC-specific compatibles only for potential quirks, and
> rely on a generic compatible to allow for forward-compatibility as long
> as things don't break.
I vaguely remember a brief discussion about this and I think we thought about
using "t6000-asc", "t8103-asc" in this case since this specific mailbox hardware
was only introduced in the M1. I think Apple calls this variant ascwrap-v4
and m3wrap-v2.
Doing it like you suggested is also fine with me though.
Sven
next prev parent reply other threads:[~2021-12-09 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 5:50 [PATCH 0/2] Apple mailbox fixup: switch to generic compatibles Hector Martin
2021-12-09 5:50 ` [PATCH 1/2] dt-bindings: mailbox: apple,mailbox: Add generic and t6000 compatibles Hector Martin
2021-12-09 14:16 ` [PATCH 1/2] dt-bindings: mailbox: apple, mailbox: " Mark Kettenis
2021-12-15 16:59 ` [PATCH 1/2] dt-bindings: mailbox: apple,mailbox: " Rob Herring
2021-12-15 17:13 ` Sven Peter
2021-12-15 17:14 ` Sven Peter
2021-12-09 5:50 ` [PATCH 2/2] mailbox: apple: Bind to generic compatibles Hector Martin
2021-12-09 16:33 ` Sven Peter [this message]
2021-12-13 3:55 ` [PATCH 0/2] Apple mailbox fixup: switch " Hector Martin
2021-12-15 8:43 ` Sven Peter
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=3fb087c1-2d67-4527-ad63-1f8ce54e6965@www.fastmail.com \
--to=sven@svenpeter.dev \
--cc=alyssa@rosenzweig.io \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=kettenis@openbsd.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=robh+dt@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).