diff options
author | Shobhit Kumar <shobhit.kumar@intel.com> | 2015-02-05 12:40:56 +0100 |
---|---|---|
committer | Jani Nikula <jani.nikula@intel.com> | 2015-02-09 13:26:19 +0100 |
commit | d180d2bbb66579e3bf449642b8ec2a76f4014fcd (patch) | |
tree | 4eb557df13a787ffad4a66981e48a1544bfddac5 /drivers/gpu/drm/rockchip | |
parent | drm/i915: Prevent use-after-free in invalidate_range_start callback (diff) | |
download | linux-d180d2bbb66579e3bf449642b8ec2a76f4014fcd.tar.xz linux-d180d2bbb66579e3bf449642b8ec2a76f4014fcd.zip |
drm/i915: Correct the IOSF Dev_FN field for IOSF transfers
As per the specififcation, the SB_DevFn is the PCI_DEVFN of the target
device and not the source. So PCI_DEVFN(2,0) is not correct. Further the
port ID should be enough to identify devices unless they are MFD. The
SB_DevFn was intended to remove ambiguity in case of these MFD devices.
For non MFD devices the recommendation for the target device IP was to
ignore these fields, but not all of them followed the recommendation.
Some like CCK ignore these fields and hence PCI_DEVFN(2, 0) works and so
does PCI_DEVFN(0, 0) as it works for DPIO. The issue came to light because
of GPIONC which was not getting programmed correctly with PCI_DEVFN(2, 0).
It turned out that this did not follow the recommendation and expected 0
in this field.
In general the recommendation is to use SB_DevFn as PCI_DEVFN(0, 0) for
all devices except target PCI devices.
Signed-off-by: Shobhit Kumar <shobhit.kumar@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: stable@vger.kernel.org
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/gpu/drm/rockchip')
0 files changed, 0 insertions, 0 deletions