From: Takashi Iwai <tiwai@suse.de>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: hamohammed.sa@gmail.com, alsa-devel@alsa-project.org,
k.kozlowski@samsung.com, Shuah Khan <shuahkh@osg.samsung.com>,
a.hajda@samsung.com, prabhakar.csengg@gmail.com,
laurent.pinchart@ideasonboard.com, s.nawrocki@samsung.com,
devel@driverdev.osuosl.org, crope@iki.fi,
lixiubo@cmss.chinamobile.com, linux-samsung-soc@vger.kernel.org,
chehabrafael@gmail.com, javier@osg.samsung.com, kgene@kernel.org,
der.herr@hofr.at, soren.brinkmann@xilinx.com,
hans.verkuil@cisco.com, navyasri.tech@gmail.com,
dan.carpenter@oracle.com, linux-media@vger.kernel.org,
tommi.franttila@intel.com, Julia.Lawall@lip6.fr, perex@perex.cz,
linux-arm-kernel@lists.infradead.org, hyun.kwon@xilinx.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, kyungmin.park@samsung.com,
Sakari Ailus <sakari.ailus@iki.fi>,
g.liakhovetski@gmx.de
Subject: Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context
Date: Mon, 14 Mar 2016 11:33:25 +0100 [thread overview]
Message-ID: <s5hmvq14adm.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160314071358.27c87dab@recife.lan>
On Mon, 14 Mar 2016 11:13:58 +0100,
Mauro Carvalho Chehab wrote:
>
> Em Mon, 14 Mar 2016 09:22:37 +0200
> Sakari Ailus <sakari.ailus@iki.fi> escreveu:
>
> > Hi Shuah,
> >
> > On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote:
> > > Add GFP flags to media_create_pad_link(), media_create_intf_link(),
> > > media_devnode_create(), and media_add_link() that could get called
> > > in atomic context to allow callers to pass in the right flags for
> > > memory allocation.
> > >
> > > tree-wide driver changes for media_*() GFP flags change:
> > > Change drivers to add gfpflags to interffaces, media_create_pad_link(),
> > > media_create_intf_link() and media_devnode_create().
> > >
> > > Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> > > Suggested-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> >
> > What's the use case for calling the above functions in an atomic context?
> >
>
> ALSA code seems to do a lot of stuff at atomic context. That's what
> happens on my test machine when au0828 gets probed before
> snd-usb-audio:
> http://pastebin.com/LEX5LD5K
>
> It seems that ALSA USB probe routine (usb_audio_probe) happens in
> atomic context.
No, usb_audio_probe() doesn't take a lock. But
media_device_register_entity() seems taking a spinlock, instead.
Takashi
next prev parent reply other threads:[~2016-03-14 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 1:48 [PATCH] media: add GFP flag to media_*() that could get called in atomic context Shuah Khan
2016-03-13 8:30 ` Nicholas Mc Guire
2016-03-13 11:50 ` Mauro Carvalho Chehab
2016-03-14 7:22 ` Sakari Ailus
2016-03-14 10:13 ` Mauro Carvalho Chehab
2016-03-14 10:33 ` Takashi Iwai [this message]
2016-03-14 10:52 ` Sakari Ailus
2016-03-14 11:46 ` Mauro Carvalho Chehab
2016-03-14 12:09 ` Sakari Ailus
2016-03-15 15:55 ` Mauro Carvalho Chehab
2016-03-16 8:28 ` Sakari Ailus
2016-03-16 12:02 ` Mauro Carvalho Chehab
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=s5hmvq14adm.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Julia.Lawall@lip6.fr \
--cc=a.hajda@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=chehabrafael@gmail.com \
--cc=crope@iki.fi \
--cc=dan.carpenter@oracle.com \
--cc=der.herr@hofr.at \
--cc=devel@driverdev.osuosl.org \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=hyun.kwon@xilinx.com \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lixiubo@cmss.chinamobile.com \
--cc=mchehab@osg.samsung.com \
--cc=navyasri.tech@gmail.com \
--cc=perex@perex.cz \
--cc=prabhakar.csengg@gmail.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=shuahkh@osg.samsung.com \
--cc=soren.brinkmann@xilinx.com \
--cc=tommi.franttila@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).