From: Robin Murphy <robin.murphy@arm.com>
To: Honghui Zhang <honghui.zhang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: joro@8bytes.org, robh@kernel.org, youlin.pei@mediatek.com,
devicetree@vger.kernel.org, kendrick.hsu@mediatek.com,
srv_heupstream@mediatek.com, erin.lo@mediatek.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, yong.wu@mediatek.com,
xinping.qian@mediatek.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] memory: mtk-smi: add larbid init routine
Date: Fri, 28 Jul 2017 10:59:35 +0100 [thread overview]
Message-ID: <a4a00e4b-175c-88d3-d2b4-9f4f1c41a935@arm.com> (raw)
In-Reply-To: <1501204505.29316.9.camel@mtksdaap41>
On 28/07/17 02:15, Honghui Zhang wrote:
> On Thu, 2017-07-27 at 17:42 +0200, Matthias Brugger wrote:
>>
>> On 07/27/2017 04:01 AM, honghui.zhang@mediatek.com wrote:
>>> From: Honghui Zhang <honghui.zhang@mediatek.com>
>>>
>>> In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"),
>>> the larb->larbid was added but not initialized.
>>> Mediatek's gen1 smi need this hardware larbid information to get the
>>> register offset which controls whether enable iommu for this larb.
>>> This patch add the initialize routine for larbid.
>>>
>>> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
>>> ---
>>> drivers/memory/mtk-smi.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c
>>> index 2b798bb4..fe36b3e 100644
>>> --- a/drivers/memory/mtk-smi.c
>>> +++ b/drivers/memory/mtk-smi.c
>>> @@ -240,6 +240,7 @@ static int mtk_smi_larb_probe(struct platform_device *pdev)
>>> struct device *dev = &pdev->dev;
>>> struct device_node *smi_node;
>>> struct platform_device *smi_pdev;
>>> + int err;
>>>
>>> if (!dev->pm_domain)
>>> return -EPROBE_DEFER;
>>> @@ -263,6 +264,14 @@ static int mtk_smi_larb_probe(struct platform_device *pdev)
>>> return PTR_ERR(larb->smi.clk_smi);
>>> larb->smi.dev = dev;
>>>
>>> + err = of_property_read_u32(dev->of_node, "mediatek,larbid",
>>> + &larb->larbid);
>>> + if (err && of_device_is_compatible(dev->of_node,
>>> + "mediatek,mt2701-smi-larb")) {
>>
>> Instead of checking hard-coded bindings you should be able to determine the
>> generation using the smi_pdev.
>> Apart I think it would be better to check for mediatek,larbid only on
>> MTK_SIM_GEN1, or do I miss something?
>>
>
> Hi, Matthias,
> There's a new SoC of mediatek which use MTK_SMI_GEN2 hardware, but it
> has 2 iommus and 2 smi_common, and we are intend to send it's driver
> soon. It need the mediatek,larbid to identify which iommu should be
> binding to.
>
> This patch use the hard-code bindings will make the future work easier.
In that case, might it make sense to add some indicator like "bool
need_larb_id" to struct mtk_smi_larb_gen?
Robin.
>
> thanks.
>> Regards,
>> Matthias
>>
>>> + dev_err(dev, "missing larbid property\n");
>>> + return err;
>>> + }
>>> +
>>> smi_node = of_parse_phandle(dev->of_node, "mediatek,smi", 0);
>>> if (!smi_node)
>>> return -EINVAL;
>>>
>>
>> _______________________________________________
>> Linux-mediatek mailing list
>> Linux-mediatek@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-mediatek
>
>
next prev parent reply other threads:[~2017-07-28 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 2:01 [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver honghui.zhang
2017-07-27 2:01 ` [PATCH 1/3] memory: mtk-smi: add larbid init routine honghui.zhang
2017-07-27 15:42 ` Matthias Brugger
2017-07-28 1:15 ` Honghui Zhang
2017-07-28 9:59 ` Robin Murphy [this message]
2017-07-28 10:38 ` Honghui Zhang
2017-07-27 2:01 ` [PATCH 2/3] dt-bindings: mediatek: add descriptions for larbid honghui.zhang
2017-07-27 2:01 ` [PATCH 3/3] arm: dts: mediatek: add larbid property for larb honghui.zhang
2017-07-27 12:58 ` [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver Joerg Roedel
2017-07-28 0:55 ` Honghui Zhang
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=a4a00e4b-175c-88d3-d2b4-9f4f1c41a935@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=honghui.zhang@mediatek.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kendrick.hsu@mediatek.com \
--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=robh@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=will.deacon@arm.com \
--cc=xinping.qian@mediatek.com \
--cc=yong.wu@mediatek.com \
--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
all inboxes | Powered by JetHome®