Linux RTC
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Michal Simek <michal.simek@xilinx.com>
Cc: Michal Simek <monstr@monstr.eu>,
	John Stultz <john.stultz@linaro.org>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>
Subject: Re: [rtc-linux] RTC used as a module
Date: Mon, 21 Aug 2017 15:00:24 +0200	[thread overview]
Message-ID: <44ceadeb-812a-e639-4c53-4cc11eb9dec4@xilinx.com> (raw)
In-Reply-To: <20170821125344.ch36irhbmuyda7vw@piout.net>

On 21.8.2017 14:53, Alexandre Belloni wrote:
> On 21/08/2017 at 14:47:20 +0200, Alexandre Belloni wrote:
>> On 21/08/2017 at 14:19:07 +0200, Michal Simek wrote:
>>> On 21.8.2017 14:13, Alexandre Belloni wrote:
>>>> On 21/08/2017 at 12:50:34 +0200, Michal Simek wrote:
>>>>> Hi,
>>>>>
>>>>> On 21.8.2017 00:03, Alexandre Belloni wrote:
>>>>>> Hi Michal,
>>>>>>
>>>>>> I've just send a patch to fix this issue (and avoid your other patch).
>>>>>>
>>>>>> Could you test it? (I did test on an atmel platform)
>>>>>>
>>>>>> Sorry it took so long!
>>>>>
>>>>> not a problem but it looks like it is still just temporary solution. I
>>>>> would expect that you can't unload module when this alarm is used. It if
>>>>> it is not used then you should be able to remove it.
>>>>>
>>>>
>>>> Yes, the alarmtimer handling needs to be made more flexible, especially
>>>> in the rtc device selection.
>>>
>>> ok. What about to extend that commit message for the patch you sent to
>>> explicitly say that this is temporary solution and what should be the
>>> right fix?
>>>
>>> Maybe you can also add link that patch which introduced this issue.
>>> It was in that patch I sent.
>>>
>>
>> You didn't pinpoint the correct patch. The patch introducing the issue
>> you were seeing (i.e. being able to remove the module) is
>> 8bc0dafb5cf38a19484dfb16e2c6d29e85820046. Before this patch,
>> rtc_class_open() was called and this prevented the module from being
>> removed (it does try_module_get). For now, this is how the feature has
>> been implemented since 2011 and nobody cared enough to change that
>> behaviour.
>>
> 
> To be clear, I'm not saying this should not be done. I'm just try to
> explain that this would not be a fix but rather a feature improvement.


I am not quite sure I agree with this description. It doesn't mean that
none care about this from 2011 that this is correct behavior.
You know much more than I in this area but it seems to me quite normal
that if you have module and features which implement and you are not
using them that you can remove module.
It means your patch is a temporary solution for bug introduced in 2011
and found in 2016/2017.

Thanks,
Michal




-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2017-08-21 13:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 13:02 [rtc-linux] RTC used as a module Michal Simek
2017-02-23 12:14 ` Alexandre Belloni
2017-03-03  9:41   ` Michal Simek
2017-03-03 14:46     ` Michal Simek
2017-03-03 15:09       ` Alexandre Belloni
2017-03-03 19:55         ` Michal Simek
2017-03-03 20:04       ` John Stultz
2017-03-06 14:56         ` Michal Simek
2017-03-16 15:35           ` Michal Simek
2017-04-07  7:12             ` Michal Simek
2017-06-29  7:34               ` Michal Simek
2017-08-20 22:03                 ` Alexandre Belloni
2017-08-21 10:50                   ` Michal Simek
2017-08-21 12:13                     ` Alexandre Belloni
2017-08-21 12:19                       ` Michal Simek
2017-08-21 12:47                         ` Alexandre Belloni
2017-08-21 12:50                           ` Michal Simek
2017-08-21 12:53                           ` Alexandre Belloni
2017-08-21 13:00                             ` Michal Simek [this message]

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=44ceadeb-812a-e639-4c53-4cc11eb9dec4@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=john.stultz@linaro.org \
    --cc=monstr@monstr.eu \
    --cc=rtc-linux@googlegroups.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