BranchCommit messageAuthorAge
master.gitconfig: sign tags by defaultTobias Klauser5 days
='nohover'>AgeCommit message (Collapse)AuthorFilesLines -next.git/commit/arch/m68k/include/asm/m527xsim.h?id=2d24b532f95b8b1b61bf670ef5bdee52bcf59640'>m68knommu: platform support for i2c devices on ColdFire SoCSteven King1-0/+8 2015-03-30m68knommu: ColdFire 5271 only has a single FEC controllerGreg Ungerer1-0/+2 2012-09-27m68knommu: fix inconsistent formating in ColdFire 527x definitionsGreg Ungerer1-17/+17 2012-09-27m68knommu: remove address offsets relative to IPSBAR for ColdFire 527xGreg Ungerer1-18/+34 2012-07-16m68knommu: use MCF_IRQ_PIT1 instead of MCFINT_VECBASE + MCFINT_PIT1Steven King1-0/+1 2012-03-05m68knommu: make 527x CPU reset register addressing consistentGreg Ungerer1-2/+2 2012-03-05m68knommu: make 527x QSPI platform addressing consistentGreg Ungerer1-0/+24 2012-03-05m68knommu: make 527x FEC platform addressing consistentGreg Ungerer1-0/+15 2012-03-05m68knommu: make 527x UART platform addressing consistentGreg Ungerer1-3/+7 2011-03-31Fix common misspellingsLucas De Marchi1-1/+1 2011-03-15m68knommu: external interrupt support to ColdFire intc-2 controllerGreg Ungerer1-0/+3 2011-03-15m68knommu: remove ColdFire CLOCK_DIV config optionGreg Ungerer1-0/+1 2011-03-15m68knommu: clean up use of MBAR for DRAM registers on ColdFire startGreg Ungerer1-13/+13 2011-03-15m68knommu: move ColdFire DMA register addresses to per-cpu headersGreg Ungerer1-0/+8 2011-03-15m68knommu: remove use of MBAR value for ColdFire 527x peripheral addressingGreg Ungerer1-3/+11 2011-03-15m68knommu: move ColdFire PIT timer base addressesGreg Ungerer1-3/+8 2011-03-15m68knommu: remove kludge seting of MCF_IPSBAR for ColdFire 54xxGreg Ungerer1-2/+3 2011-01-05m68knommu: create bit definitions for the version 2 ColdFire cache controllerGreg Ungerer1-0/+1 2011-01-05m68knommu: move UART addressing to part specific includesGreg Ungerer1-0/+6 2011-01-05m68knommu: fix clock rate value reported for ColdFire 54xx partsGreg Ungerer1-1/+2 2011-01-05m68knommu: move ColdFire CPU names into their headersGreg Ungerer1-0/+2 ass='logheader'>2014-11-05drm/edid: add #defines and helpers for ELDJani Nikula1-0/+102 In the interest of reducing magic numbers and having to cross check with the specs all the time. Signed-off-by: Jani Nikula <> Reviewed-by: Rodrigo Vivi <> Signed-off-by: Daniel Vetter <> 2014-06-02drm/edid: Parse and handle HDMI deep color modes.Mario Kleiner1-0/+5 Check the HDMI cea block for deep color mode bits. If available, assign the highest supported bpc for a hdmi display, corresponding to the given deep color modes. Signed-off-by: Mario Kleiner <> Signed-off-by: Alex Deucher <> 2013-09-02Merge branch 'drm-next-3.12' of git:// ↵Dave Airlie1-0/+1 into drm-next Alex writes: This is the radeon drm-next request. Big changes include: - support for dpm on CIK parts - support for ASPM on CIK parts - support for berlin GPUs - major ring handling cleanup - remove the old 3D blit code for bo moves in favor of CP DMA or sDMA - lots of bug fixes [airlied: fix up a bunch of conflicts from drm_order removal] * 'drm-next-3.12' of git:// (898 commits) drm/radeon/dpm: make sure dc performance level limits are valid (CI) drm/radeon/dpm: make sure dc performance level limits are valid (BTC-SI) (v2) drm/radeon: gcc fixes for extended dpm tables drm/radeon: gcc fixes for kb/kv dpm drm/radeon: gcc fixes for ci dpm drm/radeon: gcc fixes for si dpm drm/radeon: gcc fixes for ni dpm drm/radeon: gcc fixes for trinity dpm drm/radeon: gcc fixes for sumo dpm drm/radeonn: gcc fixes for rv7xx/eg/btc dpm drm/radeon: gcc fixes for rv6xx dpm drm/radeon: gcc fixes for radeon_atombios.c drm/radeon: enable UVD interrupts on CIK drm/radeon: fix init ordering for r600+ drm/radeon/dpm: only need to reprogram uvd if uvd pg is enabled drm/radeon: check the return value of uvd_v1_0_start in uvd_v1_0_init drm/radeon: split out radeon_uvd_resume from uvd_v4_2_resume radeon kms: fix uninitialised hotplug work usage in r100_irq_process() drm/radeon/audio: set up the sads on DCE3.2 asics drm/radeon: fix handling of variable sized arrays for router objects ... Conflicts: drivers/gpu/drm/i915/i915_dma.c drivers/gpu/drm/i915/i915_gem_dmabuf.c drivers/gpu/drm/i915/intel_pm.c drivers/gpu/drm/radeon/cik.c drivers/gpu/drm/radeon/ni.c drivers/gpu/drm/radeon/r600.c 2013-08-30drm/edid: add a helper function to extract the speaker allocation data block ↵Alex Deucher1-0/+1 (v3) This adds a helper function to extract the speaker allocation data block from the EDID. This data block describes what speakers are present on the display device. v2: update per Ville Syrjälä's comments v3: fix copy/paste typo in memory allocation Signed-off-by: Alex Deucher <> Reviewed-by: Ville Syrjälä <> Tested-by: Rafał Miłecki <> 2013-08-30drm: Add a helper to forge HDMI vendor infoframesLespiau, Damien1-0/+4 This can then be used by DRM drivers to setup their vendor infoframes. v2: Fix hmdi typo (Simon Farnsworth) v3: Adapt to the hdmi_vendor_infoframe rename Signed-off-by: Damien Lespiau <> Reviewed-by: Simon Farnsworth <> Reviewed-by: Ville Syrjälä <> Reviewed-by: Thierry Reding <> Signed-off-by: Dave Airlie <> 2013-04-23drm: add drm_edid_to_eld helper extracting SADs from EDID (v2)Rafał Miłecki1-0/+9 Some devices (ATI/AMD cards) don't support passing ELD struct to the hardware but just require filling specific registers and then the hardware/firmware does the rest. In such cases we need to read the info from SAD blocks and put them in the correct registers. agd5f: note that the returned pointer needs to be kfreed as per Christian's suggestion. v2: fix warning Signed-off-by: Rafał Miłecki <> Reviewed-by: Christian König <> Signed-off-by: Alex Deucher <> 2013-02-22drm: Add HDMI infoframe helpersThierry Reding1-0/+6 Add a generic helper to fill in an HDMI AVI infoframe with data extracted from a DRM display mode. Signed-off-by: Thierry Reding <> Reviewed-by: Alex Deucher <> 2012-04-23drm/edid: Add packed attribute to new gtf2 and cvt structsTakashi Iwai1-2/+2 The new structs added in struct detailed_data_monitor_range must be marked with packed attribute although the outer struct itself is already marked as packed. Otherwise these 7-bytes structs may be aligned, and give the wrong position and size for the data. Signed-off-by: Takashi Iwai <> Acked-by: Adam Jackson <> Signed-off-by: Dave Airlie <> 2012-04-20drm/edid: Update range descriptor struct for EDID 1.4Adam Jackson1-6/+20 Signed-off-by: Adam Jackson <> Tested-by: Takashi Iwai <> Reviewed-by: Rodrigo Vivi <> Signed-off-by: Dave Airlie <> 2012-03-20drm: allow loading an EDID as firmware to override broken monitorCarsten Emde1-0/+1 Broken monitors and/or broken graphic boards may send erroneous or no EDID data. This also applies to broken KVM devices that are unable to correctly forward the EDID data of the connected monitor but invent their own fantasy data. This patch allows to specify an EDID data set to be used instead of probing the monitor for it. It contains built-in data sets of frequently used screen resolutions. In addition, a particular EDID data set may be provided in the /lib/firmware directory and loaded via the firmware interface. The name is passed to the kernel as module parameter of the drm_kms_helper module either when loaded options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel commandline parameter drm_kms_helper.edid_firmware=edid/1280x1024.bin It is also possible to restrict the usage of a specified EDID data set to a particular connector. This is done by prepending the name of the connector to the name of the EDID data set using the syntax edid_firmware=[<connector>:]<edid> such as, for example, edid_firmware=DVI-I-1:edid/1920x1080.bin in which case no other connector will be affected. The built-in data sets are Resolution Name -------------------------------- 1024x768 edid/1024x768.bin 1280x1024 edid/1280x1024.bin 1680x1050 edid/1680x1050.bin 1920x1080 edid/1920x1080.bin They are ignored, if a file with the same name is available in the /lib/firmware directory. The built-in EDID data sets are based on standard timings that may not apply to a particular monitor and even crash it. Ideally, EDID data of the connected monitor should be used. They may be obtained through the drm/cardX/cardX-<connector>/edid entry in the /sys/devices PCI directory of a correctly working graphics adapter. It is even possible to specify the name of an EDID data set on-the-fly via the /sys/module interface, e.g. echo edid/myedid.bin >/sys/module/drm_kms_helper/parameters/edid_firmware The new screen mode is considered when the related kernel function is called for the first time after the change. Such calls are made when the X server is started or when the display settings dialog is opened in an already running X server. Signed-off-by: Carsten Emde <> Signed-off-by: Dave Airlie <> 2011-09-21drm: support routines for HDMI/DP ELDWu Fengguang1-0/+9 ELD (EDID-Like Data) describes to the HDMI/DP audio driver the audio capabilities of the plugged monitor. This adds drm_edid_to_eld() for converting EDID to ELD. The converted ELD will be saved in a new drm_connector.eld[128] data field. This is necessary because the graphics driver will need to fixup some of the data fields (eg. HDMI/DP connection type, AV sync delay) before writing to the hardware ELD buffer. drm_av_sync_delay() will help the graphics drivers dynamically compute the AV sync delay for fixing-up the ELD. ELD selection policy: it's possible for one encoder to be associated with multiple connectors (ie. monitors), in which case the first found ELD will be returned by drm_select_eld(). This policy may not be suitable for all users, but let's start it simple first. The impact of ELD selection policy: assume there are two monitors, one supports stereo playback and the other has 8-channel output; cloned display mode is used, so that the two monitors are associated with the same internal encoder. If only the stereo playback capability is reported, the user won't be able to start 8-channel playback; if the 8-channel ELD is reported, then user space applications may send 8-channel samples down, however the user may actually be listening to the 2-channel monitor and not connecting speakers to the 8-channel monitor. According to James, many TVs will either refuse the display anything or pop-up an OSD warning whenever they receive hdmi audio which they cannot handle. Eventually we will require configurability and/or per-monitor audio control even when the video is cloned. CC: Zhao Yakui <> CC: Wang Zhenyu <> CC: Jeremy Bush <> CC: Christopher White <> CC: Pierre-Louis Bossart <> CC: Paul Menzel <> CC: James Cloos <> CC: Chris Wilson <> Signed-off-by: Ben Skeggs <> Signed-off-by: Wu Fengguang <> Signed-off-by: Keith Packard <> 2011-04-28drm: parse color format support for digital displaysJesse Barnes1-0/+8 EDID 1.4 digital displays report the color spaces they support in the features block. Add support for grabbing this data and stuffing it into the display_info struct for driver use. Signed-off-by: Jesse Barnes <> Reviewed-by: Alex Deucher <> Signed-off-by: Dave Airlie <> 2011-04-28drm: add bit depth parsingJesse Barnes1-1/+16 EDID 1.4 digital monitors report the bit depth supported in the input field. Add support for parsing this out and storing the info in the display_info structure for use by drivers. [airlied: tweaked to fix inter-patch dependency] Signed-off-by: Jesse Barnes <> Reviewed-by: Adam Jackson <> Signed-off-by: Dave Airlie <> 2010-08-10drm/edid: Add detailed block walk for CEA extensionsAdam Jackson1-0/+6 Signed-off-by: Adam Jackson <> Signed-off-by: Dave Airlie <> 2010-05-18drm_edid: There should be 6 Standard TimingsDan Carpenter1-1/+1 Smatch complained that we initialize 6 elements in add_detailed_modes() but the timings[] array is declared with 5 elements. Adam Jackson verified that 6 is the correct number of timings. On Mon, May 10, 2010 at 12:08:24PM -0400, Adam Jackson wrote: > > > struct std_timing timings[5]; > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This decl is wrong, should be 6. From the 1.4 spec: > > "Six additional Standard Timings may be listed as a display descriptor > (tag #FAh)." > > The 1.3 spec is a little less explicit about it, but does show 6 > standard timing codes in the 0xFA detailed subblock, terminated by 0x0A > in the 18th byte. I don't have the docs for 1.2 or earlier, but we're > paranoid enough about not adding broken timings that we should be fine. This patch is basically a clean up, because timings[] is declared inside a union and increasing the number of elements here doesn't change the overall size of the union. Signed-off-by: Dan Carpenter <> Signed-off-by: Dave Airlie <> 2010-04-06drm/edid: Remove arbitrary EDID extension limitAdam Jackson1-3/+0 Signed-off-by: Adam Jackson <> Signed-off-by: Dave Airlie <> 2010-02-09drm/radeon/kms: add support for hardcoded edids in rom (v2)Alex Deucher1-0/+3 Some servers hardcode an edid in rom so that they will work properly with KVMs. This is a port of the relevant code from the ddx. [airlied: reworked to validate edid at boot stage - and remove special quirk, if there is a valid EDID in the BIOS rom we'll just try and use it.] Signed-off-by: Alex Deucher <> Signed-off-by: Dave Airlie <>