From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Jonathan Marek <jonathan@marek.ca>, linux-arm-msm@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc: fastrpc: add ioctl for attaching to sensors pd
Date: Mon, 7 Sep 2020 15:01:18 +0100 [thread overview]
Message-ID: <f2faa7b2-1e7d-2f39-ef36-a3790cedfab9@linaro.org> (raw)
In-Reply-To: <3f1f8ff1-cf23-ae2c-4cff-cdcce0b11e2e@marek.ca>
On 07/09/2020 14:47, Jonathan Marek wrote:
> On 9/7/20 8:36 AM, Srinivas Kandagatla wrote:
>>
>>
>> On 01/09/2020 01:32, Jonathan Marek wrote:
>>> -#define FASTRPC_IOCTL_MMAP _IOWR('R', 6, struct
>>> fastrpc_req_mmap)
>>> -#define FASTRPC_IOCTL_MUNMAP _IOWR('R', 7, struct
>>> fastrpc_req_munmap)
>>> +#define FASTRPC_IOCTL_MMAP _IOWR('R', 6, struct
>>> fastrpc_req_mmap)
>>> +#define FASTRPC_IOCTL_MUNMAP _IOWR('R', 7, struct
>>> fastrpc_req_munmap)
>>
>> Looks like changes that do not belong to this patch!
>>
>> I wanted to try this patch on SM8250.
>> How do you test attaching fastrpc to sensor core?, I mean which
>> userspace lib/tool do you use?
>>
>> --srini
>>
>
> I pushed my sdsprpcd implementation to github, which is responsible for
> initializing the sensors, and uses this ioctl:
>
> https://github.com/flto/fastrpc
Thanks!, I can take a look and see if I can try it out with linaro
fastrpc library!
>
> Note: it uses my own WIP fastrpc "library" instead of the one from
> linaro, I also have other related code, like a sensor client, and
> cDSP/aDSP compute examples, but need to confirm that I can share them
>
> Also, the corresponding dts patch I sent has a problem, the label =
> "dsps"; should be label = "sdsp"; (copied the "dsps" from downstream,
> but upstream expects "sdsp"), will send a v2 later today.
Also the dts patch will fail to apply as it is, as it seems me that you
have based the patch after adding audio dts patch!
--srini
>
>>> +#define FASTRPC_IOCTL_INIT_ATTACH_SNS _IO('R', 8)
next prev parent reply other threads:[~2020-09-07 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 0:32 Jonathan Marek
2020-09-07 12:33 ` Greg Kroah-Hartman
2020-09-07 13:51 ` Jonathan Marek
2020-09-07 13:58 ` Srinivas Kandagatla
2020-09-07 14:02 ` Jonathan Marek
2020-09-08 8:19 ` Srinivas Kandagatla
2020-09-07 12:36 ` Srinivas Kandagatla
2020-09-07 13:47 ` Jonathan Marek
2020-09-07 14:01 ` Srinivas Kandagatla [this message]
2020-09-07 14:05 ` Jonathan Marek
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=f2faa7b2-1e7d-2f39-ef36-a3790cedfab9@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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®