Received: by 2002:a05:6a10:87d6:0:0:0:0 with SMTP id g22csp728350pxr; Mon, 11 Apr 2022 05:51:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzZj8hk5rbNGAa/Q8ZFh0hYKonBWF+l/nSAHfFP1H7xtKyp+RDOGN8doNAOtvBc1ms/wejW X-Received: by 2002:a05:6402:36d:b0:41d:7a5f:8393 with SMTP id s13-20020a056402036d00b0041d7a5f8393mr5465962edw.277.1649681477577; Mon, 11 Apr 2022 05:51:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649681477; cv=none; d=google.com; s=arc-20160816; b=BNMLwgJamRjkUlkKx14gksb68NKoktDe/RFgLIuh8vTiABvYQwlIkny/BOv6Geo493 mCaczLIgYe12/2MkG4dvmlg3vyY0BlDTi+xV9tKgJijoB9raA0Vm2xOq8h4EgpGfSUlD XiBBbV2VcqAwFS43ejr2fyZwEspMbfRBzYiilo0cYvfQ5PikkuRCrdTK09G/QFUJ+5FJ f4q3Z7geVLNSk9Kl/QC1OMZrBHPgIhWDrJL7oFvvOCKKwR8UY/w1n+ekdKC68IC2eld6 Va89q/LGwTEnPSanuYtKlZuUR0gSHzTPRcbkcqwVEGvWVLrEx/91JHFY9AU0kmgYpu0M RwcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=0eqcGjjm4t9oja+wPiB6DWrW8xnu61nXeB06A5pikcg=; b=dC5EsvHiM4QyeD7caxdlylJDGjq8uIBx18scslnWpX+8Kiv4Z7uvULXoaDGYp6Sy9A QU/ez69cYV6ggYpJvLAOgujvq54Tk+CKaMk+pUu7V26JzGTBFw4RmwyLUPrYgKL/MOdj x7/jEEIpSIN6SWe5v9/ijSfLOXvmWgHSW1bo+YbVkTcII31prM7bsnfZnOzPI/YSI3ZS 0BXJ3x6V7nvUWpPevStTvlE+YDzoAEaoutEHtMc5AqgZhu6DWgzoAlK35sScOSUCwXXY 6oCkHQa1uSsYkeIxtJZHgeNP5uNwgbPl4+ZF87beZ+rL78OAIRbkpVPrAhBgKBbpl2bX 2zoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=UA7ENPCX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o15-20020a170906974f00b006e8035bb2f1si8220798ejy.548.2022.04.11.05.50.52; Mon, 11 Apr 2022 05:51:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=UA7ENPCX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345197AbiDKKQl (ORCPT + 99 others); Mon, 11 Apr 2022 06:16:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345177AbiDKKQf (ORCPT ); Mon, 11 Apr 2022 06:16:35 -0400 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8674B140A6; Mon, 11 Apr 2022 03:14:20 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id e21so5751975wrc.8; Mon, 11 Apr 2022 03:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=0eqcGjjm4t9oja+wPiB6DWrW8xnu61nXeB06A5pikcg=; b=UA7ENPCXOxx/YrFjB425AB1sIrOppxca9ehmwGxQEysxoHrSF4c09veGHwTzbuPSoG lQRKftye/P10K3xLbfsFKxZUVDrggIEqqu8uf16Jg4dRDWTHvkdw6w81APN3QD2ko03S xL3CXZhbiO3AuEzydbNJg1H4OF2UTIQLkMWgWDvxQO9dxmdjsbEUFLMP5JXjhojScnIb 3yHaVV/DqiwpVfeHBvNG7hWiufMdcpdMyWAO5rljP8LiG64P6sD50LOAnyQ8AZb02+G9 HfCbIEkN8BC0YSH9jil1xIBoKD8AV4+dKUxjTi/4DpmfxMmjameAwN9Z7fIJy/fmMvgm QTog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=0eqcGjjm4t9oja+wPiB6DWrW8xnu61nXeB06A5pikcg=; b=2AVkWadwp5XePpVdZz6JQ7fOpoGEHwFlfbS9k0CQ692HE8Bu5fyG90mG0Etugt9h3D CjfaW3+LERZLRJWf+++UH33ilt3zYzehFJuxLFqzhSD1ayQW+t1f54+hDuyODqHQ1SMF Kbv7DNBUIFMOOHdQZYMN53Zf4vWRHNFtwoY+3n10ayIUST/vBBmwbfYh6kW7Bi4l4ybH y9Iid5KCEnVFsQkXzQp+YdE1MEdWXezo6TC8gXnUEPyaVn9/TXLBbFA2LocsZm9+Y+E5 d4QArADShk3gMjsc1UG/AmaGHwvOmYW1p/vIqyjhBz3w+UT4pVTVP7LtAlQgERMWjTkE 17Rg== X-Gm-Message-State: AOAM533HjJ6F8jAuyQOeCwLDC9K5Bg+0ggLenctskppPs+zOfryX0SeN plq2Ppq8qi6kRlAPEq94a/Mah+PnPWpuCQ== X-Received: by 2002:a5d:5986:0:b0:205:87ae:9e18 with SMTP id n6-20020a5d5986000000b0020587ae9e18mr24751709wri.537.1649672059138; Mon, 11 Apr 2022 03:14:19 -0700 (PDT) Received: from localhost (92.40.202.18.threembb.co.uk. [92.40.202.18]) by smtp.gmail.com with ESMTPSA id g16-20020a05600c4ed000b0038ceb0b21b4sm20526369wmq.24.2022.04.11.03.14.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Apr 2022 03:14:18 -0700 (PDT) From: Aidan MacDonald To: paul@crapouillou.net, paulburton@kernel.org, tsbogend@alpha.franken.de, mturquette@baylibre.com, sboyd@kernel.org Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org Subject: [RESEND PATCH 0/3] Clock fixes for Ingenic SoCs Date: Mon, 11 Apr 2022 11:14:38 +0100 Message-Id: <20220411101441.17020-1-aidanmacdonald.0x0@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Resending this series since it appears none of the patches were picked up the first time around. I ran across a problem trying to get Linux running on an Ingenic X1000 SoC: since the memory clock isn't referenced by any driver, it appears unused and gets disabled automatically. After that, the system hangs on any RAM access. There is a hack in board-ingenic.c to forcibly enable the CPU clock, but this is insufficient for the X1000 since the memory clock has its own gate and mux that isn't tied to the CPU. This patch series fixes the bug by adding CLK_IS_CRITICAL flags to important clocks, which seems to be the approach used in many other SoC clock drivers. Original submission: https://lore.kernel.org/linux-mips/20220208010048.211691-1-aidanmacdonald.0x0@gmail.com/ Aidan MacDonald (3): clk: ingenic: Allow specifying common clock flags clk: ingenic: Mark critical clocks in Ingenic SoCs mips: ingenic: Do not manually reference the CPU clock arch/mips/generic/board-ingenic.c | 26 -------------------------- drivers/clk/ingenic/cgu.c | 2 +- drivers/clk/ingenic/cgu.h | 3 +++ drivers/clk/ingenic/jz4725b-cgu.c | 2 ++ drivers/clk/ingenic/jz4740-cgu.c | 2 ++ drivers/clk/ingenic/jz4760-cgu.c | 2 ++ drivers/clk/ingenic/jz4770-cgu.c | 1 + drivers/clk/ingenic/jz4780-cgu.c | 3 +++ drivers/clk/ingenic/x1000-cgu.c | 3 +++ drivers/clk/ingenic/x1830-cgu.c | 3 +++ 10 files changed, 20 insertions(+), 27 deletions(-) -- 2.35.1