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] [day] [month] [year] [list]
Date:	Fri, 11 Sep 2015 19:51:59 -0700
From:	Greg Kroah-Hartman <greg@...ah.com>
To:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:	Mike Rapoport <mike.rapoport@...il.com>,
	Teddy Wang <teddy.wang@...iconmotion.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 06/17] staging: sm750fb: rename swI2CInit to
 sm750_sw_i2c_init

On Thu, Sep 10, 2015 at 06:31:08PM +0530, Sudip Mukherjee wrote:
> On Thu, Sep 10, 2015 at 03:39:58PM +0300, Mike Rapoport wrote:
> > Hi Sudip,
> > 
> > On Thu, Sep 10, 2015 at 10:10:19AM +0530, Sudip Mukherjee wrote:
> > > On Wed, Sep 09, 2015 at 01:07:04PM -0700, Greg Kroah-Hartman wrote:
> > > > > 
> > > > > As far as I understood, the intention for HW is for using i2c
> > > > > controller, and SW is for using gpio bit-bang
> > > > 
> > > > big-bang i2c?  ick.
> > > :(
> > > Yes, there is a special version of SM750 which uses sw i2c.
> > > SM750LE is a special version which only Huawei uses.
> > 
> > If I'm not mistaken, device variant can be identified in run-time and
> > i2c implementation may be selected accordingly. Am I right?
> Yes, that is a possibility but I do not have this SM750LE hardware, so
> if anything breaks in the sw i2c while trying to unify these two i2c
> codes, I will not be able to test.
> Maybe Greg can give some idea here about how to proceed.

No idea, sorry.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists