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:	Tue, 27 Mar 2012 09:54:48 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Daniel Kurtz <djkurtz@...omium.org>
Cc:	Keith Packard <keithp@...thp.com>, David Airlie <airlied@...ux.ie>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Benson Leung <bleung@...omium.org>,
	Yufeng Shen <miletus@...omium.org>
Subject: Re: [PATCH 02/11 v3] drm/i915/intel_i2c: assign HDMI port D to pin
 pair 6

On Tue, Mar 27, 2012 at 01:49:51AM +0800, Daniel Kurtz wrote:
> I'm not sure what a "Bspec" is, but here is the documents I used:
> 
> [DevSNB+]: http://intellinuxgraphics.org/documentation/SNB/IHD_OS_Vol3_Part3.pdf
> Section 2.2.2 lists the 6 gmbus ports (gpio pin pairs):
>   [ 5: HDMI/DPD, 4: HDMIB, 3: HDMI/DPC, 2: LVDS, 1: SSC, 0: VGA ]
> 2.2.2.1 lists the GPIO registers to control these 6 ports.
> 2.2.3.1 lists the mapping between 5 of these gmbus ports and the 3
> Pin_Pair_Select bits (of the GMBUS0 register).  This table is missing
> HDMIB (port 101).
> 
> [DevIBX]: http://intellinuxgraphics.org/IHD_OS_Vol3_Part3r2.pdf
> Section 2.2.2 lists the same 6 gmbus ports plus two 'reserved' gpio ports.
> 2.2.2.1 lists 8 GPIO registers... however, it says the size of the
> block is 6x32, which implies that those 2 reserved GPIO registers
> (GPIO_6 & GPIO_7) don't actually exist (or are irrelevant).
> 2.2.3.1 lists the mapping between the 6 named gmbus ports and the 3
> Pin_Pair_Select bits (of the GMBUS0 register).  This table has HDMIB.

Exactly this. Bspec is the internal name for what these public docs are
based on. When fixing up an inconsistency wrt the docs it's always good to
cite it like this, so that later on people can cross check. And we need
section numbers because they are the most stable - Internal Bspec is just
a collection of individual sections as html pages. And hw people also tend
to use the same sections for the same stuff in newer/older chips.

Cheers, Daniel
-- 
Daniel Vetter
Mail: daniel@...ll.ch
Mobile: +41 (0)79 365 57 48
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ