linux-kernel - Re: [PATCH 2/2] drm/msm/hdmi: add hdmi hdcp support (V2)

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]

Date:	Wed, 11 Feb 2015 14:23:59 -0800
From:	Bjorn Andersson <bjorn@...o.se>
To:	Jilai Wang <jilaiw@...eaurora.org>,
	Wolfram Sang <wsa@...-dreams.de>
Cc:	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	linux-arm-msm <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Rob Clark <robdclark@...il.com>
Subject: Re: [PATCH 2/2] drm/msm/hdmi: add hdmi hdcp support (V2)

On Wed, Feb 11, 2015 at 10:59 AM,  <jilaiw@...eaurora.org> wrote:
> There is one issue to use i2c_smbus_XX functions:
> i2c_smbus_read_i2c_block_data has limitation with the maximum count
> I2C_SMBUS_BLOCK_MAX.
> But in function hdmi_hdcp_recv_ksv_fifo, since the downstream ksv_fifo
> size will exceed this limitation and must be read in a single transaction,
> we can't use this function then.
>

That's interesting, because we have the same problem in the Synaptics
driver, where we want to read more than 32 bytes with a method that
follows the smbus flow.

Wolfram, do you have any input on making i2c_smbus* functions work for
larger accesses? Or should we just conclude that it's not "smbus" and
open code this in the various places?

Regards,
Bjorn
--
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/