linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jianjun Wang (王建军)" <Jianjun.Wang@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Youlin Pei (裴友林)" <youlin.pei@mediatek.com>,
	"ot_jieyang@mediatek.com" <ot_jieyang@mediatek.com>,
	"drinkcat@chromium.org" <drinkcat@chromium.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
	"Chuanjia Liu (柳传嘉)" <Chuanjia.Liu@mediatek.com>,
	"Ryan-JH Yu (余家豪)" <Ryan-JH.Yu@mediatek.com>,
	"Qizhong Cheng (程啟忠)" <Qizhong.Cheng@mediatek.com>,
	"kw@linux.com" <kw@linux.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"Ryder Lee (李庚諺)" <Ryder.Lee@mediatek.com>,
	"Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: PCI: mediatek-gen3: Add property to disable dvfsrc voltage request
Date: Thu, 19 Aug 2021 03:40:43 +0000	[thread overview]
Message-ID: <dbae65c4e56a7d445905245be9e3f3d3f3b68d89.camel@mediatek.com> (raw)
In-Reply-To: <20210716173333.GA3632722@robh.at.kernel.org>

On Fri, 2021-07-16 at 11:33 -0600, Rob Herring wrote:
> On Wed, Jun 30, 2021 at 10:49:33AM +0800, Jianjun Wang wrote:
> > Add property to disable dvfsrc voltage request, if this property
> > is presented, we assume that the requested voltage is always
> > higher enough to keep the PCIe controller active.
> > 
> > Signed-off-by: Jianjun Wang <jianjun.wang@mediatek.com>
> > ---
> >  .../devicetree/bindings/pci/mediatek-pcie-gen3.yaml       | 8
> > ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/pci/mediatek-pcie-
> > gen3.yaml b/Documentation/devicetree/bindings/pci/mediatek-pcie-
> > gen3.yaml
> > index e7b1f9892da4..3e26c032cea9 100644
> > --- a/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
> > +++ b/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
> > @@ -96,6 +96,12 @@ properties:
> >    phys:
> >      maxItems: 1
> >  
> > +  disable-dvfsrc-vlt-req:
> > +    description: Disable dvfsrc voltage request, if this property
> > is presented,
> > +      we assume that the requested voltage is always higher enough
> > to keep
> > +      the PCIe controller active.
> > +    type: boolean
> What determines setting this property? Can it be implied by the 
> compatible (which should be SoC specific).
> 
> Is this property specific to PCIe controller? 
> 
> Wouldn't the request be harmless to make the voltage request even if
> not 
> needed?
> 
> I think this probably should be addressed in a common way as part of 
> other QoS, devfreq, etc. requirements for devices.
> 
> Rob

Hi Rob,

Thanks for your review and sorry for the late response.

We have internal discussion and we agree with that this feature should
not be specific to the PCIe controller, we need to find a common way to
do this. 

But as the driver of dvfsrc is not finished the upstream, we don't have
a better solution for now, so we would like to pull back this patch and
will send another patch to disable dvfsrc by default until we find a
common solution to enable it.

Thanks.


  reply	other threads:[~2021-08-19  3:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  2:49 [PATCH v3 0/2] PCI: mediatek-gen3: Add support for disable dvfsrc Jianjun Wang
2021-06-30  2:49 ` [PATCH v3 1/2] dt-bindings: PCI: mediatek-gen3: Add property to disable dvfsrc voltage request Jianjun Wang
2021-06-30  3:40   ` Qizhong Cheng
2021-07-14 11:20     ` Jianjun Wang
2021-07-16 17:33   ` Rob Herring
2021-08-19  3:40     ` Jianjun Wang (王建军) [this message]
2021-06-30  2:49 ` [PATCH v3 2/2] PCI: mediatek-gen3: Add support for " Jianjun Wang
2021-06-30  3:38   ` Qizhong Cheng

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=dbae65c4e56a7d445905245be9e3f3d3f3b68d89.camel@mediatek.com \
    --to=jianjun.wang@mediatek.com \
    --cc=Chuanjia.Liu@mediatek.com \
    --cc=Qizhong.Cheng@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=Ryan-JH.Yu@mediatek.com \
    --cc=Ryder.Lee@mediatek.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=ot_jieyang@mediatek.com \
    --cc=robh@kernel.org \
    --cc=youlin.pei@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).