On Tue, Apr 04, 2017 at 02:15:13PM +0100, John Keeping wrote: > Hi Sean, > > On Sun, 12 Mar 2017 07:06:59 -0500, Rob Herring wrote: > > > On Fri, Mar 03, 2017 at 11:39:45AM +0000, John Keeping wrote: > > > This reset is required in order to fully reset the internal state of the > > > MIPI controller. > > > > > > Signed-off-by: John Keeping <john@xxxxxxxxxxxx> > > > --- > > > On Thu, 2 Mar 2017 13:56:46 -0800, Brian Norris wrote: > > > > On Fri, Feb 24, 2017 at 12:55:06PM +0000, John Keeping wrote: > > > > > + /* > > > > > + * Note that the reset was not defined in the initial device tree, so > > > > > + * we have to be prepared for it not being found. > > > > > + */ > > > > > + apb_rst = devm_reset_control_get(dev, "apb"); > > > > > > > > Did this reset ever get documented in the device tree bindings? I > > > > couldn't find it. Perhaps a follow-up patch is in order? > > > > > > Here's a patch to do that. > > > > > > .../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 7 +++++++ > > > 1 file changed, 7 insertions(+) > > > > Acked-by: Rob Herring <robh@xxxxxxxxxx> > > I don't see this patch in linux-next, so I guess it has fallen through > the cracks somewhere. Since we have Rob's ack, can you pick this via > drm-misc? > Yeah, sorry about that. Applied to misc-next Sean > > Regards, > John -- Sean Paul, Software Engineer, Google / Chromium OS -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
