linux-kernel - Re: [PATCH v5 3/3] USB: ohci-nxp: Support for LPC32xx

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120311074323.GA30894@pengutronix.de>
Date:	Sun, 11 Mar 2012 08:43:23 +0100
From:	Wolfram Sang <w.sang@...gutronix.de>
To:	Roland Stigge <stigge@...com.de>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	kevin.wells@....com, linux-arm-kernel@...ts.infradead.org,
	arnd@...db.de
Subject: Re: [PATCH v5 3/3] USB: ohci-nxp: Support for LPC32xx

> > And while we are at it: Could you also try replacing i2c_write()
> > with i2c_smbus_write_byte_data(isp1301_i2c_client, reg, val)?
> 
> Interestingly now, replacing i2c_write() calls with
> i2c_smbus_write_byte_data() did _not_ work (hardware initialization
> failure). I guess this is due to the differences between i2c and
> smbus, and the hardware only handles the former correctly?

Did you take into consideration that the smbus-call has (client, reg, val) as
arguments while i2c_write has (val, reg), that is you have to swap the
arguments?

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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