Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

On Thu, Jan 21, 2016 at 7:09 PM, Carlos Palminha wrote: > i made some progress in identifying the issue... > When my driver calls drm_fb_helper_initial_config it seems DRM blocks waiting > for register_framebuffer to return. > The sequence is >

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

Hey, On 22 January 2016 at 07:41, Daniel Vetter wrote: > On Thu, Jan 21, 2016 at 7:09 PM, Carlos Palminha > wrote: >> i made some progress in identifying the issue... >> When my driver calls drm_fb_helper_initial_config it seems DRM blocks >> waiting for register_framebuffer to return. >> The

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

i made some progress in identifying the issue... When my driver calls drm_fb_helper_initial_config it seems DRM blocks waiting for register_framebuffer to return. The sequence is drm_fb_helper_initial_config->drm_fb_helper_single_fb_probe->register_framebuffer. Its strange because

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

On 20 January 2016 at 00:52, Carlos Palminha wrote: > when i boot the kernel and connect the HDMI cable after booting i can > retrieve 4 modes... :) > > if i boot linux with the HDMI cable inserted the kernel hangs. What's the hang kernel log. Is it a oops? > Possible relation with HPD? Yes,

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

when i boot the kernel and connect the HDMI cable after booting i can retrieve 4 modes... :) if i boot linux with the HDMI cable inserted the kernel hangs. Possible relation with HPD? Regards, C.Palminha # modetest -M drm-arcpgu -c Connectors: id encoder status typesize (mm)

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

Hi Xiang, Its returning 0 modes... :( Regards, C.Palminha # modetest -M drm-arcpgu -c Connectors: id encoder status typesize (mm) modes encoders 21 0 disconnectedHDMI-A 0x0 0 20 props: 1 EDID: flags: immutable

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

On 18 January 2016 at 22:45, Carlos Palminha wrote: > I'm also getting a message from DRM saying can't find any crtc or > sizes...i'm really missing something here. > :( > > -- log -- > [drm] Initialized drm 1.1.0 20060810 > drm-arcpgu e0017000.pgu: No connectors reported connected with modes >

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

I'm also getting a message from DRM saying can't find any crtc or sizes...i'm really missing something here. :( -- log -- [drm] Initialized drm 1.1.0 20060810 drm-arcpgu e0017000.pgu: No connectors reported connected with modes [drm] Cannot find any crtc or sizes - going 1024x768 Console:

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

Hi Xinliang, My get_modes seems to be implemented as the rcar driver... Probably still missing some init step? Regards, C.Palminha static int arcpgu_drm_connector_get_modes(struct drm_connector *connector) { struct drm_encoder_slave *slave; const struct drm_encoder_slave_funcs *sfuncs; struct

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

On 31 December 2015 at 02:46, Carlos Palminha wrote: > Hi guys, > > I'm writing a DRM driver for a framebuffer embedded hardware that uses an > i2c encoder (adv7511), following the basic steps suggested by Laurent in > "anatomy of an embedded KMS driver": >

Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?

Hi guys, I'm writing a DRM driver for a framebuffer embedded hardware that uses an i2c encoder (adv7511), following the basic steps suggested by Laurent in "anatomy of an embedded KMS driver": https://www.youtube.com/watch?v=Ja8fM7rTae4 After initiliazing all kms, crtc, encoder, i2c,