From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Anholt Subject: Rasperry Pi clock support Date: Thu, 13 Aug 2015 16:05:39 -0700 Message-ID: <1439507142-2965-1-git-send-email-eric@anholt.net> Return-path: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Stephen Warren , Lee Jones , Stephen Boyd , Mike Turquette , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org I'm also avoiding requests to set rate/state when they're a no-op, as apparently no-op changes to pixel clock break the firmware-configured display setup. It *shouldn't* change anything, but I've confirmed that setting the CPU clock works fine, and after a couple of weeks of prodding pixel clock now, I'm at a loss for what's going on with it. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html