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 arcpgu_drm_connector * con =
container_of(connector, struct arcpgu_drm_connector, connector);
slave = con->encoder_slave;
if(slave == NULL) {
dev_err(connector->dev->dev,
"connector_get_modes: cannot find slave encoder for connector\n");
return 0;
}
sfuncs = slave->slave_funcs;
if(sfuncs->get_modes == NULL){
return 0;
}
return sfuncs->get_modes(&slave->base,connector);
}
On 31-12-2015 02:19, Xinliang Liu wrote:
On 31 December 2015 at 02:46, Carlos Palminha
<CARLOS.PALMINHA@xxxxxxxxxxxx <mailto:CARLOS.PALMINHA@xxxxxxxxxxxx>> 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":
https://www.youtube.com/watch?v=Ja8fM7rTae4
After initiliazing all kms, crtc, encoder, i2c, connector functions
and structures i'm calling drm_fbdev_cma_init to create a fbdev.
When booting i'm getting an error message saying "No connectors
reported connected with modes", but the driver init is ok and i can
find the /dev/dri/* and /dev/fb0 devices.
Any clue what i might be missing during the driver load?
I think you should check on the 'get_modes' call back of adv7511
driver. (Or, if possible show us the code.)
Best,
-xinliang
Thanks...
Regards,
C.Palminha
--- boot log snippet ---
[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: switching to colour frame buffer device 128x48
drm-arcpgu e0017000.pgu: fb0: frame buffer device
[drm] Initialized drm-arcpgu 1.0.0 20151127 on minor 0
--- boot log snippet ---
--
To unsubscribe from this list: send the line "unsubscribe
linux-fbdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
<mailto:majordomo@xxxxxxxxxxxxxxx>
More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
