linux-kernel - [PATCH 0/3] repair RTC subsys (for i.MX)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1304523088-17039-1-git-send-email-w.sang@pengutronix.de>
Date:	Wed,  4 May 2011 17:31:25 +0200
From:	Wolfram Sang <w.sang@...gutronix.de>
To:	rtc-linux@...glegroups.com
Cc:	linux-kernel@...r.kernel.org, johnstul@...ibm.com,
	Wolfram Sang <w.sang@...gutronix.de>
Subject: [PATCH 0/3] repair RTC subsys (for i.MX)

The recent updates to the RTC subsystem (removing UIE interrupts and use
alarms instead) introduced two problems for i.MX (and the subsys in
general, I'd think):

a) because registering the rtc now calls get_alarm(), the requirement
has been added for a lot of drivers that drvdata is properly set up
_before_ registering. rtc-mxc did not do that (probably bad; but as said
like a lot of other rtc-drivers currently) and oopsed.

b) the callbacks to the rtc-core for update_irqs have been removed, but
irq-handlers are still there, now being unused cruft. In case of
rtc-mxc, this is only one if-block, but for rtc-mc13xxx.c this is a
seperate handler.

>From a glimpse, most platform drivers seem to have at least one of these
problems now :( John, am I correct or am I missing something?

Kind regards,

   Wolfram

Wolfram Sang (3):
  rtc: mc13xxx: remove UIE signaling
  rtc: mxc: fix crash on boot
  rtc: mxc: remove UIE signaling

 drivers/rtc/rtc-mc13xxx.c |   23 -----------------------
 drivers/rtc/rtc-mxc.c     |   22 +++++++++++-----------
 2 files changed, 11 insertions(+), 34 deletions(-)

-- 
1.7.2.5

--
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/