On Tuesday, 14 August 2018 17:21:24 MSK Thierry Reding wrote: > On Mon, Aug 13, 2018 at 06:09:46PM +0300, Dmitry Osipenko wrote: > > On Monday, 13 August 2018 17:50:14 MSK Thierry Reding wrote: > > > From: Thierry Reding <treding@xxxxxxxxxx> > > > > > > The BSEV clock has a separate gate bit and can not be assumed to be > > > always enabled. Add explicit handling for the BSEV clock and reset. > > > > > > This fixes an issue on Tegra124 where the BSEV clock is not enabled > > > by default and therefore accessing the BSEV registers will hang the > > > CPU if the BSEV clock is not enabled and the reset not deasserted. > > > > > > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx> > > > --- > > > > Are you sure that BSEV clock is really needed for T20/30? I've tried > > already to disable the clock explicitly and everything kept working, > > though I'll try again. > > I think you're right that these aren't strictly required for VDE to work > on Tegra20 and Tegra30. However, the BSEV clock and reset do exist on > those platforms, so I didn't see a reason why they shouldn't be handled > uniformly across all generations. It's a bit messy to have unsed clock being enabled. I guess BSEV clock on T20/30 only enables the AES engine. If the decryption engine is integrated with the video decoder, then the clock and reset should be requested by the driver, but BSEV should be kept disabled if it's not used. If BSEV clock isn't powering anything related to VDE on T20/30, then let's make BSEV clock and reset control optional. For the clock we could check whether err = -ENOENT and continue, later we may switch to devm_clk_get_optional() of the upcoming [0]. For the reset there is devm_reset_control_get_optional(). Please try to verify by all means that we can omit BSEV on T20/30. If you are not sure, then let's make them optional as we can always make them required later. P.S. I'll test and review all the patches during the next days. [0] https://lkml.org/lkml/2018/7/18/460 _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
