From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>
Cc: Arjun Gopalan <agopalan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Brian Swetland <swetland-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: permission to move definition of struct rpmsg_channel_info
Date: Tue, 10 Sep 2013 19:00:51 +0200 [thread overview]
Message-ID: <20130910170051.GB22111@ulmo> (raw)
In-Reply-To: <CAK=Wgbbxp5pfQm1mvCZ2phigXe_e2_J_Zkrof9tx2jggi8EMjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Mon, Sep 09, 2013 at 10:06:24PM +0200, Ohad Ben-Cohen wrote:
> On Mon, Sep 9, 2013 at 2:57 PM, Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
[...]
> > Looking at the remoteproc core, it seems that there's no direct way to
> > change the firmware running on a remoteproc at runtime.
>
> One way is to unload and load the driver, but you can also use the
> bind/unbind sysfs files of your driver (echo -n device-name >
> /sys/..../{un}bind).
I'm not quite sure how that solves the issue with replacing the firmware
image. The driver will still request the same firmware on rebind, so the
only way to have a different firmware loaded would be to replace the
file. That sounds sub-optimal. But it's not very important at this stage
so it can be deferred until (and if) it becomes a real issue.
> Does that help?
Yes, thanks very much for confirming.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Arjun Gopalan <agopalan@nvidia.com>,
Brian Swetland <swetland@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Paul Walmsley <pwalmsley@nvidia.com>
Subject: Re: permission to move definition of struct rpmsg_channel_info
Date: Tue, 10 Sep 2013 19:00:51 +0200 [thread overview]
Message-ID: <20130910170051.GB22111@ulmo> (raw)
In-Reply-To: <CAK=Wgbbxp5pfQm1mvCZ2phigXe_e2_J_Zkrof9tx2jggi8EMjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Mon, Sep 09, 2013 at 10:06:24PM +0200, Ohad Ben-Cohen wrote:
> On Mon, Sep 9, 2013 at 2:57 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
[...]
> > Looking at the remoteproc core, it seems that there's no direct way to
> > change the firmware running on a remoteproc at runtime.
>
> One way is to unload and load the driver, but you can also use the
> bind/unbind sysfs files of your driver (echo -n device-name >
> /sys/..../{un}bind).
I'm not quite sure how that solves the issue with replacing the firmware
image. The driver will still request the same firmware on rebind, so the
only way to have a different firmware loaded would be to replace the
file. That sounds sub-optimal. But it's not very important at this stage
so it can be deferred until (and if) it becomes a real issue.
> Does that help?
Yes, thanks very much for confirming.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-10 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 19:20 permission to move definition of struct rpmsg_channel_info Arjun Gopalan
2013-08-30 19:20 ` Arjun Gopalan
2013-09-08 12:27 ` Ohad Ben-Cohen
[not found] ` <CAK=WgbZ2JgtAonvdyeDZazYBGdKpPAieJtjzi7MM6nwqhVfs7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-09 12:57 ` Thierry Reding
2013-09-09 12:57 ` Thierry Reding
2013-09-09 20:06 ` Ohad Ben-Cohen
2013-09-09 20:06 ` Ohad Ben-Cohen
[not found] ` <CAK=Wgbbxp5pfQm1mvCZ2phigXe_e2_J_Zkrof9tx2jggi8EMjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-10 17:00 ` Thierry Reding [this message]
2013-09-10 17:00 ` Thierry Reding
2013-09-10 19:18 ` Arjun Gopalan
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=20130910170051.GB22111@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=agopalan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
--cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swetland-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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.