From: Viresh Kumar <viresh.kumar@linaro.org>
To: "andrew-sh.cheng" <andrew-sh.cheng@mediatek.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"Nishanth Menon" <nm@ti.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Fan Chen (陳凡)" <fan.chen@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [v5, PATCH 4/5] cpufreq: mediatek: add opp notification for SVS support
Date: Tue, 7 Apr 2020 13:59:28 +0530 [thread overview]
Message-ID: <20200407082928.lancywbqts5yg4ks@vireshk-i7> (raw)
In-Reply-To: <1586242489.10019.1.camel@mtksdaap41>
On 07-04-20, 14:54, andrew-sh.cheng wrote:
> On Mon, 2020-04-06 at 14:59 +0530, Viresh Kumar wrote:
> > On 06-04-20, 17:12, andrew-sh.cheng wrote:
> > > I will use regulator in the locked region.
> > > And regulator will use mutex_lock.
> >
> > Yeah, you can't use spinlock here, use a mutex.
> >
> Hi Viresh,
>
> I am not familiar with read/write lock.
> Do you mean there is another read/write function, which is not
> read_lock()/write_lock(), using mutex but not spinlock?
Heh, I am asking you to use simple mutex here, leave the read/write
lock thing completely as it won't work here.
--
viresh
next prev parent reply other threads:[~2020-04-07 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191126115058epcas1p3caa6da2508caa5fbe71c202834184b15@epcas1p3.samsung.com>
[not found] ` <1574769046-28449-1-git-send-email-andrew-sh.cheng@mediatek.com>
[not found] ` <1574769046-28449-5-git-send-email-andrew-sh.cheng@mediatek.com>
2019-11-27 8:36 ` [v5, PATCH 4/5] cpufreq: mediatek: add opp notification for SVS support Viresh Kumar
[not found] ` <1575874588.13494.4.camel@mtksdaap41>
2019-12-10 6:43 ` Viresh Kumar
[not found] ` <1583827865.4840.1.camel@mtksdaap41>
2020-03-11 6:06 ` Viresh Kumar
[not found] ` <1584084154.7753.3.camel@mtksdaap41>
2020-03-13 9:10 ` Viresh Kumar
[not found] ` <1586164366.5015.6.camel@mtksdaap41>
2020-04-06 9:29 ` Viresh Kumar
[not found] ` <1586242489.10019.1.camel@mtksdaap41>
2020-04-07 8:29 ` Viresh Kumar [this message]
[not found] ` <CGME20191126115134epcas5p43ec69b25093165dad94f95e9213804cb@epcas5p4.samsung.com>
[not found] ` <1574769046-28449-3-git-send-email-andrew-sh.cheng@mediatek.com>
2019-12-17 2:38 ` [v5, PATCH 2/5] dt-bindings: devfreq: add compatible for mt8183 cci devfreq Chanwoo Choi
2019-12-17 7:31 ` [v5, PATCH 0/5] Add cpufreq and cci devfreq for mt8183, and SVS support Chanwoo Choi
[not found] ` <CGME20191126115136epcas5p241f7e64102dab29530370fb5e7f9c6fc@epcas5p2.samsung.com>
[not found] ` <1574769046-28449-4-git-send-email-andrew-sh.cheng@mediatek.com>
2019-12-17 10:08 ` [v5, PATCH 3/5] devfreq: add mediatek cci devfreq Chanwoo Choi
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=20200407082928.lancywbqts5yg4ks@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andrew-sh.cheng@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
/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: link
Be 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).