From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 1/3] staging: zynpu: Add driver support for ARM(China) ZHOUYI AI accelerator
Date: Wed, 24 Nov 2021 09:52:50 +0100 [thread overview]
Message-ID: <YZ39YqsNTSolEJZ2@kroah.com> (raw)
In-Reply-To: <20211124084620.628-2-caihuoqing@baidu.com>
On Wed, Nov 24, 2021 at 04:46:15PM +0800, Cai Huoqing wrote:
> ZHOUYI NPU is an AI accelerator chip which is integrated into ARM SOC,
> such as Allwinner R329 SOC.
> Add driver support for this AI accelerator here.
>
> This driver is not tandard linux style, there are some clean up works,
"standard"?
> fixing code style, refactorring.
> And it only works with a closed source usermode driver, so need to
> reverse the libraries, and impelement it, then open source
> the usermode driver.
Who will be doing the "reversing" of the usermode driver?
We can't take this now if there's no actual users of this code that
anyone can test. Why not just change the license of the usermode code
now to make this simpler?
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-24 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 8:46 [PATCH v2 0/3] staging: zynpu: Add driver support for ARM(China) ZHOUYI AI accelerator Cai Huoqing
2021-11-24 8:46 ` [PATCH v2 1/3] " Cai Huoqing
2021-11-24 8:52 ` Greg Kroah-Hartman [this message]
2021-11-24 9:09 ` Cai Huoqing
2021-11-24 12:25 ` Cai Huoqing
2021-11-26 21:36 ` kernel test robot
2021-11-27 0:34 ` kernel test robot
2021-11-27 1:04 ` kernel test robot
2021-11-24 8:46 ` [PATCH v2 2/3] dt-bindings: staging: Add the binding documentation for " Cai Huoqing
2021-11-25 21:26 ` Rob Herring
2021-11-24 8:46 ` [PATCH v2 3/3] MAINTAINERS: Add the driver info of the " Cai Huoqing
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=YZ39YqsNTSolEJZ2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=caihuoqing@baidu.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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).