From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751426AbcFATFk (ORCPT ); Wed, 1 Jun 2016 15:05:40 -0400 Received: from anholt.net ([50.246.234.109]:33897 "EHLO anholt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859AbcFATFj (ORCPT ); Wed, 1 Jun 2016 15:05:39 -0400 From: Eric Anholt To: Michael Turquette , Stephen Boyd Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Stephen Warren , Lee Jones , Eric Anholt Subject: [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Date: Wed, 1 Jun 2016 12:05:32 -0700 Message-Id: <1464807936-532-1-git-send-email-eric@anholt.net> X-Mailer: git-send-email 2.8.0.rc3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I figured out another critical clock (patch 3), but didn't use the CLK_IS_CRITICAL flag since I want to just protect whatever clock happens to be the parent (there are #ifdefs in the firmware indicating that they've experimented with using different clocks as the parent). I think these fixes are all suitable for 4.7. Eric Anholt (4): clk: bcm2835: Mark the VPU clock as critical clk: bcm2835: Mark GPIO clocks enabled at boot as critical clk: bcm2835: Mark the CM SDRAM clock's parent as critical clk: bcm2835: Skip PLLC clocks when deciding on a new clock parent drivers/clk/bcm/clk-bcm2835.c | 63 +++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 61 insertions(+), 2 deletions(-) -- 2.8.0.rc3