From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751732AbdK1HS3 (ORCPT ); Tue, 28 Nov 2017 02:18:29 -0500 Received: from mail-wm0-f52.google.com ([74.125.82.52]:47010 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbdK1HSZ (ORCPT ); Tue, 28 Nov 2017 02:18:25 -0500 X-Google-Smtp-Source: AGs4zMaEq6oF9PSkdieyxwWWx1p9gLl8xh3GDR3Et0qb/ZultkRddBaDXskHjpUIcgAw5+FxQeZC6g== Subject: Re: [PATCH v7 06/13] slimbus: Add messaging APIs to slimbus framework To: Vinod Koul Cc: gregkh@linuxfoundation.org, broonie@kernel.org, alsa-devel@alsa-project.org, sdharia@codeaurora.org, bp@suse.de, poeschel@lemonage.de, treding@nvidia.com, andreas.noever@gmail.com, alan@linux.intel.com, mathieu.poirier@linaro.org, daniel@ffwll.ch, jkosina@suse.cz, sharon.dvir1@mail.huji.ac.il, joe@perches.com, davem@davemloft.net, james.hogan@imgtec.com, michael.opdenacker@free-electrons.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, arnd@arndb.de References: <20171115141043.29202-1-srinivas.kandagatla@linaro.org> <20171115141043.29202-7-srinivas.kandagatla@linaro.org> <20171117074834.GM3187@localhost> <20171127055606.GR3187@localhost> From: Srinivas Kandagatla Message-ID: Date: Tue, 28 Nov 2017 07:18:22 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171127055606.GR3187@localhost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27/11/17 05:56, Vinod Koul wrote: > 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 There is no response for the request, currently code waits for it arrive and then timesout on completion.