From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73B03C04E87 for ; Tue, 21 May 2019 15:34:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 494FE2173C for ; Tue, 21 May 2019 15:34:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="rbdO73qS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728726AbfEUPeQ (ORCPT ); Tue, 21 May 2019 11:34:16 -0400 Received: from mail-wr1-f52.google.com ([209.85.221.52]:41930 "EHLO mail-wr1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727534AbfEUPeQ (ORCPT ); Tue, 21 May 2019 11:34:16 -0400 Received: by mail-wr1-f52.google.com with SMTP id g12so18855880wro.8 for ; Tue, 21 May 2019 08:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bqLYld3VX/KZYenyewBwijFGLXmDZ4ZcB2Pc2sDMB8o=; b=rbdO73qSK67ppmSog10HPSh8JWD2iexbOqLqx4e1x6h4qKRmTBM4+j/hqHfdA7n7ef 9ejSwP1LWI3C53xS9kXBmxqz62EALFyhdwd4DhzroVJC/UW5EF+XISqs0Bv9eyJcdORl UKkyPNqRpMkY8zwKZ6JI85UQsI4awnVuFixu45X5Yej9Du8lCYak4YciKwH/V2lJHLcj 4j6fzIs3Mw5fIGsVHpgpzc5HAsyxDcfzq7E65s7oxZrR+vmsBmp8CosszSvUIG+LlRm1 3ZsWAh6KLxL+ZvjuXVPjDyfXitiRL3zo4yv/PfR8LBTeAUYQzVKyfXKUtdiQ1Zu5fLbf 1iyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bqLYld3VX/KZYenyewBwijFGLXmDZ4ZcB2Pc2sDMB8o=; b=nycmcnzFcGGAA7dIx4ymGBeHk9MwGg3E2+OjqiGkZyUH7nGR47twcNma6vLatOEpHH /YzaM8CV6zURMzRPu9VfB0adMI23/xtZ067Bnl0mDJmcfcJ3/ycpfcK9mEuE/RGnPFqI +BdQhFgGspNEUQdqG7+tRazXPwj3lj+IYVDpzToOApV0kZ0Yfo7Sv4p9wVViBkpOqSWn ActOlk8NO6iYKGQ/J+H5V94uyyJ9Yh+tBrsywl9ARpQEKPKNHvThc4Z0UXF/ewdu1OGj ESOMemk0g2eJqmmNNwFcxd4pjsouYJLgYUvYT0vmRLlXk8vEcQFldoWNfZ4AVxMgNFVo DLJA== X-Gm-Message-State: APjAAAUjg/1wSzw+MwVyRU7AsnlcMNqlER2IayF0ONY71WdD2KJMrXEF IsLEF/Py5mps/v9mPKveDpCoUMZNHbj2DIAFD4Lfow== X-Google-Smtp-Source: APXvYqyBLXULB9X5PD+iPwuBEjdqQQwlx6IsrRh80MfxPXTrYxfxqqW+idUM28iKqva9wskFgLsjCqyphLZjvkLGhRQ= X-Received: by 2002:adf:978b:: with SMTP id s11mr26223969wrb.169.1558452854441; Tue, 21 May 2019 08:34:14 -0700 (PDT) MIME-Version: 1.0 References: <7caebeb2-ea96-2276-3078-1e53f09ce227@collabora.com> <7ec57c29-d1ab-dc4c-755d-a6009b9132b5@collabora.com> <36620156-d119-b1b2-989e-0c13b783296e@collabora.com> <02E7334B1630744CBDC55DA8586225837F884D53@ORSMSX103.amr.corp.intel.com> <02E7334B1630744CBDC55DA8586225837F885FFD@ORSMSX103.amr.corp.intel.com> <1672b93a-dfe6-acb2-715e-c4a13af54413@collabora.com> In-Reply-To: <1672b93a-dfe6-acb2-715e-c4a13af54413@collabora.com> From: John Stultz Date: Tue, 21 May 2019 08:34:02 -0700 Message-ID: Subject: Re: [REGRESSION] usb: gadget: f_fs: Allow scatter-gather buffers To: Andrzej Pietrasiewicz Cc: "Yang, Fei" , Felipe Balbi , Bjorn Andersson , Chen Yu , lkml , Linux USB List , Amit Pundir , Marek Szyprowski , "kernel@collabora.com" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 21, 2019 at 3:04 AM Andrzej Pietrasiewicz wrote: > > One thing that becomes evident now is that adb uses async io. > It seems that interaction of async io and s-g mode should be further > investigated. Although on our devices, we have async io disabled w/ adb, as there is an existing/separate issue w/ the dwc3 driver in 4.19 and older kernels. So it seems its not strictly connected to async io. thanks -john