From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grygorii Strashko Subject: Common clock framework API vs RT patchset Date: Tue, 4 Aug 2015 15:00:47 +0300 Message-ID: <55C0A96F.80307@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: "Menon, Nishanth" , Felipe Balbi , Sekhar Nori To: Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:33615 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933719AbbHDMAv (ORCPT ); Tue, 4 Aug 2015 08:00:51 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id t74C0om2030322 for ; Tue, 4 Aug 2015 07:00:50 -0500 Received: from DFLE72.ent.ti.com (dfle72.ent.ti.com [128.247.5.109]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id t74C0oZH019607 for ; Tue, 4 Aug 2015 07:00:50 -0500 Sender: linux-rt-users-owner@vger.kernel.org List-ID: Hi All, I'd very appreciated if someone can clarify one point for me. Is allowed/expected/prohibited to use CLK API like clk_enable/disable in atomic context now on RT-Kernel (HW IRQ or under RAW spinlocks)? How safe is it to allow CLK API to be preemptive? -- regards, -grygorii