dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tommaso Merciai <tomm.merciai@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
	Peter Robinson <pbrobinson@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH 1/2] drm/i2c/tda998x: Switch to atomic operations
Date: Tue, 11 Jan 2022 21:21:51 +0100	[thread overview]
Message-ID: <20220111202151.GB4503@tom-desktop> (raw)
In-Reply-To: <CAOMZO5Db9WuFTckQ=ngT32Q5EgOFf9_T+duuT1nzemWRTSwoQA@mail.gmail.com>

On Sun, Jan 09, 2022 at 03:44:07PM -0300, Fabio Estevam wrote:
> Hi Tommaso,
> 
> On Sat, Jan 8, 2022 at 4:17 PM Tommaso Merciai <tomm.merciai@gmail.com> wrote:
> 
> > Hi Fabio,
> > If you need some test let me know. Whitch filesystem are you using?
> 
> I am using a rootfs generated by Buildroot.
> 
> The issue I see seems to be hotplug-related.
> 
> cat /sys/class/drm/card1-HDMI-A-1/status
> 
> not always match with the real state of the HDMI cable.
> 
> > In the next days I will investigate on this issue.
> > Let me know.
> 
> Thanks

Hi Fabio,
Got it, I'll try to reproduce the issue on my side and let you know.

Thanks,
Tommaso

  reply	other threads:[~2022-01-12  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31  1:39 [PATCH 1/2] drm/i2c/tda998x: Switch to atomic operations Fabio Estevam
2021-12-31  1:39 ` [PATCH 2/2] drm/i2c/tda998x: Implement atomic_get_input_bus_fmts Fabio Estevam
2022-01-03 11:47   ` Laurent Pinchart
2022-01-03 11:48 ` [PATCH 1/2] drm/i2c/tda998x: Switch to atomic operations Laurent Pinchart
2022-01-03 12:35   ` Fabio Estevam
2022-01-08 19:16     ` Tommaso Merciai
2022-01-09 18:44       ` Fabio Estevam
2022-01-11 20:21         ` Tommaso Merciai [this message]
2022-01-15 23:23           ` Tommaso Merciai
2022-01-16 13:27             ` Fabio Estevam
2022-01-16 16:28               ` Tommaso Merciai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220111202151.GB4503@tom-desktop \
    --to=tomm.merciai@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux@armlinux.org.uk \
    --cc=marex@denx.de \
    --cc=pbrobinson@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox