On Thu, May 23, 2024 at 10:46:35AM +0000, Alexey Romanov wrote: > Hi Conor, > > On Mon, May 06, 2024 at 04:47:29PM +0100, Conor Dooley wrote: > > On Mon, May 06, 2024 at 01:48:01PM +0000, Alexey Romanov wrote: > > > On Mon, Apr 15, 2024 at 05:43:15PM +0100, Conor Dooley wrote: > > > > On Thu, Apr 11, 2024 at 04:38:26PM +0300, Alexey Romanov wrote: > > > > > GXL crypto IP isn't connected to clk and seconnd interrput line, > > > > > so we must remove them from dt-bindings. > > > > > > > > How does the device work without a clock? > > > > > > It's clocked by a common clock, the vendor didn't provide more > > > information. It doesn't have any special clock domains. > > > > So the hardware block does have a clock, which, even if it is a clock > > shared with other hardware blocks, makes your patch incorrect. > > > > Is the "blkmv" clock the shared clock? > > I received accurate information from the vendor. Starting from GXL, > DMA engine is used for crypto HW and clock is hard weired to it (at RTL > level). > That's why we have to remove it from device tree, because we can't > control it anyway. That's not true, if the clock runs at a fixed frequency it should be described as a fixed-clock in the devicetree.
Attachment:
signature.asc
Description: PGP signature
