From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Jon Nettleton <jon@solid-run.com>,
"erik.kaneda@intel.com" <erik.kaneda@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"devel@acpica.org" <devel@acpica.org>,
"robert.moore@intel.com" <robert.moore@intel.com>,
Linuxarm <linuxarm@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: RE: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
Date: Thu, 25 Mar 2021 15:54:51 +0000 [thread overview]
Message-ID: <acfab98e75434a59910cf56336c54ba2@huawei.com> (raw)
In-Reply-To: <CABdtJHtZPyWpXN9JZbgdu=HswreTc2o2pRhrwHFzQJqz-kFSBw@mail.gmail.com>
> -----Original Message-----
> From: Jon Nettleton [mailto:jon@solid-run.com]
> Sent: 25 March 2021 08:40
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: erik.kaneda@intel.com; linux-arm-kernel@lists.infradead.org;
> linux-acpi@vger.kernel.org; iommu@lists.linux-foundation.org;
> devel@acpica.org; Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>;
> robert.moore@intel.com; Linuxarm <linuxarm@huawei.com>;
> steven.price@arm.com; Guohanjun (Hanjun Guo) <guohanjun@huawei.com>;
> Sami.Mujawar@arm.com; robin.murphy@arm.com; wanghuiqiang
> <wanghuiqiang@huawei.com>
> Subject: Re: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
[...]
> Well it was a released revision, although it was found to have issues.
> Currently
> HoneyComb Systems Ready certified firmware does include support for this
> table,
> although incomplete. Without agreement on mainline support I am fine to
> update
> to the latest spec bump.
Ok. Sorry didn’t know that you already had a firmware with that revision.
Thanks for agreeing to update to latest.
> >
> > So could you please revert the merge and I am planning to work on the E.b
> soon.
> > Please let me know if I need to explicitly send a revert pull request or not.
>
> Can you please CC. me on your next release. I was planning on spending time
> on this regardless. I already have a patchset for the fsl-mc-bus driver that
> needs to change in order to function properly with RMR support.
Sure. Will CC you.
Hi All,
I have send pull requests to acpica git for reverting rev E and to update it with E.b,
https://github.com/acpica/acpica/pull/682
Please take a look and let me know.
Thanks,
Shameer
WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Jon Nettleton <jon@solid-run.com>,
"erik.kaneda@intel.com" <erik.kaneda@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Linuxarm <linuxarm@huawei.com>,
"robert.moore@intel.com" <robert.moore@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
wanghuiqiang <wanghuiqiang@huawei.com>,
"Guohanjun \(Hanjun Guo\)" <guohanjun@huawei.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: RE: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
Date: Thu, 25 Mar 2021 15:54:51 +0000 [thread overview]
Message-ID: <acfab98e75434a59910cf56336c54ba2@huawei.com> (raw)
In-Reply-To: <CABdtJHtZPyWpXN9JZbgdu=HswreTc2o2pRhrwHFzQJqz-kFSBw@mail.gmail.com>
> -----Original Message-----
> From: Jon Nettleton [mailto:jon@solid-run.com]
> Sent: 25 March 2021 08:40
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: erik.kaneda@intel.com; linux-arm-kernel@lists.infradead.org;
> linux-acpi@vger.kernel.org; iommu@lists.linux-foundation.org;
> devel@acpica.org; Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>;
> robert.moore@intel.com; Linuxarm <linuxarm@huawei.com>;
> steven.price@arm.com; Guohanjun (Hanjun Guo) <guohanjun@huawei.com>;
> Sami.Mujawar@arm.com; robin.murphy@arm.com; wanghuiqiang
> <wanghuiqiang@huawei.com>
> Subject: Re: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
[...]
> Well it was a released revision, although it was found to have issues.
> Currently
> HoneyComb Systems Ready certified firmware does include support for this
> table,
> although incomplete. Without agreement on mainline support I am fine to
> update
> to the latest spec bump.
Ok. Sorry didn’t know that you already had a firmware with that revision.
Thanks for agreeing to update to latest.
> >
> > So could you please revert the merge and I am planning to work on the E.b
> soon.
> > Please let me know if I need to explicitly send a revert pull request or not.
>
> Can you please CC. me on your next release. I was planning on spending time
> on this regardless. I already have a patchset for the fsl-mc-bus driver that
> needs to change in order to function properly with RMR support.
Sure. Will CC you.
Hi All,
I have send pull requests to acpica git for reverting rev E and to update it with E.b,
https://github.com/acpica/acpica/pull/682
Please take a look and let me know.
Thanks,
Shameer
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Jon Nettleton <jon@solid-run.com>,
"erik.kaneda@intel.com" <erik.kaneda@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"devel@acpica.org" <devel@acpica.org>,
"robert.moore@intel.com" <robert.moore@intel.com>,
Linuxarm <linuxarm@huawei.com>,
"steven.price@arm.com" <steven.price@arm.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: RE: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
Date: Thu, 25 Mar 2021 15:54:51 +0000 [thread overview]
Message-ID: <acfab98e75434a59910cf56336c54ba2@huawei.com> (raw)
In-Reply-To: <CABdtJHtZPyWpXN9JZbgdu=HswreTc2o2pRhrwHFzQJqz-kFSBw@mail.gmail.com>
> -----Original Message-----
> From: Jon Nettleton [mailto:jon@solid-run.com]
> Sent: 25 March 2021 08:40
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: erik.kaneda@intel.com; linux-arm-kernel@lists.infradead.org;
> linux-acpi@vger.kernel.org; iommu@lists.linux-foundation.org;
> devel@acpica.org; Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>;
> robert.moore@intel.com; Linuxarm <linuxarm@huawei.com>;
> steven.price@arm.com; Guohanjun (Hanjun Guo) <guohanjun@huawei.com>;
> Sami.Mujawar@arm.com; robin.murphy@arm.com; wanghuiqiang
> <wanghuiqiang@huawei.com>
> Subject: Re: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
[...]
> Well it was a released revision, although it was found to have issues.
> Currently
> HoneyComb Systems Ready certified firmware does include support for this
> table,
> although incomplete. Without agreement on mainline support I am fine to
> update
> to the latest spec bump.
Ok. Sorry didn’t know that you already had a firmware with that revision.
Thanks for agreeing to update to latest.
> >
> > So could you please revert the merge and I am planning to work on the E.b
> soon.
> > Please let me know if I need to explicitly send a revert pull request or not.
>
> Can you please CC. me on your next release. I was planning on spending time
> on this regardless. I already have a patchset for the fsl-mc-bus driver that
> needs to change in order to function properly with RMR support.
Sure. Will CC you.
Hi All,
I have send pull requests to acpica git for reverting rev E and to update it with E.b,
https://github.com/acpica/acpica/pull/682
Please take a look and let me know.
Thanks,
Shameer
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi at huawei.com>
To: devel@acpica.org
Subject: [Devel] Re: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
Date: Thu, 25 Mar 2021 15:54:51 +0000 [thread overview]
Message-ID: <acfab98e75434a59910cf56336c54ba2@huawei.com> (raw)
In-Reply-To: CABdtJHtZPyWpXN9JZbgdu=HswreTc2o2pRhrwHFzQJqz-kFSBw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
> -----Original Message-----
> From: Jon Nettleton [mailto:jon(a)solid-run.com]
> Sent: 25 March 2021 08:40
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi(a)huawei.com>
> Cc: erik.kaneda(a)intel.com; linux-arm-kernel(a)lists.infradead.org;
> linux-acpi(a)vger.kernel.org; iommu(a)lists.linux-foundation.org;
> devel(a)acpica.org; Lorenzo Pieralisi <lorenzo.pieralisi(a)arm.com>;
> robert.moore(a)intel.com; Linuxarm <linuxarm(a)huawei.com>;
> steven.price(a)arm.com; Guohanjun (Hanjun Guo) <guohanjun(a)huawei.com>;
> Sami.Mujawar(a)arm.com; robin.murphy(a)arm.com; wanghuiqiang
> <wanghuiqiang(a)huawei.com>
> Subject: Re: [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E
[...]
> Well it was a released revision, although it was found to have issues.
> Currently
> HoneyComb Systems Ready certified firmware does include support for this
> table,
> although incomplete. Without agreement on mainline support I am fine to
> update
> to the latest spec bump.
Ok. Sorry didn’t know that you already had a firmware with that revision.
Thanks for agreeing to update to latest.
> >
> > So could you please revert the merge and I am planning to work on the E.b
> soon.
> > Please let me know if I need to explicitly send a revert pull request or not.
>
> Can you please CC. me on your next release. I was planning on spending time
> on this regardless. I already have a patchset for the fsl-mc-bus driver that
> needs to change in order to function properly with RMR support.
Sure. Will CC you.
Hi All,
I have send pull requests to acpica git for reverting rev E and to update it with E.b,
https://github.com/acpica/acpica/pull/682
Please take a look and let me know.
Thanks,
Shameer
next prev parent reply other threads:[~2021-03-25 15:55 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 12:11 [RFC PATCH v2 0/8] ACPI/IORT: Support for IORT RMR node Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 1/8] ACPICA: IORT: Update for revision E Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2021-03-22 10:36 ` Shameerali Kolothum Thodi
2021-03-22 10:36 ` [Devel] " Shameerali Kolothum Thodi
2021-03-22 10:36 ` Shameerali Kolothum Thodi
2021-03-22 10:36 ` Shameerali Kolothum Thodi
2021-03-22 21:57 ` Kaneda, Erik
2021-03-22 21:57 ` Kaneda, Erik
2021-03-22 21:57 ` Kaneda, Erik
2021-03-23 15:53 ` Lorenzo Pieralisi
2021-03-23 15:53 ` [Devel] " Lorenzo Pieralisi
2021-03-23 15:53 ` Lorenzo Pieralisi
2021-03-23 15:53 ` Lorenzo Pieralisi
2021-03-23 18:51 ` Kaneda, Erik
2021-03-23 18:51 ` Kaneda, Erik
2021-03-23 18:51 ` Kaneda, Erik
2021-03-24 9:50 ` Lorenzo Pieralisi
2021-03-24 9:50 ` [Devel] " Lorenzo Pieralisi
2021-03-24 9:50 ` Lorenzo Pieralisi
2021-03-24 9:50 ` Lorenzo Pieralisi
2021-03-25 8:40 ` Jon Nettleton
2021-03-25 8:40 ` Jon Nettleton
2021-03-25 8:40 ` Jon Nettleton
2021-03-25 15:54 ` Shameerali Kolothum Thodi [this message]
2021-03-25 15:54 ` [Devel] " Shameerali Kolothum Thodi
2021-03-25 15:54 ` Shameerali Kolothum Thodi
2021-03-25 15:54 ` Shameerali Kolothum Thodi
2021-04-15 7:27 ` Auger Eric
2021-04-15 7:27 ` Auger Eric
2021-04-15 7:27 ` Auger Eric
2020-11-19 12:11 ` [RFC PATCH v2 2/8] ACPI/IORT: Add support for RMR node parsing Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2021-04-15 9:39 ` Auger Eric
2021-04-15 9:39 ` Auger Eric
2021-04-15 9:39 ` Auger Eric
2021-04-15 10:30 ` Shameerali Kolothum Thodi
2021-04-15 10:30 ` [Devel] " Shameerali Kolothum Thodi
2021-04-15 10:30 ` Shameerali Kolothum Thodi
2021-04-15 10:30 ` Shameerali Kolothum Thodi
2020-11-19 12:11 ` [RFC PATCH v2 3/8] iommu/dma: Introduce generic helper to retrieve RMR info Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 4/8] ACPI/IORT: Add RMR memory regions reservation helper Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 5/8] iommu/arm-smmu-v3: Introduce strtab init helper Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 6/8] iommu/arm-smmu-v3: Add bypass flag to arm_smmu_write_strtab_ent() Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 7/8] iommu/arm-smmu-v3: Get associated RMR info and install bypass STE Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` [RFC PATCH v2 8/8] iommu/arm-smmu-v3: Reserve any RMR regions associated with a dev Shameer Kolothum
2020-11-19 12:11 ` [Devel] " Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-11-19 12:11 ` Shameer Kolothum
2020-12-10 10:25 ` [RFC PATCH v2 0/8] ACPI/IORT: Support for IORT RMR node Steven Price
2020-12-10 10:25 ` Steven Price
2020-12-10 10:25 ` Steven Price
2020-12-14 10:55 ` Shameerali Kolothum Thodi
2020-12-14 10:55 ` [Devel] " Shameerali Kolothum Thodi
2020-12-14 10:55 ` Shameerali Kolothum Thodi
2020-12-14 10:55 ` Shameerali Kolothum Thodi
2020-12-14 12:33 ` Robin Murphy
2020-12-14 12:33 ` [Devel] " Robin Murphy
2020-12-14 12:33 ` Robin Murphy
2020-12-14 12:33 ` Robin Murphy
2020-12-14 13:42 ` Steven Price
2020-12-14 13:42 ` Steven Price
2020-12-14 13:42 ` Steven Price
2020-12-14 14:47 ` Shameerali Kolothum Thodi
2020-12-14 14:47 ` [Devel] " Shameerali Kolothum Thodi
2020-12-14 14:47 ` Shameerali Kolothum Thodi
2020-12-14 14:47 ` Shameerali Kolothum Thodi
2020-12-17 14:47 ` Jon Nettleton
2020-12-17 14:47 ` Jon Nettleton
2020-12-17 14:47 ` Jon Nettleton
2020-12-17 15:42 ` Shameerali Kolothum Thodi
2020-12-17 15:42 ` [Devel] " Shameerali Kolothum Thodi
2020-12-17 15:42 ` Shameerali Kolothum Thodi
2020-12-17 15:42 ` Shameerali Kolothum Thodi
2020-12-17 15:53 ` Jon Nettleton
2020-12-17 15:53 ` Jon Nettleton
2020-12-17 15:53 ` Jon Nettleton
2020-12-18 10:53 ` Jon Nettleton
2020-12-18 10:53 ` Jon Nettleton
2020-12-18 10:53 ` Jon Nettleton
2021-01-04 8:55 ` Shameerali Kolothum Thodi
2021-01-04 8:55 ` [Devel] " Shameerali Kolothum Thodi
2021-01-04 8:55 ` Shameerali Kolothum Thodi
2021-01-04 8:55 ` Shameerali Kolothum Thodi
2021-01-04 10:55 ` Jon Nettleton
2021-01-04 10:55 ` Jon Nettleton
2021-01-04 10:55 ` Jon Nettleton
2021-04-09 9:50 ` Auger Eric
2021-04-09 9:50 ` Auger Eric
2021-04-09 9:50 ` Auger Eric
2021-04-09 10:08 ` Shameerali Kolothum Thodi
2021-04-09 10:08 ` [Devel] " Shameerali Kolothum Thodi
2021-04-09 10:08 ` Shameerali Kolothum Thodi
2021-04-09 10:08 ` Shameerali Kolothum Thodi
2021-04-15 9:48 ` Auger Eric
2021-04-15 9:48 ` Auger Eric
2021-04-15 9:48 ` Auger Eric
2021-04-15 10:37 ` Shameerali Kolothum Thodi
2021-04-15 10:37 ` [Devel] " Shameerali Kolothum Thodi
2021-04-15 10:37 ` Shameerali Kolothum Thodi
2021-04-15 10:37 ` Shameerali Kolothum Thodi
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=acfab98e75434a59910cf56336c54ba2@huawei.com \
--to=shameerali.kolothum.thodi@huawei.com \
--cc=Sami.Mujawar@arm.com \
--cc=devel@acpica.org \
--cc=erik.kaneda@intel.com \
--cc=guohanjun@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jon@solid-run.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robert.moore@intel.com \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=wanghuiqiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.