From: <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <baolu.lu@linux.intel.com>, <joro@8bytes.org>, <will@kernel.org>,
<robh+dt@kernel.org>, <jgg@nvidia.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<iommu@lists.linux-foundation.org>,
<yuji2.ishikawa@toshiba.co.jp>,
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 1/3] iommu: Add Visconti5 IOMMU driver
Date: Mon, 20 Jun 2022 02:15:46 +0000 [thread overview]
Message-ID: <TYWPR01MB9420432737626348118C515F92B09@TYWPR01MB9420.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <63369db0-cf7f-aa53-bf9f-de2b0b2289ac@linux.intel.com>
Hi,
> -----Original Message-----
> From: Baolu Lu <baolu.lu@linux.intel.com>
> Sent: Wednesday, May 25, 2022 3:27 PM
> To: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; Joerg Roedel <joro@8bytes.org>; Will
> Deacon <will@kernel.org>; Rob Herring <robh+dt@kernel.org>; Jason
> Gunthorpe <jgg@nvidia.com>
> Cc: baolu.lu@linux.intel.com; devicetree@vger.kernel.org;
> linux-kernel@vger.kernel.org; iommu@lists.linux-foundation.org; ishikawa
> yuji(石川 悠司 ○RDC□AITC○EA開)
> <yuji2.ishikawa@toshiba.co.jp>; linux-arm-kernel@lists.infradead.org
> Subject: Re: [PATCH 1/3] iommu: Add Visconti5 IOMMU driver
>
> On 2022/5/25 09:31, Nobuhiro Iwamatsu wrote:
> > +static const struct iommu_ops visconti_atu_ops = {
> > + .domain_alloc = visconti_atu_domain_alloc,
> > + .probe_device = visconti_atu_probe_device,
> > + .release_device = visconti_atu_release_device,
> > + .device_group = generic_device_group,
> > + .of_xlate = visconti_atu_of_xlate,
> > + .pgsize_bitmap = ATU_IOMMU_PGSIZE_BITMAP,
> > + .default_domain_ops = &(const struct iommu_domain_ops) {
> > + .attach_dev = visconti_atu_attach_device,
> > + .detach_dev = visconti_atu_detach_device,
>
> The detach_dev callback is about to be deprecated. The new drivers should
> implement the default domain and blocking domain instead.
I see. I will update this with next version.
>
> > + .map = visconti_atu_map,
> > + .unmap = visconti_atu_unmap,
> > + .iova_to_phys = visconti_atu_iova_to_phys,
> > + .free = visconti_atu_domain_free,
> > + }
> > +};
>
> Best regards,
> baolu
Best regards,
Nobuhiro
next prev parent reply other threads:[~2022-06-20 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 1:31 [PATCH 0/3] Add Visconti5 IOMMU driver Nobuhiro Iwamatsu
2022-05-25 1:31 ` [PATCH 1/3] iommu: " Nobuhiro Iwamatsu
2022-05-25 4:45 ` kernel test robot
2022-05-25 6:09 ` kernel test robot
2022-05-25 6:26 ` Baolu Lu
2022-05-25 18:26 ` Jason Gunthorpe
2022-05-26 0:43 ` Tian, Kevin
2022-05-26 1:40 ` Jason Gunthorpe
2022-06-20 5:49 ` nobuhiro1.iwamatsu
2022-06-24 13:39 ` Jason Gunthorpe
2022-06-20 2:15 ` nobuhiro1.iwamatsu [this message]
2022-05-25 9:36 ` kernel test robot
2022-05-25 1:31 ` [PATCH 2/3] iommu: bindings: Add binding documentation for Toshiba Visconti5 IOMMU device Nobuhiro Iwamatsu
2022-06-02 13:43 ` Rob Herring
2022-05-25 1:31 ` [PATCH 3/3] MAINTAINERS: Add entries for Toshiba Visconti5 IOMMU Nobuhiro Iwamatsu
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=TYWPR01MB9420432737626348118C515F92B09@TYWPR01MB9420.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=baolu.lu@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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).