All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	"Luis de Bethencourt" <luis@debethencourt.com>,
	linux-sh@vger.kernel.org,
	"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	linux-samsung-soc@vger.kernel.org,
	"Hyun Kwon" <hyun.kwon@xilinx.com>,
	"Matthias Schwarzott" <zzam@gentoo.org>,
	"Kyungmin Park" <kyungmin.park@samsung.com>,
	"Tommi Rantala" <tt.rantala@gmail.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Hans Verkuil" <hans.verkuil@cisco.com>,
	linux-media@vger.kernel.org, "Kukjin Kim" <kgene@kernel.org>,
	"Krzysztof Kozlowski" <k.kozlowski@samsung.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Olli Salonen" <olli.salonen@iki.fi>,
	linux-arm-kernel@lists.infradead.org,
	"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
	"Antti Palosaari" <crope@iki.fi>,
	"Shuah Khan" <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/2] [media] media-device: split media initialization and registration
Date: Mon, 21 Dec 2015 11:37:34 -0300	[thread overview]
Message-ID: <56780EAE.7090909@osg.samsung.com> (raw)
In-Reply-To: <20151215091342.2f825d91@recife.lan>

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

WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] [media] media-device: split media initialization and registration
Date: Mon, 21 Dec 2015 14:37:34 +0000	[thread overview]
Message-ID: <56780EAE.7090909@osg.samsung.com> (raw)
In-Reply-To: <20151215091342.2f825d91@recife.lan>

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

WARNING: multiple messages have this Message-ID (diff)
From: javier@osg.samsung.com (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] [media] media-device: split media initialization and registration
Date: Mon, 21 Dec 2015 11:37:34 -0300	[thread overview]
Message-ID: <56780EAE.7090909@osg.samsung.com> (raw)
In-Reply-To: <20151215091342.2f825d91@recife.lan>

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

WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	"Luis de Bethencourt" <luis@debethencourt.com>,
	linux-sh@vger.kernel.org,
	"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	linux-samsung-soc@vger.kernel.org,
	"Hyun Kwon" <hyun.kwon@xilinx.com>,
	"Matthias Schwarzott" <zzam@gentoo.org>,
	"Kyungmin Park" <kyungmin.park@samsung.com>,
	"Tommi Rantala" <tt.rantala@gmail.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Hans Verkuil" <hans.verkuil@cisco.com>,
	linux-media@vger.kernel.org, "Kukjin Kim" <kgene@kernel.org>,
	"Krzysztof Kozlowski" <k.kozlowski@samsung.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Olli Salonen" <olli.salonen@iki.fi>,
	linux-arm-kernel@lists.infradead.org,
	"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
	"Antti Palosaari" <crope@iki.fi>,
	"Shuah Khan" <shuahkh@osg.samsung.com>,
	"Rafael Lourenço de Lima Chehab" <chehabrafael@gmail.com>
Subject: Re: [PATCH 2/2] [media] media-device: split media initialization and registration
Date: Mon, 21 Dec 2015 11:37:34 -0300	[thread overview]
Message-ID: <56780EAE.7090909@osg.samsung.com> (raw)
In-Reply-To: <20151215091342.2f825d91@recife.lan>

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

  reply	other threads:[~2015-12-21 14:37 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 13:03 [PATCH 0/2] [media] Fix race between graph enumeration and entities registration Javier Martinez Canillas
2015-09-10 13:03 ` Javier Martinez Canillas
2015-09-10 13:03 ` Javier Martinez Canillas
2015-09-10 13:03 ` Javier Martinez Canillas
2015-09-10 13:03 ` [PATCH 1/2] [media] media-device: check before unregister if mdev was registered Javier Martinez Canillas
2015-09-10 17:15   ` Sakari Ailus
2015-09-10 17:35     ` Javier Martinez Canillas
2015-09-10 13:03 ` [PATCH 2/2] [media] media-device: split media initialization and registration Javier Martinez Canillas
2015-09-10 13:03   ` Javier Martinez Canillas
2015-09-10 13:03   ` Javier Martinez Canillas
2015-09-10 13:03   ` Javier Martinez Canillas
2015-09-10 17:14   ` Sakari Ailus
2015-09-10 17:14     ` Sakari Ailus
2015-09-10 17:14     ` Sakari Ailus
2015-09-10 17:14     ` Sakari Ailus
2015-09-10 18:31     ` Javier Martinez Canillas
2015-09-10 18:31       ` Javier Martinez Canillas
2015-09-10 18:31       ` Javier Martinez Canillas
2015-09-10 18:31       ` Javier Martinez Canillas
2015-09-11  5:51       ` Sakari Ailus
2015-09-11  5:51         ` Sakari Ailus
2015-09-11  5:51         ` Sakari Ailus
2015-09-11  5:51         ` Sakari Ailus
2015-09-11  7:31         ` Javier Martinez Canillas
2015-09-11  7:31           ` Javier Martinez Canillas
2015-09-11  7:31           ` Javier Martinez Canillas
2015-09-11  7:31           ` Javier Martinez Canillas
2015-09-11  9:07           ` Mauro Carvalho Chehab
2015-09-11  9:07             ` Mauro Carvalho Chehab
2015-09-11  9:07             ` Mauro Carvalho Chehab
2015-09-11  9:07             ` Mauro Carvalho Chehab
2015-09-11  9:28             ` Sakari Ailus
2015-09-11  9:28               ` Sakari Ailus
2015-09-11  9:28               ` Sakari Ailus
2015-09-11  9:28               ` Sakari Ailus
2015-12-15 11:13     ` Mauro Carvalho Chehab
2015-12-15 11:13       ` Mauro Carvalho Chehab
2015-12-15 11:13       ` Mauro Carvalho Chehab
2015-12-15 11:13       ` Mauro Carvalho Chehab
2015-12-21 14:37       ` Javier Martinez Canillas [this message]
2015-12-21 14:37         ` Javier Martinez Canillas
2015-12-21 14:37         ` Javier Martinez Canillas
2015-12-21 14:37         ` Javier Martinez Canillas
2015-12-28  1:14       ` Sakari Ailus
2015-12-28  1:14         ` Sakari Ailus
2015-12-28  1:14         ` Sakari Ailus
2015-12-28  1:14         ` Sakari Ailus
2015-12-28 10:26         ` Mauro Carvalho Chehab
2015-12-28 10:26           ` Mauro Carvalho Chehab
2015-12-28 10:26           ` Mauro Carvalho Chehab
2015-12-28 10:26           ` Mauro Carvalho Chehab
2015-12-28 12:52           ` Mauro Carvalho Chehab
2015-12-28 12:52             ` Mauro Carvalho Chehab
2015-12-28 12:52             ` Mauro Carvalho Chehab
2015-12-28 12:52             ` Mauro Carvalho Chehab
2015-09-10 17:39   ` Sakari Ailus
2015-09-10 17:39     ` Sakari Ailus
2015-09-10 17:39     ` Sakari Ailus
2015-09-10 17:39     ` Sakari Ailus
2015-09-10 18:33     ` Javier Martinez Canillas
2015-09-10 18:33       ` Javier Martinez Canillas
2015-09-10 18:33       ` Javier Martinez Canillas
2015-09-10 18:33       ` Javier Martinez Canillas

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=56780EAE.7090909@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=crope@iki.fi \
    --cc=hans.verkuil@cisco.com \
    --cc=hyun.kwon@xilinx.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-samsung-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=luis@debethencourt.com \
    --cc=mchehab@osg.samsung.com \
    --cc=michal.simek@xilinx.com \
    --cc=olli.salonen@iki.fi \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=tt.rantala@gmail.com \
    --cc=zzam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.