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=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 F2A26C433E5 for ; Thu, 25 Mar 2021 09:16:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D4E9261A37 for ; Thu, 25 Mar 2021 09:16:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229913AbhCYJPn (ORCPT ); Thu, 25 Mar 2021 05:15:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39210 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229836AbhCYJPb (ORCPT ); Thu, 25 Mar 2021 05:15:31 -0400 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 25164C06175F for ; Thu, 25 Mar 2021 02:15:31 -0700 (PDT) Received: by mail-lf1-x12b.google.com with SMTP id q29so1460612lfb.4 for ; Thu, 25 Mar 2021 02:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jQSUS0sWefxNSCHEC1KdchHT6ruHmXruWSe0jguDBe4=; b=o57KpS/SVqgB4aa8+prMDX4/0f/sQZGpgBQ8t5UkMLPn5Qn3CNlhP1s7Y7cH4Uk0Yt 5+aTgDlMtpj8VahIttojhrrqsMz/i3HQcvat2q+Z9IlJEJlzy4HXE35AMDJMbCm+Fwag qFIWd7dGn1Dkpw/9bBN+AjxUmjgcMmvYPGwu96VWRx3Jk3pOWVzsmR2MflpGxpsR/+zI 214Nl9OF95l2M2We75WAIh54bzfBMQE0D8P4KtGSM+lKlRhSnbRTreADGhK5Iq5E6anG Hinv7XgoNn7ofg5sU3fNhh/jDogg7F6goe/WLIVqPG5zG3KvOj4ZK71BAHaib2103KXC sl4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jQSUS0sWefxNSCHEC1KdchHT6ruHmXruWSe0jguDBe4=; b=uefN+9dM5gho5647g3RU9HOqhPxsKX0Vc5zCd8PaAKh45HcNwgVrYBM/zzhUuzX2oW Ir2RjMXzaQadJ9X5s8twD81ML3GMDuA4TVkYOOLFyNRgaU8qsRuIHlgM18ZKB92WVPVZ byEsWHPqOm1pCF2GcqEIr8dL5zD5m+6AoBzOOtIrDJ7iYnprUMWH579KJXAmcaokEOO7 rod74lxJpnFcUgu4hhcWlgdVufpDTNz3hqLMCuNbLbWslPHIEqadkB07ROZon+SeptDR 60/5o3iRnvMcZRFsnfM/tVkC89v6uNPb1nXbTJSMaQiTJ5LYPTH/aE17krLO6qpDrF6E VJ0Q== X-Gm-Message-State: AOAM532wKakLyPBwx6pqndXAK1nvgyVgAEDRw8zwngTz/Y/A8gMJiYXK MxnHMDwyKEZfQwhVWevoP+ZPVCd25HIltkBA/XlqqQ== X-Google-Smtp-Source: ABdhPJwItH2xIo9/hQ0G/Dsu3MfocBFrbbbYJg+8rqc4pz2dbpv/HCAoF4I48/Ib6niSpMgouHHNNiCfW6MgVKURop4= X-Received: by 2002:a19:548:: with SMTP id 69mr4426509lff.465.1616663729558; Thu, 25 Mar 2021 02:15:29 -0700 (PDT) MIME-Version: 1.0 References: <20210321033150.15380-1-zhiyong.tao@mediatek.com> <20210321033150.15380-2-zhiyong.tao@mediatek.com> In-Reply-To: <20210321033150.15380-2-zhiyong.tao@mediatek.com> From: Linus Walleij Date: Thu, 25 Mar 2021 10:15:18 +0100 Message-ID: Subject: Re: [PATCH] pinctrl: add lock in mtk_rmw function. To: Zhiyong Tao Cc: Rob Herring , Mark Rutland , Matthias Brugger , Sean Wang , srv_heupstream@mediatek.com, hui.liu@mediatek.com, huang eddie , jg_poxu@mediatek.com, Biao Huang , Hongzhou Yang , Erin Lo , Sean Wang , seiya.wang@mediatek.com, sj.huang@mediatek.com, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Linux ARM , "moderated list:ARM/Mediatek SoC support" , "open list:GPIO SUBSYSTEM" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Sun, Mar 21, 2021 at 4:32 AM Zhiyong Tao wrote: > When multiple threads operate on the same register resource > which include multiple pin, It will make the register resource > wrong to control. So we add lock to avoid the case. > > Signed-off-by: Zhiyong Tao Patch applied! Yours, Linus Walleij