From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from avon.wwwdotorg.org (avon.wwwdotorg.org. [70.85.31.133]) by gmr-mx.google.com with ESMTPS id pn4si218033igb.3.2016.05.10.16.02.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 May 2016 16:02:30 -0700 (PDT) Subject: [rtc-linux] Re: [PATCH] rtc: rename so the tps6586x-rtc module can be autoloaded at boot To: Nicolas Chauvet References: <1462876002-6462-1-git-send-email-kwizart@gmail.com> <573201AD.7080705@wwwdotorg.org> Cc: Alessandro Zummo , Alexandre Belloni , rtc-linux@googlegroups.com, linux-omap@vger.kernel.org, linux-tegra@vger.kernel.org From: Stephen Warren Message-ID: <57326883.6020000@wwwdotorg.org> Date: Tue, 10 May 2016 17:02:27 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , On 05/10/2016 03:44 PM, Nicolas Chauvet wrote: > 2016-05-10 17:43 GMT+02:00 Stephen Warren : >> On 05/10/2016 04:26 AM, Nicolas Chauvet wrote: >>> >>> This module is loaded by the related mfd driver which has >>> the needed MODULE_DEVICE_TABLE(i2c,...). >>> >>> This patch fix the modalias when the rtc driver is built >>> as a module, so the right name is used. >>> Everything operates correctly when this module is builtin. >> >> >> I'm sure this used to work. Do you know when/why it broke? Perhaps a Fixes: >> tag would be useful, and perhaps a Cc: stable? > > I don't remember autoloading of rtc-tps6586x.ko has ever worked. Then > there is still the issue of rtc modules loaded too late for the kernel > (or the kernel not capable to defer the read of hw clock), but that's > another issue. > > I first tried to report the issue on this bug tracker and at that > time, autoloading wasn't working (was in 2014). > https://bugzilla.redhat.com/show_bug.cgi?id=1074002 > > I'm sure current distros using an arm generic kernel (with all > modules) will rebase on kernel 4.4, but technically the bug is present > in kernel 3.10 from the oldest current maintained branch (since the > driver introduction). Ah, all the cases I used previous did indeed have the RTC driver built-in not a module, so that explains it. -- -- 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.