From: Takashi Iwai <tiwai@suse.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matwey V. Kornilov" <matwey@sai.msu.ru>,
Robert Foss <robert.foss@linaro.org>
Subject: Re: [PATCH] media: pwc: Fix the URB buffer allocation
Date: Fri, 05 Feb 2021 14:42:23 +0100 [thread overview]
Message-ID: <s5hy2g23a2o.wl-tiwai@suse.de> (raw)
In-Reply-To: <YB1EXirrstMlg/vA@lunn.ch>
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
next prev parent reply other threads:[~2021-02-05 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 20:28 [PATCH] media: pwc: Fix the URB buffer allocation Takashi Iwai
2021-01-22 8:57 ` Robert Foss
2021-02-05 12:36 ` Hans Verkuil
2021-02-05 12:53 ` Andrew Lunn
2021-02-05 13:03 ` Takashi Iwai
2021-02-05 13:13 ` Andrew Lunn
2021-02-05 13:42 ` Takashi Iwai [this message]
2021-02-05 13:53 ` Andrew Lunn
2021-02-05 14:05 ` Hans Verkuil
2021-02-05 14:19 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hy2g23a2o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=andrew@lunn.ch \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--cc=mchehab@kernel.org \
--cc=robert.foss@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox