Linux IOMMU Development
 help / color / mirror / Atom feed
From: Yong Wu <yong.wu@mediatek.com>
To: chao hao <Chao.Hao@mediatek.com>
Cc: devicetree@vger.kernel.org, FY Yang <fy.yang@mediatek.com>,
	wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 3/7] iommu/mediatek: Set MISC_CTRL register
Date: Sat, 20 Jun 2020 10:03:36 +0800	[thread overview]
Message-ID: <1592618616.3951.12.camel@mhfsdcap03> (raw)
In-Reply-To: <1592480963.12647.5.camel@mbjsdccf07>


[-- Attachment #1.1: Type: text/plain, Size: 2676 bytes --]

Hi Chao,

On Thu, 2020-06-18 at 19:49 +0800, chao hao wrote:

> On Wed, 2020-06-17 at 11:34 +0200, Matthias Brugger wrote:


[snip]


> > >  
> > >  #define REG_MMU_MISC_CTRL			0x048
> > > +#define F_MMU_IN_ORDER_WR_EN			(BIT(1) | BIT(17))
> > > +#define F_MMU_STANDARD_AXI_MODE_BIT		(BIT(3) | BIT(19))
> > > +
> > >  #define REG_MMU_DCM_DIS				0x050
> > >  
> > >  #define REG_MMU_CTRL_REG			0x110
> > > @@ -578,6 +581,14 @@ static int mtk_iommu_hw_init(const struct mtk_iommu_data *data)
> > >  		writel_relaxed(0, data->base + REG_MMU_MISC_CTRL);
> > >  	}
> > >  
> > > +	if (data->plat_data->has_misc_ctrl) {
> > 
> > That's confusing. We renamed the register to misc_ctrl, but it's present in all
> > SoCs. We should find a better name for this flag to describe what the hardware
> > supports.
> > 
> 
> ok, thanks for you advice, I will rename it in next version.
> ex:has_perf_req(has performance requirement)
> 
> 
> > Regards,
> > Matthias
> > 
> > > +		/* For mm_iommu, it can improve performance by the setting */
> > > +		regval = readl_relaxed(data->base + REG_MMU_MISC_CTRL);
> > > +		regval &= ~F_MMU_STANDARD_AXI_MODE_BIT;
> > > +		regval &= ~F_MMU_IN_ORDER_WR_EN;


Note: mt2712 also is MISC_CTRL register, but it don't use this in_order
setting.

As commented in v3. 0x48 is either STANDARD_AXI_MODE or MISC_CTRL
register. No need two flags(reset_axi/has_xx) for it.

something like:

regval = readl_relaxed(data->base + REG_MMU_MISC_CTRL);
if (reset_axi) {
	regval = 0;
} else {   /* MISC_CTRL */
	if (!apu[1])
		regval &= ~F_MMU_STANDARD_AXI_MODE_BIT;
	if (out_order_en)
		regval &= ~F_MMU_IN_ORDER_WR_EN;
}
writel_relaxed(regval, data->base + REG_MMU_MISC_CTRL);


[1] Your current patch doesn't support apu-iommu, thus, add it when
necessary.


> > > +		writel_relaxed(regval, data->base + REG_MMU_MISC_CTRL);
> > > +	}
> > > +
> > >  	if (devm_request_irq(data->dev, data->irq, mtk_iommu_isr, 0,
> > >  			     dev_name(data->dev), (void *)data)) {
> > >  		writel_relaxed(0, data->base + REG_MMU_PT_BASE_ADDR);
> > > diff --git a/drivers/iommu/mtk_iommu.h b/drivers/iommu/mtk_iommu.h
> > > index 1b6ea839b92c..d711ac630037 100644
> > > --- a/drivers/iommu/mtk_iommu.h
> > > +++ b/drivers/iommu/mtk_iommu.h
> > > @@ -40,6 +40,7 @@ struct mtk_iommu_plat_data {
> > >  
> > >  	/* HW will use the EMI clock if there isn't the "bclk". */
> > >  	bool                has_bclk;
> > > +	bool		    has_misc_ctrl;
> > >  	bool                has_vld_pa_rng;
> > >  	bool                reset_axi;
> > >  	unsigned char       larbid_remap[MTK_LARB_NR_MAX];
> > > 
> 
> 



[-- Attachment #1.2: Type: text/html, Size: 4649 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-06-20  2:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  3:00 [PATCH v4 00/07] MT6779 IOMMU SUPPORT Chao Hao
2020-06-17  3:00 ` [PATCH v4 1/7] dt-bindings: mediatek: Add bindings for MT6779 Chao Hao
2020-06-17  3:00 ` [PATCH v4 2/7] iommu/mediatek: Rename the register STANDARD_AXI_MODE(0x48) to MISC_CTRL Chao Hao
2020-06-17  9:04   ` Matthias Brugger
2020-06-17  3:00 ` [PATCH v4 3/7] iommu/mediatek: Set MISC_CTRL register Chao Hao
2020-06-17  9:34   ` Matthias Brugger
2020-06-18 11:49     ` chao hao
2020-06-20  2:03       ` Yong Wu [this message]
2020-06-24  6:39         ` chao hao
2020-06-17  3:00 ` [PATCH v4 4/7] iommu/mediatek: Move inv_sel_reg into the plat_data Chao Hao
2020-06-17  9:09   ` Matthias Brugger
2020-06-17  3:00 ` [PATCH v4 5/7] iommu/mediatek: Add sub_comm id in translation fault Chao Hao
2020-06-17  9:17   ` Matthias Brugger
2020-06-17 11:11     ` Yong Wu
2020-06-18 11:44       ` chao hao
2020-06-17  3:00 ` [PATCH v4 6/7] iommu/mediatek: Add REG_MMU_WR_LEN definition preparing for mt6779 Chao Hao
2020-06-17  9:22   ` Matthias Brugger
2020-06-19 10:56     ` chao hao
2020-06-21 11:01       ` Matthias Brugger
2020-06-24  6:36         ` chao hao
2020-06-17  3:00 ` [PATCH v4 7/7] iommu/mediatek: Add mt6779 basic support Chao Hao
2020-06-17  9:33   ` Matthias Brugger
2020-06-18 11:54     ` chao hao
2020-06-18 16:00       ` Matthias Brugger
2020-06-19 10:50         ` chao hao

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=1592618616.3951.12.camel@mhfsdcap03 \
    --to=yong.wu@mediatek.com \
    --cc=Chao.Hao@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fy.yang@mediatek.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=wsd_upstream@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