From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Anderson Date: Sun, 3 May 2020 13:17:17 -0400 Subject: [PATCH v7 16/22] riscv: Enable cpu clock if it is present In-Reply-To: References: <20200502100628.24809-1-pragnesh.patel@sifive.com> <20200502100628.24809-17-pragnesh.patel@sifive.com> Message-ID: <56fa904b-44bb-cbe4-95b6-989e02b390ec@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 5/3/20 3:12 AM, Pragnesh Patel wrote: > Hi Sean, > >> -----Original Message----- >> From: Sean Anderson >> Sent: 02 May 2020 23:46 >> To: Pragnesh Patel ; u-boot at lists.denx.de >> Cc: atish.patra at wdc.com; palmerdabbelt at google.com; >> bmeng.cn at gmail.com; Paul Walmsley ; >> jagan at amarulasolutions.com; Troy Benjegerdes >> ; anup.patel at wdc.com; Sagar Kadam >> ; rick at andestech.com; Lukas Auer >> >> Subject: Re: [PATCH v7 16/22] riscv: Enable cpu clock if it is present >> >> [External Email] Do not click links or attachments unless you recognize the >> sender and know the content is safe >> >> On 5/2/20 6:06 AM, Pragnesh Patel wrote: >>> The cpu clock is probably already enabled if we are executing code >>> (though we could be executing from a different core). This patch >>> prevents the cpu clock or its parents from being disabled. >>> >>> Signed-off-by: Sean Anderson >> >> If you make substantial changes can you please make a note of it in the >> commit? I did not sign off on *this* code. > > This patch is copied from your v9 series [1] and I made some changes, so the idea is to > give credit to everyone who contributed. That's fine, just please make a note when you make substantial changes. For example, you could write Signed-off-by: Sean Anderson Reviewed-by: Bin Meng [set clock frequency from clock-frequency property] Signed-off-by: Pragnesh Patel so it's more clear what changes have been made since this patch was posted last. --Sean