[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <5346AB76.1020800@samsung.com>
Date: Thu, 10 Apr 2014 08:32:22 -0600
From: Shuah Khan <shuah.kh@...sung.com>
To: Mauro Carvalho Chehab <m.chehab@...sung.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: Greg KH <gregkh@...uxfoundation.org>, tj@...nel.org,
rafael.j.wysocki@...el.com, linux@...ck-us.net, toshi.kani@...com,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
shuahkhan@...il.com, Shuah Khan <shuah.kh@...sung.com>
Subject: Re: [RFC PATCH 0/2] managed token devres interfaces
On 04/10/2014 05:38 AM, Mauro Carvalho Chehab wrote:
> Hi Alan,
>
> Em Thu, 10 Apr 2014 12:04:35 +0100
> One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk> escreveu:
>
>>>>> - Construct string with (dev is struct em28xx *dev)
>>>>> format: "tuner:%s-%s-%d"
>>>>> with the following:
>>>>> dev_name(&dev->udev->dev)
>>>>> dev->udev->bus->bus_name
>>>>> dev->tuner_addr
>>
>> What guarantees this won't get confused by hot plugging and re-use of the
>> bus slot ?
>
> Good point. Yes, this should be addressed.
>
This resource should be destroyed when em28xx_ handles unplug from its
em28xx_usb_disconnect() or in generic words, in its "uninit". It is a
matter of making sure this resource is handled in the "uninit" for this
media device/driver(s) like any other shared resource.
Would that cover the hot plugging and re-use of the bus slot scenario?
-- Shuah
--
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@...sung.com | (970) 672-0658
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists