All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: 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>,
	"andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>
Cc: "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 13:49:13 +0000	[thread overview]
Message-ID: <ef8dcf7a-34ed-4b27-a154-e01bc167d4e6@arm.com> (raw)
In-Reply-To: <1A12CB39-B4FD-4859-9CD7-115314D97C75@live.com>

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.
> 
> Signed-off-by: Paul Pawlowski <paul@mrarm.io>
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
> ---
> drivers/staging/Kconfig                       |   2 +
> drivers/staging/Makefile                      |   1 +
> drivers/staging/apple-bce/Kconfig             |  18 +
> drivers/staging/apple-bce/Makefile            |  28 +
> drivers/staging/apple-bce/apple_bce.c         | 448 ++++++++++
> drivers/staging/apple-bce/apple_bce.h         |  44 +
> drivers/staging/apple-bce/audio/audio.c       | 714 ++++++++++++++++
> drivers/staging/apple-bce/audio/audio.h       | 128 +++
> drivers/staging/apple-bce/audio/description.h |  45 ++
> drivers/staging/apple-bce/audio/pcm.c         | 311 +++++++
> drivers/staging/apple-bce/audio/pcm.h         |  19 +
> drivers/staging/apple-bce/audio/protocol.c    | 350 ++++++++
> drivers/staging/apple-bce/audio/protocol.h    | 148 ++++
> .../staging/apple-bce/audio/protocol_bce.c    | 229 ++++++
> .../staging/apple-bce/audio/protocol_bce.h    |  75 ++
> drivers/staging/apple-bce/mailbox.c           | 154 ++++
> drivers/staging/apple-bce/mailbox.h           |  56 ++
> drivers/staging/apple-bce/queue.c             | 393 +++++++++
> drivers/staging/apple-bce/queue.h             | 180 +++++
> drivers/staging/apple-bce/queue_dma.c         | 223 +++++
> drivers/staging/apple-bce/queue_dma.h         |  53 ++
> drivers/staging/apple-bce/vhci/command.h      | 207 +++++
> drivers/staging/apple-bce/vhci/queue.c        | 271 +++++++
> drivers/staging/apple-bce/vhci/queue.h        |  79 ++
> drivers/staging/apple-bce/vhci/transfer.c     | 664 +++++++++++++++
> drivers/staging/apple-bce/vhci/transfer.h     |  76 ++
> drivers/staging/apple-bce/vhci/vhci.c         | 764 ++++++++++++++++++
> drivers/staging/apple-bce/vhci/vhci.h         |  55 ++
> 28 files changed, 5735 insertions(+)

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...

Since I don't know enough about audio or USB code, all I can really say 
here is to echo Greg's comment that, judging by that diffstat alone, 
this probably wants to be at least 3-5 separate patches, adding each 
functional piece in manageable chunks.

Thanks,
Robin.

  parent reply	other threads:[~2025-03-10 13:49 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 [this message]
2025-03-10 13:54   ` andriy.shevchenko
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=ef8dcf7a-34ed-4b27-a154-e01bc167d4e6@arm.com \
    --to=robin.murphy@arm.com \
    --cc=admin@kodeit.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --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=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 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.