[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171127055606.GR3187@localhost>
Date: Mon, 27 Nov 2017 11:26:06 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: gregkh@...uxfoundation.org, broonie@...nel.org,
alsa-devel@...a-project.org, sdharia@...eaurora.org, bp@...e.de,
poeschel@...onage.de, treding@...dia.com, andreas.noever@...il.com,
alan@...ux.intel.com, mathieu.poirier@...aro.org, daniel@...ll.ch,
jkosina@...e.cz, sharon.dvir1@...l.huji.ac.il, joe@...ches.com,
davem@...emloft.net, james.hogan@...tec.com,
michael.opdenacker@...e-electrons.com, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, arnd@...db.de
Subject: Re: [PATCH v7 06/13] slimbus: Add messaging APIs to slimbus framework
On Mon, Nov 20, 2017 at 06:47:52AM +0000, Srinivas Kandagatla wrote:
> >>+ * -ENOTCONN: If the transmitted message was not ACKed by destination
> >>+ * device.
> >
> >I am preferring ENODATA in SDW for this case, as Slaves didnt respond or
> >ACK.
> Isn't that a timeout error then.
>
> ENODATA is for "No data available", reporting ENODATA would be misleading.
Do you get a explict NACK or no response for this
>
> >
> >ENOTCONN is defined as /* Transport endpoint is not connected */ which is
> >not the case here, connected yes but not responded.
>
> Code as it is would not return this, so i will be deleting ENOTCONN from
> kernel doc.
ok
--
~Vinod
Powered by blists - more mailing lists