[PATCH 1/2] dt-bindings: Add URT UMSH-8596MD-xT panel bindings
On Sat, Feb 13, 2016 at 10:50:24PM +0100, Maciej S. Szmigiero wrote: > Add DT bindings for United Radiant Technology > UMSH-8596MD-xT 7.0" WVGA TFT LCD panels. > > Signed-off-by: Maciej S. Szmigiero > --- > This replaces "of: add URT UMSH-8596MD-xT panel DT bindings" > submission. > > .../bindings/display/panel/urt,umsh-8596md.txt | 16 > > 1 file changed, 16 insertions(+) > create mode 100644 > Documentation/devicetree/bindings/display/panel/urt,umsh-8596md.txt Acked-by: Rob Herring
[PATCH v2 13/13] dt-bindings: msm/hdmi: Add HDMI PHY bindings
On Mon, Feb 15, 2016 at 12:23:26PM +0530, Archit Taneja wrote:
> Add HDMI PHY bindings. Update the example to use HDMI PHY.
>
> Add a missing power-domains property in the HDMI core bindings.
>
> Cc: devicetree at vger.kernel.org
> Cc: Rob Herring
>
> Signed-off-by: Archit Taneja
> ---
> .../devicetree/bindings/display/msm/hdmi.txt | 39
> +-
> 1 file changed, 38 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/hdmi.txt
> b/Documentation/devicetree/bindings/display/msm/hdmi.txt
> index 379ee2e..4d71910 100644
> --- a/Documentation/devicetree/bindings/display/msm/hdmi.txt
> +++ b/Documentation/devicetree/bindings/display/msm/hdmi.txt
> @@ -11,6 +11,7 @@ Required properties:
> - reg: Physical base address and length of the controller's registers
> - reg-names: "core_physical"
> - interrupts: The interrupt signal from the hdmi block.
> +- power-domains: Should be <&mmcc MDSS_GDSC>.
> - clocks: device clocks
>See ../clocks/clock-bindings.txt for details.
> - qcom,hdmi-tx-ddc-clk-gpio: ddc clk pin
> @@ -18,6 +19,7 @@ Required properties:
> - qcom,hdmi-tx-hpd-gpio: hpd pin
> - core-vdda-supply: phandle to supply regulator
> - hdmi-mux-supply: phandle to mux regulator
> +- qcom,hdmi-phy: phandle to HDMI PHY device node
Why not use the generic phy binding?
>
> Optional properties:
> - qcom,hdmi-tx-mux-en-gpio: hdmi mux enable pin
> @@ -27,6 +29,27 @@ Optional properties:
> - pinctrl-0: the default pinctrl state (active)
> - pinctrl-1: the "sleep" pinctrl state
>
> +HDMI PHY:
> +Required properties:
> +- compatible: Could be the following
> + * "qcom,hdmi-phy-8x60"
> + * "qcom,hdmi-phy-8960"
> + * "qcom,hdmi-phy-8x74"
No wildcards please. Where's 8994?
> + * "qcom,hdmi-phy-8996"
> +- reg: Physical base address and length of the registers of the PHY sub
> blocks.
> +- reg-names: The names of register regions. The following regions are
> required:
> + * "hdmi_pll"
> + * "hdmi_phy"
> + For HDMI PHY on msm8996, these additional register regions are required:
> +* "hdmi_tx_l0"
> +* "hdmi_tx_l1"
> +* "hdmi_tx_l3"
> +* "hdmi_tx_l4"
> +- power-domains: Should be <&mmcc MDSS_GDSC>.
> +- clocks: device clocks
> + See Documentation/devicetree/bindings/clocks/clock-bindings.txt for
> details.
> +- core-vdda-supply: phandle to vdda regulator device node
> +
> Example:
>
> / {
> @@ -35,7 +58,7 @@ Example:
> hdmi: qcom,hdmi-tx-8960 at 4a0 {
Node names should be generic, so just "hdmi".
> compatible = "qcom,hdmi-tx-8960";
> reg-names = "core_physical";
> - reg = <0x04a0 0x1000>;
> + reg = <0x04a0 0x2f0>;
> interrupts = ;
> power-domains = <&mmcc MDSS_GDSC>;
> clock-names =
> @@ -54,5 +77,19 @@ Example:
> pinctrl-names = "default", "sleep";
> pinctrl-0 = <&hpd_active &ddc_active &cec_active>;
> pinctrl-1 = <&hpd_suspend &ddc_suspend &cec_suspend>;
> +
> + qcom,hdmi-phy = <&hdmi_phy>;
> + };
> +
> + hdmi_phy: qcom,hdmi-phy-8960 at 4a00400 {
ditto. phy at ...
> + compatible = "qcom,hdmi-phy-8960";
> + reg-names = "hdmi_phy",
> + "hdmi_pll";
> + reg = <0x4a00400 0x60>,
> + <0x4a00500 0x100>;
> + power-domains = <&mmcc MDSS_GDSC>;
> + clock-names = "slave_iface_clk";
> + clocks = <&mmcc HDMI_S_AHB_CLK>;
> + core-vdda-supply = <&pm8921_hdmi_mvs>;
> };
> };
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation
>
[PATCH 6/6] drm/msm/dsi: Parse DSI lanes via DT
On Mon, Feb 15, 2016 at 06:30:59PM +0530, Archit Taneja wrote: > The DSI driver is currently unaware of how the DSI clock and data pins > are mapped to the logical lanes provided by the DSI controller. > > Use the generic 'lanes' DT binding provided for DSI lanes (used for DSI > in bindings/display/ti/ti,omap4-dss.txt) to get the desired mapping. > > The MSM DSI controller is restricted in terms of what all mappings > it can support. The lane polarity is fixed for all the lanes, the clock > lanes are fixed, and the data lanes can be swapped among each other only > for a few combinations. Apply these restrictions when we parse the DT > data. > > Cc: devicetree at vger.kernel.org > Cc: Rob Herring > Cc: Tomi Valkeinen > > Signed-off-by: Archit Taneja > --- > .../devicetree/bindings/display/msm/dsi.txt| 26 +++- > drivers/gpu/drm/msm/dsi/dsi_host.c | 146 > ++--- > 2 files changed, 149 insertions(+), 23 deletions(-) > > diff --git a/Documentation/devicetree/bindings/display/msm/dsi.txt > b/Documentation/devicetree/bindings/display/msm/dsi.txt > index e7423be..f0d8b6f 100644 > --- a/Documentation/devicetree/bindings/display/msm/dsi.txt > +++ b/Documentation/devicetree/bindings/display/msm/dsi.txt > @@ -44,9 +44,28 @@ Optional properties: > - pinctrl-names: the pin control state names; should contain "default" > - pinctrl-0: the default pinctrl state (active) > - pinctrl-n: the "sleep" pinctrl state > -- port: DSI controller output port. This contains one endpoint subnode, with > its > - remote-endpoint set to the phandle of the connected panel's endpoint. > - See Documentation/devicetree/bindings/graph.txt for device graph info. > +- port: DSI controller output port, containing one endpoint subnode. > + > + DSI Endpoint properties: > + - remote-endpoint: set to phandle of the connected panel's endpoint. > +See Documentation/devicetree/bindings/graph.txt for device graph info. > + - lanes: list of pin numbers for the DSI lanes: CLKp, CLKn, DATA0p, DATA0n, > +DATA1p, DATA1n, ... > +This provides a physical to logical mapping of the DSI lanes. The CLKp > and > +CLKn pins have to be mapped to pins 0 and 1. For data lanes, there are > only Then why describe the clk pins? > +a limited number of physical to logical mappings possible: > + > + "0123": Logic 0->Phys 0; Logic 1->Phys 1; Logic 2->Phys 2; Logic > 3->Phys 3; > + "3012": Logic 3->Phys 0; Logic 0->Phys 1; Logic 1->Phys 2; Logic > 2->Phys 3; > + "2301": Logic 2->Phys 0; Logic 3->Phys 1; Logic 0->Phys 2; Logic > 1->Phys 3; > + "1230": Logic 1->Phys 0; Logic 2->Phys 1; Logic 3->Phys 2; Logic > 0->Phys 3; > + "0321": Logic 0->Phys 0; Logic 3->Phys 1; Logic 2->Phys 2; Logic > 1->Phys 3; > + "1032": Logic 1->Phys 0; Logic 0->Phys 1; Logic 3->Phys 2; Logic > 2->Phys 3; > + "2103": Logic 2->Phys 0; Logic 1->Phys 1; Logic 0->Phys 2; Logic > 3->Phys 3; > + "3210": Logic 3->Phys 0; Logic 2->Phys 1; Logic 1->Phys 2; Logic > 0->Phys 3; > + > + Here, a "3012" mapping will be represented by: > + lanes = <0 1 8 9 2 3 4 5 6 7>; I'm lost here. What does 8 mean for example. The index represents? Rob
[Bug 91960] [i915] kernel warning hsw_unclaimed_reg_debug intel_uncore.c:619
45:33 donald kernel: [ 5693.502918] [] ? do_vfs_ioctl+0x2d6/0x4b0 Feb 18 23:45:33 donald kernel: [ 5693.502919] [] ? SyS_ioctl+0x76/0x90 Feb 18 23:45:33 donald kernel: [ 5693.502921] [] ? system_call_fast_compare_end+0xc/0x6b Feb 18 23:45:33 donald kernel: [ 5693.502922] ---[ end trace 62eab8e72842e940 ]--- Feb 21 13:36:50 donald kernel: [ 3314.585209] [ cut here ] Feb 21 13:36:50 donald kernel: [ 3314.585231] WARNING: CPU: 0 PID: 11491 at /build/linux-he22YB/linux-4.4.2/drivers/gpu/drm/i915/intel_uncore.c:619 hsw_unclaimed_reg_de bug+0x65/0x80 [i915]() Feb 21 13:36:50 donald kernel: [ 3314.585233] Unclaimed register detected after reading register 0x22380 Feb 21 13:36:50 donald kernel: [ 3314.585235] Modules linked in: usb_serial_simple usbserial ctr ccm rfcomm joydev bnep intel_rapl iosf_mbi iTCO_wdt iTCO_vendor_support arc4 x86_pkg_temp_thermal intel_powerclamp coretemp kvm iwlmvm irqbypass mac80211 psmouse serio_raw pcspkr intel_pch_thermal i2c_i801 sg lpc_ich uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iwlwifi videobuf2_core v4l2_common rtsx_pci_ms btusb btrtl cfg80211 memstick videodev btbcm btintel media snd_hda_codec_hdmi bluetooth cdc_mbim cdc_wdm shpchp cdc_ncm snd_hda_codec_realtek usbnet snd_hda_codec_generic mii cdc_acm snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm mei_me snd_timer mei thinkpad_acpi nvram snd soundcore rfkill battery ac evdev tpm_tis tpm processor acpi_call(O) parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel rtsx_pci_sdmmc mmc_core jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng aesni_intel ahci libahci aes_x86_64 lrw gf128mul glue_helper ablk_helper ehci_pci cryptd ehci_hcd e1000e ptp i915 pps_core libata i2c_algo_bit xhci_pci drm_kms_helper scsi_mod xhci_hcd rtsx_pci mfd_core usbcore drm usb_common thermal wmi fjes video button Feb 21 13:36:50 donald kernel: [ 3314.585302] CPU: 0 PID: 11491 Comm: chromium Tainted: GW O4.4.0-1-amd64 #1 Debian 4.4.2-2 Feb 21 13:36:50 donald kernel: [ 3314.585304] Hardware name: LENOVO 20BX000TGM/20BX000TGM, BIOS JBET55WW (1.20 ) 12/23/2015 Feb 21 13:36:50 donald kernel: [ 3314.585305] 06381811 812e7679 88035dc03d70 Feb 21 13:36:50 donald kernel: [ 3314.585307] 8107632d 880349e6 88035dc03dc8 880349e60080 Feb 21 13:36:50 donald kernel: [ 3314.585310] 0001 0046 810763bc a030f4e8 Feb 21 13:36:50 donald kernel: [ 3314.585312] Call Trace: Feb 21 13:36:50 donald kernel: [ 3314.585313][] ? dump_stack+0x40/0x57 Feb 21 13:36:50 donald kernel: [ 3314.585321] [] ? warn_slowpath_common+0x7d/0xb0 Feb 21 13:36:50 donald kernel: [ 3314.585323] [] ? warn_slowpath_fmt+0x5c/0x80 Feb 21 13:36:50 donald kernel: [ 3314.585336] [] ? hsw_unclaimed_reg_debug+0x65/0x80 [i915] Feb 21 13:36:50 donald kernel: [ 3314.585348] [] ? gen6_read32+0xc8/0x180 [i915] Feb 21 13:36:50 donald kernel: [ 3314.585359] [] ? intel_lrc_irq_handler+0xc4/0x230 [i915] Feb 21 13:36:50 donald kernel: [ 3314.585367] [] ? gen8_gt_irq_handler+0x20c/0x240 [i915] Feb 21 13:36:50 donald kernel: [ 3314.585374] [] ? gen8_irq_handler+0x9d/0x6f0 [i915] Feb 21 13:36:50 donald kernel: [ 3314.585377] [] ? handle_irq_event_percpu+0x6d/0x170 Feb 21 13:36:50 donald kernel: [ 3314.585379] [] ? handle_irq_event+0x39/0x60 Feb 21 13:36:50 donald kernel: [ 3314.585381] [] ? handle_edge_irq+0x7b/0x140 Feb 21 13:36:50 donald kernel: [ 3314.585384] [] ? handle_irq+0x19/0x30 Feb 21 13:36:50 donald kernel: [ 3314.585387] [] ? do_IRQ+0x46/0xd0 Feb 21 13:36:50 donald kernel: [ 3314.585389] [] ? common_interrupt+0x82/0x82 Feb 21 13:36:50 donald kernel: [ 3314.585390] Feb 21 13:36:50 donald kernel: [ 3314.585391] ---[ end trace d0ef44d32ab0c1be ]--- -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160221/4d8d73b2/attachment-0001.html>
[Bug 35998] RS600: Texture alignment issues under Gnome Shell
https://bugs.freedesktop.org/show_bug.cgi?id=35998 --- Comment #36 from Andrew Randrianasulu --- Created attachment 121870 --> https://bugs.freedesktop.org/attachment.cgi?id=121870&action=edit mmiotrace from Catalyst 9.3 kernel 2.6.27.27 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160221/58da1ffe/attachment-0001.html>
[Bug 112781] New: radeon: f95429e "only init fbdev if we have connectors" breaks suspend on Clevo P170EM laptop
https://bugzilla.kernel.org/show_bug.cgi?id=112781 Bug ID: 112781 Summary: radeon: f95429e "only init fbdev if we have connectors" breaks suspend on Clevo P170EM laptop Product: Drivers Version: 2.5 Kernel Version: 4.5-rc2 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri at kernel-bugs.osdl.org Reporter: haagch.christoph at googlemail.com Regression: No Created attachment 204201 --> https://bugzilla.kernel.org/attachment.cgi?id=204201&action=edit dmesg On a Clevo P170EM with these GPUs: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) With rc2 suspend stopped working. It starts to suspend, turns off the display, etc., but then it fails to actually enter the suspend state. The power stays on and after a while the radeon GPU fan starts spinning up. There's nothing in the logs relating to the problem I could find. I bisected to f95429eccc570dc45d589c327bfcfddcdc3e8228 and confirmed it with latest linux git (4.5-rc5) with this commit reverted - suspend works. Attached is a dmesg with this setup including one successful suspend and wake up. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 94231] Problems compiling libdrm since glibc 2.23
https://bugs.freedesktop.org/show_bug.cgi?id=94231 Bug ID: 94231 Summary: Problems compiling libdrm since glibc 2.23 Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: libdrm Assignee: dri-devel at lists.freedesktop.org Reporter: mike at fireburn.co.uk Created attachment 121865 --> https://bugs.freedesktop.org/attachment.cgi?id=121865&action=edit Patch to include sys/sysmacros.h in libdrm Get errors about mkdev, major and minor not being defined when compiling libdrm after upgrading glibc to 2.23 Including sys/sysmacros.h fixes it for me -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160221/34c88cab/attachment.html>
