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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 6 Jul 2019 22:04:20 +0200
From:   Alexandre Belloni <>
To:     Frank Wunderlich <>
Cc:     Lee Jones <>, Rob Herring <>,
        Mark Rutland <>,
        Matthias Brugger <>,
        Sean Wang <>,
        Sebastian Reichel <>,
        Alessandro Zummo <>,,,,,,,
        Eddie Huang <>,
        Thomas Gleixner <>,
        Richard Fontana <>,
        Allison Randal <>,
        "David S . Miller" <>,
        Mauro Carvalho Chehab <>,
        Greg Kroah-Hartman <>,
        Rob Herring <>,
        Linus Walleij <>,
        Nicolas Ferre <>,
        "Paul E . McKenney" <>,
        Josef Friedl <>
Subject: Re: Re: Re: [PATCH v2 3/7] rtc: mt6397: improvements of rtc driver

On 06/07/2019 18:15:20+0200, Frank Wunderlich wrote:
> > Gesendet: Freitag, 05. Juli 2019 um 23:24 Uhr
> > Von: "Alexandre Belloni" <>
> > Let's say the RTC has been used to start your platform, then the irq
> > handler will be called as soon as the irq is requested, leading to a
> > null pointer dereference.
> i cannot test this with my platform, but i have changed it in my repo
> > Yes and IIRC, I did comment that the rtc change also had to be separated
> > from 1/7.
> also this is put in separate commit, can you take a look before i post v3?
> > Also, I really doubt this new compatible is necessary at all as you
> > could simply directly use mediatek,mt6397-rtc.
> imho this can confuse because the wrong chip-name is used in dts

This is not true, we do that all the time and the immediate benefit of
using the mt6397 compatible is that then there is no need to
synchronize between subsystems. If you want to be absolutely
conservative, you could use

compatible = "mediatek,mt6323-rtc", "mediatek,mt6397-rtc";

in your DT.

Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering

Powered by blists - more mailing lists