aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/sun4i
ModeNameSize
-rw-r--r--Kconfig2384logplain
-rw-r--r--Makefile1308logplain
-rw-r--r--sun4i_backend.c29707logplain
-rw-r--r--sun4i_backend.h8374logplain
-rw-r--r--sun4i_crtc.c6823logplain
-rw-r--r--sun4i_crtc.h673logplain
-rw-r--r--sun4i_dotclock.c4555logplain
-rw-r--r--sun4i_dotclock.h405logplain
-rw-r--r--sun4i_drv.c12406logplain
-rw-r--r--sun4i_drv.h445logplain
-rw-r--r--sun4i_framebuffer.c1275logplain
-rw-r--r--sun4i_framebuffer.h333logplain
-rw-r--r--sun4i_frontend.c20650logplain
-rw-r--r--sun4i_frontend.h5363logplain
-rw-r--r--sun4i_hdmi.h10037logplain
-rw-r--r--sun4i_hdmi_ddc_clk.c3123logplain
-rw-r--r--sun4i_hdmi_enc.c22450logplain
-rw-r--r--sun4i_hdmi_i2c.c9212logplain
-rw-r--r--sun4i_hdmi_tmds_clk.c5280logplain
-rw-r--r--sun4i_layer.c7486logplain
-rw-r--r--sun4i_layer.h915logplain
-rw-r--r--sun4i_lvds.c3899logplain
-rw-r--r--sun4i_lvds.h280logplain
-rw-r--r--sun4i_rgb.c6295logplain
-rw-r--r--sun4i_rgb.h325logplain
-rw-r--r--sun4i_tcon.c45148logplain
-rw-r--r--sun4i_tcon.h11197logplain
-rw-r--r--sun4i_tv.c17926logplain
-rw-r--r--sun6i_drc.c3091logplain
-rw-r--r--sun6i_mipi_dsi.c34262logplain
-rw-r--r--sun6i_mipi_dsi.h1196logplain
-rw-r--r--sun8i_csc.c6583logplain
-rw-r--r--sun8i_csc.h884logplain
-rw-r--r--sun8i_dw_hdmi.c8646logplain
-rw-r--r--sun8i_dw_hdmi.h8421logplain
-rw-r--r--sun8i_hdmi_phy.c22520logplain
-rw-r--r--sun8i_hdmi_phy_clk.c4012logplain
-rw-r--r--sun8i_mixer.c16315logplain
-rw-r--r--sun8i_mixer.h6833logplain
-rw-r--r--sun8i_tcon_top.c7918logplain
-rw-r--r--sun8i_tcon_top.h1161logplain
-rw-r--r--sun8i_ui_layer.c12358logplain
-rw-r--r--sun8i_ui_layer.h2220logplain
-rw-r--r--sun8i_ui_scaler.c5917logplain
-rw-r--r--sun8i_ui_scaler.h1584logplain
-rw-r--r--sun8i_vi_layer.c17233logplain
-rw-r--r--sun8i_vi_layer.h2421logplain
-rw-r--r--sun8i_vi_scaler.c40648logplain
-rw-r--r--sun8i_vi_scaler.h3291logplain
-rw-r--r--sunxi_engine.h4809logplain
generated by cgit
o@qca.qualcomm.com> 2014-07-22ath10k: prevent endless pci rx loopMichal Kazior1-8/+9 It was possible to enter an endless loop while processing a single pci copy engine pipe. This could effectively render ath10k incapable of responding to any requests. An example case when this could happen is when firmware generates a lot of events, e.g. spectral scan phyerr via WMI. Reported-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-22ath10k: workaround qos nullfunc bugMichal Kazior1-0/+11 Apparently fw/hw generates a corrupted QoS Control Field in Qos NullFunc frames. The only way to workaround this is to downgrade frames to NullFunc. This should be okay since powersave is done by fw/hw and these frames are only used for CQM purposes (e.g. from hostapd to check if station is still connected). This doesn't fix any user visible bug that I know of. It just prevents from sending out funky frames on the air. Reported-by: Janusz Dziedzic <janusz.dziedzic@tieto.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-22ath10k: simplify tx helpersMichal Kazior3-32/+23 It always bugged me how tid is computed and stored in a temporary var before written to the control buffer. It was confusing and it made it difficult to work with tx helpers. While at it rename the qos workaround function as it was misleading - it's not a workaround but preparation for nwifi tx mode. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-21ath10k: prevent some tx flushing failuresMichal Kazior2-0/+13 Firmware could request inspection of some submitted tx requests. Since the callback wasn't implemented it was possible to bleed tx msdu_ids which could translate to tx flushing timeouts. There's nothing ath10k can do to help firmware with tx processing now so just report all tx frames as already inspected to prevent firmware from sending up inspection events and force it to report regular tx completion indications with discard status. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-21ath10k: workaround boot issues with KVM/PCI-passthroughMichal Kazior1-2/+18 Apparently iomap writes that unmask CE irqs aren't propagated properly sometimes. Before failing try to poll for the control response message as it may have been delivered without an interrupt. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-18Merge tag 'for-linville-20140717' of git://github.com/kvalo/athJohn W. Linville9-29/+149 2014-07-15ath10k: sanitize tx ring index access properlyMichal Kazior1-4/+7 The tx ring index was immediately trimmed with a bitmask. This discarded the 0xFFFFFFFF error case (which theoretically can happen when a device is abruptly disconnected) and led to using an invalid tx ring index. This could lead to memory corruption. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-15ath10k: fix bmi exchange tx/rx raceMichal Kazior2-9/+5 It was possible for tx completion not to be processed. In that case an old stack pointer was left on copy engine tx ring. Next bmi exchange would immediately pop it and use complete() on the completion struct there causing corruption. Make sure to wait for both tx and rx completions properly. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-14ath10k: fix unregister deadlock when fw probe failsMichal Kazior1-1/+3 If firmware probing worker failed it called device_release_driver() which synchronously called remove() pci callback. The callback in turn waited for the worker that called it to finish resulting in a deadlock. Waiting for a completion instead of a worker, like some other drivers do, doesn't seem like the best idea either: Syscall Worker probe_fw() rmmod dev_lock() pci->remove() wait_for_completion() complete_all() device_release_driver() dev_lock() [sleep] free(ar) dev_unlock() [resume] There's no guarantee that Worker upon resuming can still access any data/code of the module. Leaving device bound to a driver is not as harmful as deadlocking so remove the call to device_release_driver() while a proper solution is figured out. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> 2014-07-14ath10k: add implementation for configure max amsdu, ampduJanusz Dziedzic4-8/+127 Allow to setup maximum subframes for AMSDU and AMPDU aggregation via debugfs htt_max_amsdu_ampdu file. Eg. echo "2 64" > htt_max_amsdu_ampdu will setup maxim