All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Manjunatha Venkatesh <manjunatha.venkatesh@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"will@kernel.org" <will@kernel.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"mb@lightnvm.io" <mb@lightnvm.io>,
	"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
	"arnd@arndb.d" <arnd@arndb.d>, "mst@redhat.com" <mst@redhat.com>,
	"javier@javigon.com" <javier@javigon.com>,
	"mikelley@microsoft.com" <mikelley@microsoft.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"sunilmut@microsoft.com" <sunilmut@microsoft.com>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"rvmanjumce@gmail.com" <rvmanjumce@gmail.com>
Subject: Re: [EXT] Re: [PATCH] Uwb: Nxp: sr1xx: Uwb driver support for sr1xx series chip
Date: Tue, 15 Mar 2022 13:31:50 +0100	[thread overview]
Message-ID: <YjCHNlC2Xc1QoTzQ@kroah.com> (raw)
In-Reply-To: <d0343411-f95f-e550-da69-2fdb15106312@nxp.com>

On Tue, Mar 15, 2022 at 10:43:47AM +0000, Manjunatha Venkatesh wrote:
> >> +     sr1xx_dev = filp->private_data;
> >> +     switch (cmd) {
> >> +     case SR1XX_SET_PWR:
> > You have custom ioctls on a device node, that's not very "subsystem"
> > like at all.
> >
> > You need to define a standard user/kernel api for this subsystem, do not
> > make it "whatever the device wants" like this currently is.
> >
> > And where is the userspace code that talks this brand new api?  We need
> > to see that so we can properly determine if this is all working
> > properly.
> Currently these ioctl calls used for handling proprietary operation with 
> respect to SR1xx chip.
> corresponding user space UWB code is proprietary and might be shortly 
> will be available as part of AOSP release, till that time not sure can 
> share user space code outside or not.
> Still if you think need the user space code required to evaluate driver 
> part will check internally and come back on this.

For obvious reasons, we can not take kernel drivers that add a custom
user/kernel api without any userspace code that we can see to use it.
You wouldn't want us to take such code anyway.

So please, fix that, otherwise this is not going to go very far at all.

thanks,

greg k-h

  reply	other threads:[~2022-03-15 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 12:37 [PATCH] Uwb: Nxp: sr1xx: Uwb driver support for sr1xx series chip Manjunatha Venkatesh
2022-03-07 13:16 ` Greg KH
2022-03-15 10:43   ` [EXT] " Manjunatha Venkatesh
2022-03-15 12:31     ` Greg KH [this message]
2022-04-27  6:24       ` Manjunatha Venkatesh
2022-04-27  6:37         ` Greg KH

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=YjCHNlC2Xc1QoTzQ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.d \
    --cc=axboe@kernel.dk \
    --cc=bjorn.andersson@linaro.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=jasowang@redhat.com \
    --cc=javier@javigon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manjunatha.venkatesh@nxp.com \
    --cc=mb@lightnvm.io \
    --cc=mikelley@microsoft.com \
    --cc=mst@redhat.com \
    --cc=rvmanjumce@gmail.com \
    --cc=sunilmut@microsoft.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 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.