netdev - RE: [PATCH net-next 2/6] net: txgbe: Implement I2C bus master driver

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: <000001d96855$55648460$002d8d20$@trustnetic.com>
Date:   Thu, 6 Apr 2023 14:59:29 +0800
From:   Jiawen Wu <jiawenwu@...stnetic.com>
To:     "'Andrew Lunn'" <andrew@...n.ch>
Cc:     <netdev@...r.kernel.org>, <linux@...linux.org.uk>,
        <mengyuanlou@...-swift.com>
Subject: RE: [PATCH net-next 2/6] net: txgbe: Implement I2C bus master driver

> > > Is the I2C bus master your own IP, or have you licensed a core?
> > > Or using the open cores i2C bus master? I just want to make sure
> > > there is not already a linux driver for this.
> > >
> >
> > I use the I2C core driver, and implement my own i2c_algorithm.
> > I think it needs to configure my registers to realize the function.
> 
> I had a quick look, and it appears the hardware is not an open-cores
> derived I2C bus master.
> 
> As i tried to say, sometimes you just license an I2C bus master,
> rather than develop one from scratch. And if it was a licensed IP
> core, there is likely to be an existing driver.
> 

By consulting with hardware designers, our I2C licensed the IP of
Synopsys.
But I can't use the I2C_DESIGNWARE_CORE directly, because IRQ is not
supported in our I2C.