From: Aditya Garg <gargaditya08@live.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"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: Sun, 9 Mar 2025 09:00:07 +0000 [thread overview]
Message-ID: <PN3PR01MB9597AEE275F867871BD9A5DFB8D72@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <2025030939-moonrise-zipfile-97cf@gregkh>
> On 9 Mar 2025, at 2:21 PM, gregkh@linuxfoundation.org wrote:
>
> On Sun, Mar 09, 2025 at 08:44:16AM +0000, Aditya Garg wrote:
>>
>>
>>>> On 9 Mar 2025, at 2:10 PM, Aditya Garg <gargaditya08@live.com> 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>
>>>
>>
>> FWIW, I am aware of the missing maintainers file and still not removed Linux version checks in the driver.
>>
>> My main purpose of sending this was to know the views of the maintainers about the code quality, and whether this qualifies for staging or not.
>
> I have to ask why do you want this in drivers/staging/ at all? Why not
> take the day or so to clean up the code to be the proper style and
> handle the needed issues and then submit it to the normal part of the
> kernel?
>
> Putting code in staging actually takes more work to clean it up and get
> it out of there than just doing it all at once out-of-tree. So we need
> a good reason why it is in here, as well as what the plan is to get it
> out of staging entirely. So a TODO file in the directory for the driver
> is required here.
I see. I was of the view that staging is more of like a place to keep beta drivers
>
> Also, as this is at least 3 different drivers, this should be a patch
> series and not all in one if at all possible.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2025-03-09 9:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 8:40 Aditya Garg
2025-03-09 8:44 ` Aditya Garg
2025-03-09 8:49 ` gregkh
2025-03-09 9:00 ` Aditya Garg [this message]
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
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=PN3PR01MB9597AEE275F867871BD9A5DFB8D72@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM \
--to=gargaditya08@live.com \
--cc=admin@kodeit.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.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
all inboxes | Powered by JetHome®