Jump to content

H3/H5/A64 DRM display driver

jernej

By jernej
in Advanced users - Development

 Share

Recommended Posts

zador.blood.stained

zador.blood.stained

Posted
Posted 
root@orangepiplus2e:~# grep -i ump /var/log/Xorg.0.log
[    13.865] (**) ARMSOC(0): Option "UMP_LOCK" "false"
[    13.865] (II) ARMSOC(0): umplock is Enabled
root@orangepiplus2e:~#

Edit: I checked the code and it's just a bug in printing the value.

zador.blood.stained

zador.blood.stained

Posted
Posted

OK, I'm getting 3 FPS in es2gears (I remember Icenowy reported similar "performance"), but at least no crashes...

 

... and 10 FPS with armsoc and Mesa libraries instead of Mali libraries

 

... and 80 FPS with modesetting X11 driver and Mesa libraries

zador.blood.stained

zador.blood.stained

Posted
Posted
  On 9/10/2017 at 11:20 AM, jernej said:

Mesa means SW rendering?

Expand  

Yes

  Reveal hidden contents

 

Da Alchemist

Da Alchemist

Posted
Posted

Some feedback to HDMI sound: Only pink noise on two channels, silence on all other channels.

This Time my AVR indicates Multichannel PCM and the right number of channels, even there is silence on the channels, so i think this is going in the right direction.

dmesg :http://sprunge.us/AgiB

zador.blood.stained

zador.blood.stained

Posted
Posted

@jernej

 

 - You didn't send your HDMI audio commits for reviews yet, but in any case I believe that the "sound_hdmi" node should not be a parent of the "soc" node, it should be in the root node instead.

- Should the DW CEC driver that will be added in 4.14 work on H3/H5 in theory or will it need some extra HDMI PHY/clock/reset/etc tweaks?

jernej

jernej

Posted
  • Author
Posted
  On 9/28/2017 at 3:27 PM, zador.blood.stained said:

 - You didn't send your HDMI audio commits for reviews yet, but in any case I believe that the "sound_hdmi" node should not be a parent of the "soc" node, it should be in the root node instead.

Expand  

Yeah, I'll fix that. Usually I'm lazy when it comes to DT...

 

  On 9/28/2017 at 3:27 PM, zador.blood.stained said:

- Should the DW CEC driver that will be added in 4.14 work on H3/H5 in theory or will it need some extra HDMI PHY/clock/reset/etc tweaks?

Expand  

I tested it already. Just one line fix was required to make it work, which is already included on my github:

https://github.com/jernejsk/linux-1/commit/5de498da7efd4593976c4e41ca7367ac23352616#diff-0dd6c05e592804ae87e06c218a333a37R318

2
zador.blood.stained

zador.blood.stained

Posted
Posted

Maybe a stupid question, but how to test CEC from userspace? I have /dev/cec0 device node present but cec-client can't find any CEC devices.

I managed to dist-upgrade to Ubuntu Zesty and got cec-ctl and cec-compliance utils from "v4l-utils" package, but they are not very noob-friendly.

jernej

jernej

Posted
  • Author
Posted

The best way to test CEC alongside cec-compliance is this:

1. Run "cec-ctl --playback"

2. Some TVs, including mine, needs signal that device is CEC capable. This could be done with sending viewscreen image on (not sure if this is exact name) message with cec-ctl.

3. Run cec-follower with -m (I think) to view messages from TV

4. Press buttons on your TV remote

 

I don't remeber exact commands, but I can check them when I come back from work if you want.

zador.blood.stained

zador.blood.stained

Posted
Posted

@jernej

Any thoughts? This can be observed on shutdown at least on H5 (Orange Pi Zero+2 H5), nothing is plugged in the HDMI port.

  Reveal hidden contents

 

jernej

jernej

Posted
  • Author
Posted

No, not really. I never observed that, but then again, I test everything exclusively on H3, drivers built in and in 99% cases with cable plugged in at all times . I will check that case.

 

Can you try with drivers built in and with disabled cec & dw hdmi i2s driver?

Igor

Igor

Posted
Posted

With HDMI plugged in is the same. But sometimes it doesn't crash.

jernej

jernej

Posted
  • Author
Posted
  On 11/1/2017 at 9:19 PM, Igor said:

But sometimes it doesn't crash.

Expand  

That would suggest race condition. But since I develop driver with a kernel with only built in drivers, problem may be masked.

 

Driver unloading needs some work anyway, since clocks are not disabled.

zador.blood.stained

zador.blood.stained

Posted
Posted

And according to the debug info it crashes exactly here (drivers/gpu/drm/drm_file.c): 

void drm_lastclose(struct drm_device * dev)
{
	DRM_DEBUG("\n");

	if (dev->driver->lastclose) /* <-- Here */
		dev->driver->lastclose(dev);
	DRM_DEBUG("driver lastclose completed\n");

	if (drm_core_check_feature(dev, DRIVER_LEGACY))
		drm_legacy_dev_reinit(dev);
}

Most likely it's a generic sunxi DRM problem (not related to DE2) when everything is built as modules.

jernej

jernej

Posted
  • Author
Posted
  On 2/12/2018 at 6:46 AM, zador.blood.stained said:

I see the A83t DE2 driver in 4.16-rc1

Expand  

Yeah, DE2 improvements were merged some time ago, but currently I'm waiting on A83t HDMI driver review which is a bit stuck. I hope it will be merged in time for 4.17.

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept