> I don't like this change. The RNG registers are documented as a part of > the same hardware block as the clock & power stuff which the CGU driver > handles, and indeed in the M200 SoC there is a power-related register > after the RNG registers. So shortening the range covered by the CGU > driver is not the right way to go. Could not find M200 SoC PM in ingenic's website or ftp. So did not notice this. > Perhaps you could instead have the CGU driver make use of the syscon > infrastructure to expose a regmap which your RNG driver could pick up & use? I will see how to use syscon and provide an updated patch. -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
