From: Vinod <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Suman Anna <s-anna@ti.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] samples/rpmsg: Introduce a module parameter for message count
Date: Sat, 6 Oct 2018 21:58:18 +0530 [thread overview]
Message-ID: <20181006162818.GQ2372@vkoul-mobl> (raw)
In-Reply-To: <20181006062231.GF12063@builder>
On 05-10-18, 23:22, Bjorn Andersson wrote:
> On Tue 11 Sep 10:46 PDT 2018, Suman Anna wrote:
>
> > The current rpmsg_client_sample uses a fixed number of messages to
> > be sent to each instance. This is currently set at 100. Introduce
> > an optional module parameter 'count' so that the number of messages
> > to be exchanged can be made flexible.
> >
>
> Rather than sending N messages as fast as possible to any sample channel
> that comes up, how about making the sample create a debugfs entry that
> we can write messages to from user space?
Wouldn't it be better to make it sysfs rather than debugfs knob?
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vkoul@kernel.org (Vinod)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] samples/rpmsg: Introduce a module parameter for message count
Date: Sat, 6 Oct 2018 21:58:18 +0530 [thread overview]
Message-ID: <20181006162818.GQ2372@vkoul-mobl> (raw)
In-Reply-To: <20181006062231.GF12063@builder>
On 05-10-18, 23:22, Bjorn Andersson wrote:
> On Tue 11 Sep 10:46 PDT 2018, Suman Anna wrote:
>
> > The current rpmsg_client_sample uses a fixed number of messages to
> > be sent to each instance. This is currently set at 100. Introduce
> > an optional module parameter 'count' so that the number of messages
> > to be exchanged can be made flexible.
> >
>
> Rather than sending N messages as fast as possible to any sample channel
> that comes up, how about making the sample create a debugfs entry that
> we can write messages to from user space?
Wouldn't it be better to make it sysfs rather than debugfs knob?
--
~Vinod
next prev parent reply other threads:[~2018-10-06 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:46 [PATCH] samples/rpmsg: Introduce a module parameter for message count Suman Anna
2018-09-11 17:46 ` Suman Anna
2018-09-11 17:46 ` Suman Anna
2018-09-11 18:17 ` Trilok Soni
2018-09-11 18:17 ` Trilok Soni
2018-10-01 21:09 ` Suman Anna
2018-10-01 21:09 ` Suman Anna
2018-10-01 21:09 ` Suman Anna
2018-10-06 6:22 ` Bjorn Andersson
2018-10-06 6:22 ` Bjorn Andersson
2018-10-06 6:22 ` Bjorn Andersson
2018-10-06 16:28 ` Vinod [this message]
2018-10-06 16:28 ` Vinod
2018-10-08 16:33 ` Suman Anna
2018-10-08 16:33 ` Suman Anna
2018-10-08 16:33 ` Suman Anna
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=20181006162818.GQ2372@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=s-anna@ti.com \
/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.