[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56780EAE.7090909@osg.samsung.com>
Date: Mon, 21 Dec 2015 11:37:34 -0300
From: Javier Martinez Canillas <javier@....samsung.com>
To: Mauro Carvalho Chehab <mchehab@....samsung.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org,
Luis de Bethencourt <luis@...ethencourt.com>,
linux-sh@...r.kernel.org,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Sören Brinkmann <soren.brinkmann@...inx.com>,
linux-samsung-soc@...r.kernel.org,
Hyun Kwon <hyun.kwon@...inx.com>,
Matthias Schwarzott <zzam@...too.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Tommi Rantala <tt.rantala@...il.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Hans Verkuil <hans.verkuil@...co.com>,
linux-media@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Michal Simek <michal.simek@...inx.com>,
Olli Salonen <olli.salonen@....fi>,
linux-arm-kernel@...ts.infradead.org,
Stefan Richter <stefanr@...6.in-berlin.de>,
Antti Palosaari <crope@....fi>,
Shuah Khan <shuahkh@....samsung.com>,
Rafael Lourenço de Lima Chehab
<chehabrafael@...il.com>
Subject: Re: [PATCH 2/2] [media] media-device: split media initialization and
registration
Hello Mauro,
On 12/15/2015 08:13 AM, Mauro Carvalho Chehab wrote:
[snip]
>>>
>>> /**
>>> - * media_device_register - register a media device
>>> + * media_device_init() - initialize a media device
>>> * @mdev: The media device
>>> *
>>> * The caller is responsible for initializing the media device before
>>> @@ -534,12 +534,11 @@ static void media_device_release(struct media_devnode *mdev)
>>> *
>>> * - dev must point to the parent device
>>> * - model must be filled with the device model name
>>> + *
>>> + * returns zero on success or a negative error code.
>>> */
>>> -int __must_check __media_device_register(struct media_device *mdev,
>>> - struct module *owner)
>>> +int __must_check media_device_init(struct media_device *mdev)
>>
>> I think I suggested making media_device_init() return void as the only
>> remaining source of errors would be driver bugs.
>>
>> I'd simply replace the WARN_ON() below with BUG().
>
> That sounds like bad idea to me, and it is against the current
> Kernel policy of using BUG() only when there's no other way, e. g. on
> event so severe that the Kernel has no other thing to do except to
> stop running.
>
I agree with you, that was exactly my point and what I told Sakari [0] but
he had a strong opinion about it and I didn't mind too much so I decided at
the end to just change it to a BUG_ON() so I could get his ack for this set.
> For sure, this is not the case here. Also, all drivers have already
> a logic that checks if the device init happened. So, they should already
> be doing the right thing.
>
> Regards,
> Mauro
[0]: https://lkml.org/lkml/2015/9/10/483
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
--
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