[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4784b95f-0023-5250-ba9e-23b70b66611c@suse.com>
Date: Wed, 25 Mar 2020 09:10:24 +0100
From: Jiri Slaby <jslaby@...e.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Arnaud Pouliquen <arnaud.pouliquen@...com>,
Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-remoteproc@...r.kernel.org,
Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Suman Anna <s-anna@...com>,
Fabien DESSENNE <fabien.dessenne@...com>,
linux-stm32@...md-mailman.stormreply.com,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
xiang xiao <xiaoxiang781216@...il.com>
Subject: Re: [PATCH v7 2/2] tty: add rpmsg driver
Hi,
On 24. 03. 20, 18:44, Randy Dunlap wrote:
>> + could be lost.
>> +- It can pause/resume reception by sending a control message (rely on CTS state).
>> +
>> +Control message structure:
>> +struct rpmsg_tty_ctrl {
>> + u8 cts; /* remote reception status */
>> + u16 d_ept_addr; /* data endpoint address */
>> +};
>
> Is that struct packed or padded?
As it seems, this documentation is in contradiction with code, anyway:
+struct rpmsg_tty_ctrl {
+ u16 d_ept_addr; /* data endpoint address */
+ u8 cts; /* remote reception status */
+} __packed;
thanks,
--
js
suse labs
Powered by blists - more mailing lists