Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1952380pxb; Fri, 5 Feb 2021 05:47:18 -0800 (PST) X-Google-Smtp-Source: ABdhPJzAxYB0cTavHJiSS5ivXBK/Cp2VKxqfD3Zlh5Ui1ZdD91R+izY4oFOkhX3RLmzz77Jn9TCt X-Received: by 2002:aa7:c884:: with SMTP id p4mr3635974eds.212.1612532838706; Fri, 05 Feb 2021 05:47:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612532838; cv=none; d=google.com; s=arc-20160816; b=y02Vz1rvnjE4fy1G6pRZF6mpJYNUCeCC3xevUUikgZQycd/+R1BMxYFZU6if48d2IU 3vo76UfrfWJhsEqUSQBX0ZYtqOpaCPWNwJjyUNyc6J0toLwNFLQoxLJwb3WsQpqMg1gQ 1Mssh0slhs8Doyq12dIFIeEB+8/tHjDEWjIej9byV+ms7Qk6Z+PA4J5qHfvpBfAvaR7n o3/tcFA96K2Fg/ZBrRfK5k2++QDtXZZnecDanxUJCW7D7Fxg8Oi/Dr/UN/K+ind6LqxJ ceutjtRzIAu9qizNq6ALeiIKbxGmd06ie4szdVLYrkx3HRmJkOkak/qsJ08uf71txS6a aOTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=UKdiQG0KUB4wVn9CbTH34ecV+cDgDPIAXkh3NbFuAU4=; b=QSJ1Nh4am9iMTmtrv4PAPNOrlviffYggMCyIlP5PgLTpxtCc26x2d+sEoHBYc7SDgO +ZtnFlNtqh6pAAJFwHvS+iw3GV7mM1wKbMdj21/9A1yaB0LnFTiUJ6n5+vlYeIKwYLzD U1xivja9++24FYXvH14vq6+mVJIpv0P4Q7l36+cL1f15kNpiZ9zzzamg9sq6ktYwQ4v6 d9CC/1vm2bqq/x1unsqgpWhZJFKxfhS0ukhIx3fRo08HcGNFem6XU+ZWb+vVEQhkhW7L mA5CtuEUhpcYzvdUNHDELcNyvJMIkx5xWPLt5lGc6oA9ZcyAK9FAvAWRX+QnHyoJUuCI mFFw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cc22si5745661edb.80.2021.02.05.05.46.53; Fri, 05 Feb 2021 05:47:18 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231330AbhBENpX (ORCPT + 99 others); Fri, 5 Feb 2021 08:45:23 -0500 Received: from mx2.suse.de ([195.135.220.15]:47362 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231261AbhBENnF (ORCPT ); Fri, 5 Feb 2021 08:43:05 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BCC0CACAC; Fri, 5 Feb 2021 13:42:23 +0000 (UTC) Date: Fri, 05 Feb 2021 14:42:23 +0100 Message-ID: From: Takashi Iwai To: Andrew Lunn Cc: Hans Verkuil , Mauro Carvalho Chehab , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, "Matwey V. Kornilov" , Robert Foss Subject: Re: [PATCH] media: pwc: Fix the URB buffer allocation In-Reply-To: References: <20210121202855.17400-1-tiwai@suse.de> <7afd0612-de36-60b1-6650-6f8de24a7145@xs4all.nl> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 05 Feb 2021 14:13:02 +0100, Andrew Lunn wrote: > > Hi Takashi > > > Indeed, looks so. In most cases, this doesn't matter since both point > > to the same device object. In some cases like xhci-plat HCD, they > > differ. And sysdev might be a better choice from the consistency > > POV. > > > > But this brought an interesting question, too. eg. USB chipidea > > HCD uses platform devices for both controller and sysdev, and I > > couldn't find any DMA mask setup. So, no matter what to use, the uwc > > driver would be broken on this... Maybe it's just not covered. > > Did you do a git bisect to see what actually broke it? "1161db6776bd: > media: usb: pwc: Don't use coherent DMA buffers for ISO transfer" > introduced the code, not the regression. If we understand the > regression, that might give us the answer about chipidea. It's the recent DMA core change, the commit f959dcd6ddfd ("dma-direct: Fix potential NULL pointer dereference"). But basically it's a right fix, and the driver hitting this "regression" has been already broken but casually worked without setting a proper DMA mask. Takashi