[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9d7c2ff8-c154-b1e8-a7c5-c7f63aa5474f@gmail.com>
Date: Fri, 12 Nov 2021 23:45:36 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Lyude Paul <lyude@...hat.com>,
Thierry Reding <thierry.reding@...il.com>
Cc: Jonathan Hunter <jonathanh@...dia.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
Thomas Graichen <thomas.graichen@...il.com>,
dri-devel@...ts.freedesktop.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/2] drm/tegra: Use drm_dp_aux_register_ddc/chardev()
helpers
12.11.2021 23:26, Lyude Paul пишет:
>> BTW, I see now that DPAUX I2C transfer helper may access
>> aux->drm_device. Hence v1 patch isn't correct anyways.
>
> JFYI - unless I'm misunderstanding you, the aux->drm_dev accesses in the DPAUX
> i2c transfer functions are just from the various drm_{dbg,err,etc.} calls,
> which means that they all should be able to handle aux->drm_dev being NULL. If
> you can set aux->drm_dev before i2c transfers start that's more ideal, since
> otherwise you'll see the AUX device name as "(null)" in the kernel log, but
> any point before device registration should work.
Thanks, I realized that have seen DRM log with a such debug messages
just a day ago.
drm drm: [drm:drm_dp_i2c_do_msg] (null): transaction timed out
So yes, it's indeed not critical.
Powered by blists - more mailing lists