Hi Morimoto-san,
Laurent is away this week, so I've just tried to have a quick look
through this issue in his absence. I'm afraid I don't have a ULCB-H3 to
test locally, so I'm following the code standalone at the moment.
Quoting Geert Uytterhoeven (2021-10-07 08:24:37)
> Hi Morimoto-san,
>
> On Thu, Oct 7, 2021 at 6:55 AM Kuninori Morimoto
> <kuninori.morimoto.gx@xxxxxxxxxxx> wrote:
> > I'm not sure what is related, but I noticed something.
> >
> > This is OK case.
> > DRM failed ? rcar-dw-hdmi was probed
> > ...
> > [ 0.499485] gpio_rcar e6055800.gpio: driving 4 GPIOs
> > [ 0.511240] SuperH (H)SCI(F) driver initialized
> > [ 0.512316] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 123, base_baud = 0) is a scif
> > [ 1.465894] printk: console [ttySC0] enabled
> > => [ 1.476935] rcar-du feb00000.display: failed to initialize DRM/KMS (-6)
This comes from calling rcar_du_modeset_init() ... I'll dig down to see
if there's a clear (single) path leading to -6 / -ENXIO.
> > => [ 1.485684] rcar-dw-hdmi fead0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (DWC HDMI 2.0 TX PHY)
> > => [ 1.496248] rcar-dw-hdmi fead0000.hdmi: registered DesignWare HDMI I2C bus driver
> > [ 1.535173] loop: module loaded
> > ...
> >
> > This is NG case.
> > DAM failed. rcar-dw-hdmi is not probed.
Was something changed to make this happen between this and the above
test?
> >
> > ...
> > [ 0.490286] gpio_rcar e6055800.gpio: driving 4 GPIOs
> > [ 0.501956] SuperH (H)SCI(F) driver initialized
> > [ 0.503027] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 123, base_baud = 0) is a scif
> > [ 1.432046] printk: console [ttySC0] enabled
> > => [ 1.443177] rcar-du feb00000.display: failed to initialize DRM/KMS (-6)
> > [ 1.481426] loop: module loaded
> > ...
>
> Note that in both cases feb00000.display failed to probe first
> Is this an fw_devlink issue, due to HDMI linking to DU in DT?
> Does it work with fw_devlink=permissive of fw_devlink=off?
The DT is all connected up with the ports as I would expect them on
ulcb+kf, but I saw the unanswered question from Geert above. Could you
check that please?
Is there anything else specific to replicating this issue? Is it only on
the ULCB+KF? Or does it occur on Salvator-XS too? (And does it need a
specific kernel config to reproduce?)
--
Kieran
> Gr{oetje,eeting}s,
>
> Geert
>
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
