linux-kernel - [PATCH v2 0/2] check I2C device id for pca984x chips

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-next>] [day] [month] [year] [list]

Message-Id: <20180305205822.951-1-peda@axentia.se>
Date:   Mon,  5 Mar 2018 21:58:20 +0100
From:   Peter Rosin <peda@...ntia.se>
To:     linux-kernel@...r.kernel.org
Cc:     Peter Rosin <peda@...ntia.se>, Wolfram Sang <wsa@...-dreams.de>,
        Adrian Fiergolski <adrian.fiergolski@...n.ch>,
        linux-i2c@...r.kernel.org
Subject: [PATCH v2 0/2] check I2C device id for pca984x chips

Hi!

This series tries to check the I2C device id, but instead of open
coding the check in the pca954x driver, I have a new function in
the core doing the work.

Changes since v1:
- Added Tested-by tag from Adrian
- Added Reviewed-by tag from Wolfram
- Replaced client->flags with a zero in the i2c_smbus_xfer call

Wolfram: I'll send a pull with the first patch in a few days, to
allow for a second round of feedback now that the RFC marker is gone.

Cheers,
peda

Peter Rosin (2):
  i2c: add i2c_get_device_id() to get the standard i2c device id
  i2c: mux: pca954x: verify the device id of the pca984x chips

 drivers/i2c/i2c-core-base.c         | 33 ++++++++++++++++++++++
 drivers/i2c/muxes/i2c-mux-pca954x.c | 55 +++++++++++++++++++++++++++++++++----
 include/linux/i2c.h                 | 30 ++++++++++++++++++++
 3 files changed, 112 insertions(+), 6 deletions(-)

-- 
2.11.0