linux-kernel - Re: [PATCH] i2c-ocores: add common clock support

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150122150717.GJ3413@katana>
Date:	Thu, 22 Jan 2015 16:07:17 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Max Filippov <jcmvbkbc@...il.com>
Cc:	Peter Korsgaard <jacmet@...site.dk>, linux-i2c@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i2c-ocores: add common clock support


> The clock here is not the i2c bus clock, but the clock input of the

Yes, what I would expect from a clk-property :)

> controller. The function ocores_init initializes the prescaler register of
> the controller so that the bus clock equals 100kHz (internal clock
> runs at 500kHz):

'clock-frequency' usually describes the I2C bus speed. So, for ocores,
it describes speed of the clock for the controller? That would be
ouch...


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)