LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Eddie James <eajames@linux.vnet.ibm.com> To: linux-kernel@vger.kernel.org Cc: linux-clk@vger.kernel.org, joel@jms.id.au, mturquette@baylibre.com, sboyd@kernel.org, eajames@linux.vnet.ibm.com, mine260309@gmail.com, ryan_chen@aspeedtech.com Subject: [PATCH v2 0/2] clk: aspeed: Fix is_enabled and prevent reset if clock enabled Date: Thu, 8 Mar 2018 14:57:18 -0600 [thread overview] Message-ID: <1520542640-9185-1-git-send-email-eajames@linux.vnet.ibm.com> (raw) Here are two fixes for the Aspeed clock driver. The first fixes the is_enabled clock function to account for different clock gates getting disabled with either 0s or 1s. The second patch addresses some issue found with the LPC controller clock if it gets reset while the clock is enabled, which it is by default. Thanks to Lei Yu for tracking down the LPC issue. Changes since v1: - Fix is_enabled. - Check for enabled in the spinlock in the enable function. - Use is_enabled instead of more code to read the register. Eddie James (2): clk: aspeed: Fix is_enabled for certain clocks clk: aspeed: Prevent reset if clock is enabled drivers/clk/clk-aspeed.c | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) -- 1.8.3.1
next reply other threads:[~2018-03-08 20:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-08 20:57 Eddie James [this message] 2018-03-08 20:57 ` [PATCH v2 1/2] clk: aspeed: Fix is_enabled for certain clocks Eddie James 2018-03-13 5:40 ` Joel Stanley 2018-03-15 18:14 ` Stephen Boyd 2018-03-08 20:57 ` [PATCH v2 2/2] clk: aspeed: Prevent reset if clock is enabled Eddie James 2018-03-09 3:23 ` Lei YU [not found] ` <CAARXrtktSUMBuHUUjqTgrWNZaHVkOC9DUQEr4WKeGNz2z6WVdA@mail.gmail.com> 2018-03-09 5:02 ` Joel Stanley 2018-03-13 5:42 ` Joel Stanley 2018-03-15 18:14 ` Stephen Boyd 2018-03-10 0:41 ` [PATCH v2 0/2] clk: aspeed: Fix is_enabled and prevent reset if clock enabled Stephen Boyd 2018-03-14 19:11 ` Eddie James
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1520542640-9185-1-git-send-email-eajames@linux.vnet.ibm.com \ --to=eajames@linux.vnet.ibm.com \ --cc=joel@jms.id.au \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mine260309@gmail.com \ --cc=mturquette@baylibre.com \ --cc=ryan_chen@aspeedtech.com \ --cc=sboyd@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).