Thanks a lot Manasi, Ville, Mika, Jani, Lakshmi, for all your time in reviewing
this patch.
Best Regards,
> -Original Message-
> From: dri-devel On Behalf Of Ville
> Syrjälä
> Sent: Tuesday, October 1, 2019 5:31 PM
> To: S, Srinivasan
> Cc: Navare, Manasi D ; intel-
>
On Wed, Sep 25, 2019 at 06:05:42AM +0530, srinivasa...@intel.com wrote:
> From: Srinivasan S
>
> This patch avoids DP MST payload error message in dmesg, as it is trying
> to update the payload to the disconnected DP MST device. After DP MST
> device is disconnected we should not be updating the
Could anyone please review the patch below & let me know if any other ideas
please?
https://patchwork.freedesktop.org/patch/332806/?series=66837=3
Thanks,
> -Original Message-
> From: S, Srinivasan
> Sent: Wednesday, September 25, 2019 8:33 PM
> To: 'Ville Syrjälä'
> Cc: Navare,
Hi Ville,
I have revised the patch from DRM_ERROR to DRM_DEBUG, could you please review?
https://patchwork.freedesktop.org/patch/332806/?series=66837=3
Thanks,
-Original Message-
From: S, Srinivasan
Sent: Thursday, September 19, 2019 7:22 PM
To: 'Ville Syrjälä'
Cc: Navare, Manasi D ;
From: Srinivasan S
This patch avoids DP MST payload error message in dmesg, as it is trying
to update the payload to the disconnected DP MST device. After DP MST
device is disconnected we should not be updating the payload and
hence remove the error.
v2: Removed the connector status check and
Then it's better that, could we change it to DRM_DEBUG_KMS("failed to update
payload %d\n", ret); instead of DRM_ERROR("failed to update payload %d\n",
ret);, without any connector status check, would that be fine?
Regards,
-Original Message-
From: Ville Syrjälä
Sent: Thursday,
On Wed, 18 Sep 2019, Manasi Navare wrote:
> On Wed, Sep 18, 2019 at 07:09:43AM +0530, srinivasa...@intel.com wrote:
>> From: Srinivasan S
>>
>> This patch avoids DP MST payload error message in dmesg, as it is trying
>> to read the payload from the disconnected DP MST device. After the unplug
On Thu, Sep 19, 2019 at 07:23:30AM +, S, Srinivasan wrote:
> Would the following be appropriate fix?
>
> if (connector || connector->base.status ==
> connector_status_connected) {
> ret = drm_dp_update_payload_part1(_dp->mst_mgr);
> if (ret) {
>
Would the following be appropriate fix?
if (connector || connector->base.status == connector_status_connected) {
ret = drm_dp_update_payload_part1(_dp->mst_mgr);
if (ret) {
DRM_ERROR("failed to update payload %d\n", ret);
On Wed, Sep 18, 2019 at 09:11:36PM +0300, Ville Syrjälä wrote:
> On Wed, Sep 18, 2019 at 10:50:39AM -0700, Manasi Navare wrote:
> > On Wed, Sep 18, 2019 at 07:09:43AM +0530, srinivasa...@intel.com wrote:
> > > From: Srinivasan S
> > >
> > > This patch avoids DP MST payload error message in
On Wed, Sep 18, 2019 at 10:50:39AM -0700, Manasi Navare wrote:
> On Wed, Sep 18, 2019 at 07:09:43AM +0530, srinivasa...@intel.com wrote:
> > From: Srinivasan S
> >
> > This patch avoids DP MST payload error message in dmesg, as it is trying
> > to read the payload from the disconnected DP MST
On Wed, Sep 18, 2019 at 07:09:43AM +0530, srinivasa...@intel.com wrote:
> From: Srinivasan S
>
> This patch avoids DP MST payload error message in dmesg, as it is trying
> to read the payload from the disconnected DP MST device. After the unplug
> the connector status is disconnected and we
From: Srinivasan S
This patch avoids DP MST payload error message in dmesg, as it is trying
to read the payload from the disconnected DP MST device. After the unplug
the connector status is disconnected and we should not be looking for the
payload and hence remove the error and throw the
13 matches
Mail list logo
