Hi, On Tue, Jun 9, 2020 at 5:05 AM Harigovindan P <harigovi@xxxxxxxxxxxxxx> wrote: > > ti-sn65dsi86 bridge is enumerated as a runtime device. When > suspend is triggered, PM core adds a refcount on all the > devices and calls device suspend, since usage count is > already incremented, runtime suspend will not be called > and it kept the bridge regulators and gpios ON which resulted > in platform not entering into XO shutdown. The "XO shutdown" concept is a very Qualcomm-specific concept but this bridge chip could be used on any board. ...but I think it's fine to leave it as-is since the meaning is clear enough. > Add changes to force suspend on the runtime device during pm sleep. > > Signed-off-by: Harigovindan P <harigovi@xxxxxxxxxxxxxx> > --- > > Changes in v2: > - Include bridge name in the commit message and > remove dependent patchwork link from the commit > text as bridge is independent of OEM(Stephen Boyd) > > Changes in v3: > - Updating changelog to explain the need for patch > > drivers/gpu/drm/bridge/ti-sn65dsi86.c | 2 ++ > 1 file changed, 2 insertions(+) Note that it's generally considered nice to CC folks who commented on previous versions of the patch since they are folks who are almost certainly interested in it. In this case that would be me and Stephen Boyd. You could also, in theory, carry Stephen's Reviewed-by patch from v1 since you have fixed the subject as he requested and you have now also fixed the commit message to have some details. Reviewed-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
