linux-kernel - [PATCH 0/3 v2] Updates for exynos4210 and DT-based systems

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

Date:	Tue, 13 Mar 2012 17:54:36 +0100
From:	Karol Lewandowski <k.lewandowsk@...sung.com>
To:	ben-linux@...ff.org
Cc:	thomas.abraham@...aro.org, m.szyprowski@...sung.com,
	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org,
	linux-samsung-soc@...r.kernel.org, t.stanislaws@...sung.com,
	Karol Lewandowski <k.lewandowsk@...sung.com>
Subject: [PATCH 0/3 v2] Updates for exynos4210 and DT-based systems

Changes since v1:
 - Move unrelated code fragment to separate patch (of_match_ptr())
 - Move device-type handling to separate function and rework its
   internals a bit

This patchset reworks i2c-s3c2410 driver a bit to better handle
device tree-enabled platforms and adds two quirks required by
exynos4210-specific I2C controller used by s5p-hdmi driver.

This patchset is based on "i2c-bjdooks/for-34/i2c/i2c-samsung" branch
taken from:

  git://git.fluff.org/bjdooks/linux.git

Karol Lewandowski (3):
  i2c-s3c2410: Drop unused define
  i2c-s3c2410: Rework device type handling
  i2c-s3c2410: Add HDMIPHY quirk for S3C2440

 .../devicetree/bindings/i2c/samsung-i2c.txt        |   10 ++-
 drivers/i2c/busses/i2c-s3c2410.c                   |   93 +++++++++++++++-----
 2 files changed, 77 insertions(+), 26 deletions(-)

-- 
1.7.9

--
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/