From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: amd-seattle: Fix PCI bus range due to SMMU limitation
Date: Thu, 04 Dec 2014 17:10:52 +0100 [thread overview]
Message-ID: <2035567.rcXVTvDFpt@wuerfel> (raw)
In-Reply-To: <1417405600-19232-3-git-send-email-suravee.suthikulpanit@amd.com>
On Sunday 30 November 2014 21:46:40 suravee.suthikulpanit at amd.com wrote:
> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>
> Since PCIe is using SMMUv1 which only supports 15-bit stream ID,
> only 7-bit PCI bus id is used to specify stream ID. Therefore,
> we only limit the PCI bus range to 0x7f.
>
> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>
Applied the second patch, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: suravee.suthikulpanit@amd.com, mark.rutland@arm.com,
will.deacon@arm.com, marc.zyngier@arm.com,
catalin.marinas@arm.com, liviu.dudau@arm.com,
linux-kernel@vger.kernel.org, arm@kernel.org,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: Re: [PATCH 2/2] arm64: amd-seattle: Fix PCI bus range due to SMMU limitation
Date: Thu, 04 Dec 2014 17:10:52 +0100 [thread overview]
Message-ID: <2035567.rcXVTvDFpt@wuerfel> (raw)
In-Reply-To: <1417405600-19232-3-git-send-email-suravee.suthikulpanit@amd.com>
On Sunday 30 November 2014 21:46:40 suravee.suthikulpanit@amd.com wrote:
> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>
> Since PCIe is using SMMUv1 which only supports 15-bit stream ID,
> only 7-bit PCI bus id is used to specify stream ID. Therefore,
> we only limit the PCI bus range to 0x7f.
>
> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>
Applied the second patch, thanks!
Arnd
next prev parent reply other threads:[~2014-12-04 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 3:46 [PATCH 0/2] arm64: amd-seattle: Misceleneous DT fix up suravee.suthikulpanit at amd.com
2014-12-01 3:46 ` suravee.suthikulpanit
2014-12-01 3:46 ` [PATCH 1/2] arm64: amd-seattle: Fix dma-ranges property suravee.suthikulpanit at amd.com
2014-12-01 3:46 ` suravee.suthikulpanit
2014-12-01 13:33 ` Arnd Bergmann
2014-12-01 13:33 ` Arnd Bergmann
2014-12-02 14:12 ` Suthikulpanit, Suravee
2014-12-02 14:12 ` Suthikulpanit, Suravee
2014-12-04 16:17 ` Arnd Bergmann
2014-12-04 16:17 ` Arnd Bergmann
2014-12-01 3:46 ` [PATCH 2/2] arm64: amd-seattle: Fix PCI bus range due to SMMU limitation suravee.suthikulpanit at amd.com
2014-12-01 3:46 ` suravee.suthikulpanit
2014-12-04 16:10 ` Arnd Bergmann [this message]
2014-12-04 16:10 ` Arnd Bergmann
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=2035567.rcXVTvDFpt@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.