From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Aditya Garg <gargaditya08@live.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Aun-Ali Zaidi <admin@kodeit.net>, "paul@mrarm.io" <paul@mrarm.io>,
Orlando Chamberlain <orlandoch.dev@gmail.com>
Subject: Re: [PATCH RFC] staging: Add driver to communicate with the T2 Security Chip
Date: Mon, 10 Mar 2025 15:54:50 +0200 [thread overview]
Message-ID: <Z87vKltfijzRtlpL@smile.fi.intel.com> (raw)
In-Reply-To: <ef8dcf7a-34ed-4b27-a154-e01bc167d4e6@arm.com>
On Mon, Mar 10, 2025 at 01:49:13PM +0000, Robin Murphy wrote:
> On 2025-03-09 8:40 am, Aditya Garg wrote:
> > From: Paul Pawlowski <paul@mrarm.io>
> >
> > This patch adds a driver named apple-bce, to add support for the T2
> > Security Chip found on certain Macs.
> >
> > The driver has 3 main components:
> >
> > BCE (Buffer Copy Engine) - this is what the files in the root directory
> > are for. This estabilishes a basic communication channel with the T2.
> > VHCI and Audio both require this component.
> >
> > VHCI - this is a virtual USB host controller; keyboard, mouse and
> > other system components are provided by this component (other
> > drivers use this host controller to provide more functionality).
> >
> > Audio - a driver for the T2 audio interface, currently only audio
> > output is supported.
> >
> > Currently, suspend and resume for VHCI is broken after a firmware
> > update in iBridge since macOS Sonoma.
> I'm slightly puzzled why this was sent to the IOMMU maintainers when it
> doesn't touch any IOMMU code, nor even contain any reference to the IOMMU
> API at all...
People like to put a random people to a random contributions :-)
Aditya, you can utilise my "smart" script [1] to send the series
to more-or-less relevant people (but definitely to the right ones
± potentially interested, it has a heuristics inside).
[1]: https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-10 13:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 8:40 [PATCH RFC] staging: Add driver to communicate with the T2 Security Chip Aditya Garg
2025-03-09 8:44 ` Aditya Garg
2025-03-09 8:49 ` gregkh
2025-03-09 9:00 ` Aditya Garg
2025-03-09 9:13 ` gregkh
2025-03-09 8:52 ` gregkh
2025-03-09 8:54 ` gregkh
2025-03-09 9:05 ` Aditya Garg
2025-03-09 9:15 ` gregkh
2025-03-09 9:03 ` Aditya Garg
2025-03-09 9:14 ` gregkh
2025-03-09 9:28 ` Aditya Garg
2025-03-09 9:37 ` gregkh
2025-03-09 9:41 ` Aditya Garg
2025-03-09 9:48 ` gregkh
2025-03-09 9:52 ` Aditya Garg
2025-03-09 9:55 ` gregkh
2025-03-09 10:12 ` Aditya Garg
2025-03-09 10:22 ` gregkh
2025-03-09 10:33 ` Aditya Garg
2025-03-10 8:14 ` Dan Carpenter
2025-03-10 8:45 ` Aditya Garg
2025-03-10 13:49 ` Robin Murphy
2025-03-10 13:54 ` andriy.shevchenko [this message]
2025-03-10 13:59 ` Aditya Garg
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=Z87vKltfijzRtlpL@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=admin@kodeit.net \
--cc=bhelgaas@google.com \
--cc=gargaditya08@live.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=orlandoch.dev@gmail.com \
--cc=paul@mrarm.io \
--cc=robin.murphy@arm.com \
--cc=will@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