On Fri 26 Jan 17:01 PST 2018, Jeremy McNicoll wrote: > On Tue, Dec 12, 2017 at 03:58:54PM -0800, Bjorn Andersson wrote: [..] > > > > The result of this patch is that we will actively open the RPM channel > > even though it's left in a state other than "opening" after the boot > > loader's closing of the channel. > > > > Its been a while since I looked at this closely but, isn't the result > of this patch that we now will create a channel / register a platform > device if the state of the channel is left in any state. > Correct, we will create devices for all channels found (on the specific edge), rather than just the ones that are in opening state. Looking through a few platforms does however indicate that the two cases where channels appear but are not in this state are: 1) The rpm_request channel when LK has been communicating with the RPM before jumping to the kernel. 2) You stop a remote processor, switch firmware to one with less features and the start it again. Any channels not used by the new firmware will still be found and we will fail to open them - as described above. I would be surprised if this would happen in reality. So with the added handshake mechanism we're supporting #1 and we deal with #2 - if it ever would happen. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
