Stefan Wahren <[email protected]> writes: > Am 02.12.2015 um 00:16 schrieb Eric Anholt: >> Stefan Wahren <[email protected]> writes: >> >>> It's possible that the pwm clock become an orphan. So better >>> check the result of clk_get_rate in order to prevent a division >>> by zero. >> How would we lose our clock when we're keeping the clock enabled from >> driver probe until remove? > > It's not the problem that we lose the clock inside this driver. The pwm > clock could be initial assigned to a unregistered parent clock like "GND". > > I'm refering to this discussion: > > http://lists.infradead.org/pipermail/linux-rpi-kernel/2015-November/002603.html
I actually would have expected that the prepare would error out on a clock with no rate set. Interesting. This seems like a good safety measure, so this one is also: Reviewed-by: Eric Anholt <[email protected]>
signature.asc
Description: PGP signature
