LKML Archive on
help / color / mirror / Atom feed
From: Stephen Boyd <>
To: Bjorn Andersson <>,
	Ohad Ben-Cohen <>,
	Srinivas Kandagatla <>
Subject: Re: [PATCH] Revert "rpmsg: smd: Create device for all channels"
Date: Thu, 15 Mar 2018 11:50:01 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Quoting Bjorn Andersson (2018-03-15 11:12:44)
> In an effort to pick up channels that are in a funky state we
> optimistically tried to open all channels that we found, with the
> addition that we failed if the other side did not handshake the opening.
> But as we're starting the modem a second time all channels are found -
> in a "funky" state - and we try to open them. But the modem firmware
> requires the IPCRTR to be up in order to initialize. So any channels we
> try to open before that will fail and will not be opened again.
> This takes care of the regression, at the cost of reintroducing the
> previous behavior of handling of channels with "funky" states.

Is it a funky chicken and egg problem between IPCRTR and smd?

      reply	other threads:[~2018-03-15 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 18:12 [PATCH] Revert "rpmsg: smd: Create device for all channels" Bjorn Andersson
2018-03-15 18:50 ` Stephen Boyd [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).