From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A3DEC76186 for ; Tue, 23 Jul 2019 18:24:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4FE7522AEC for ; Tue, 23 Jul 2019 18:24:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="FV39AKdM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391477AbfGWSYw (ORCPT ); Tue, 23 Jul 2019 14:24:52 -0400 Received: from mail-pg1-f196.google.com ([209.85.215.196]:38438 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391474AbfGWSYw (ORCPT ); Tue, 23 Jul 2019 14:24:52 -0400 Received: by mail-pg1-f196.google.com with SMTP id f5so11002778pgu.5 for ; Tue, 23 Jul 2019 11:24:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=message-id:mime-version:content-transfer-encoding:in-reply-to :references:subject:to:cc:from:user-agent:date; bh=b41n3LREvvCVOT99upf2mTScwjCvonjOKLeOr7b3C5o=; b=FV39AKdMDQeD6YqtoKQSMhCbjgrTyHJN60X0SWmNCD+O9p2bX6C8qYJz0eINu0Vkyf LAbFt2BoaV/5c012dA0FE9DnPmAfbtAoMuMuWTdOwtIgpVHXOPYq/wXTmyg0mmReH1eo bP8CKJ5kluT1kIqJojulM3Lhe452qac63uGtA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version :content-transfer-encoding:in-reply-to:references:subject:to:cc:from :user-agent:date; bh=b41n3LREvvCVOT99upf2mTScwjCvonjOKLeOr7b3C5o=; b=XPxbbw5iXhiArt75OLNauvdgFXm1BIDEbVbbO9zG0HZ6ea2RWwj5vt1BX6YH7EQ87a CGYk3wKrjsXNwSFZYXWOI77FbQgTMwjetJJM+ExW44qNj8noqCHXzp7DOZtYEjiGRhSo MU0F0q/ZsXpwbSG3R2OQl19xkaoX6AiIqKL9RyCG+e6u1on5FUG+p0i4igMxsDJGyLqb ZELepzIoNmPqXceYQRhGJoIC8TAq6FZCzNT+qVElk+W+TUIA3w7rGUtLH3IEnZRt1LCd 9FGWmx7zktfB40Dkdr623mfjz/smwE0HRVI0vufE2JTaGsB6NRioT9YQ2W3Y4yXMjBNP 80Cg== X-Gm-Message-State: APjAAAX1fEQvodmr84Jorbys3zDY5u37O8XT7mukhSwVf2CkihXbd/n4 mXrlxq0NM14Kd3+zOvvdYXYIFA== X-Google-Smtp-Source: APXvYqx0i7nBRik0fKx4AbxAnDtKCTytjeuS/7WcJwq1Evpncx6GnzRR1koiuEsmKqC3CiPSEsktfA== X-Received: by 2002:a17:90a:4f0e:: with SMTP id p14mr80829741pjh.40.1563906291568; Tue, 23 Jul 2019 11:24:51 -0700 (PDT) Received: from chromium.org ([2620:15c:202:1:fa53:7765:582b:82b9]) by smtp.gmail.com with ESMTPSA id t29sm53263348pfq.156.2019.07.23.11.24.50 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 23 Jul 2019 11:24:51 -0700 (PDT) Message-ID: <5d3750f3.1c69fb81.923dc.874d@mx.google.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20190722215340.3071-3-ilina@codeaurora.org> References: <20190722215340.3071-1-ilina@codeaurora.org> <20190722215340.3071-3-ilina@codeaurora.org> Subject: Re: [PATCH V2 3/4] drivers: qcom: rpmh: switch over from spinlock irq variants To: Lina Iyer , agross@kernel.org, bjorn.andersson@linaro.org Cc: linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, rnayak@codeaurora.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, dianders@chromium.org, mkshah@codeaurora.org, "Raju P.L.S.S.S.N" , Lina Iyer From: Stephen Boyd User-Agent: alot/0.8.1 Date: Tue, 23 Jul 2019 11:24:50 -0700 Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Quoting Lina Iyer (2019-07-22 14:53:39) > From: "Raju P.L.S.S.S.N" >=20 > Switch over from using _irqsave/_irqrestore variants since we no longer > race with a lock from the interrupt handler. While we are at it, rename > the cache_lock to just lock to allow use of the lock to synchronize > controller access. Is there a reason why it can't be a mutex now? >=20 > Signed-off-by: Raju P.L.S.S.S.N > Signed-off-by: Lina Iyer