Hi Tomasz,
Thanks very much for you suggestion and explain so detail.
please help check below.
On Fri, 2015-03-27 at 18:41 +0900, Tomasz Figa wrote:
Hi Yong Wu,
Sorry for long delay, I had to figure out some time to look at this again.
On Wed, Mar 18, 2015 at 8:22 PM, Yong Wu
Hi Mark,
Thanks very much for review.
About the clock name should be the PoV of _this_ device. Could you
help check below?
On Fri, 2015-03-06 at 11:13 +, Mark Rutland wrote:
On Fri, Mar 06, 2015 at 10:48:18AM +, yong...@mediatek.com wrote:
From: Yong Wu yong...@mediatek.com
On Tue, Mar 31, 2015 at 05:02:14PM +0200, Joerg Roedel wrote:
Hi Thierry,
On Fri, Mar 27, 2015 at 11:15:41AM +0100, Thierry Reding wrote:
Another possibility would be for you to ack this patch so that I can
take it into the same branch as the dependency. The remainder of this
series
On Tue, Apr 14, 2015 at 10:07:54AM +0100, Yong Wu wrote:
Hi Mark,
Thanks very much for review.
About the clock name should be the PoV of _this_ device. Could you
help check below?
On Fri, 2015-03-06 at 11:13 +, Mark Rutland wrote:
On Fri, Mar 06, 2015 at 10:48:18AM +,
Hi Will,
-Original Message-
From: iommu-boun...@lists.linux-foundation.org [mailto:iommu-
boun...@lists.linux-foundation.org] On Behalf Of Will Deacon
Sent: Monday, April 13, 2015 4:11 PM
To: Baptiste Reynal
Cc: Linux IOMMU
Subject: Re: SMMU 2-stage support
On Fri, Apr 03, 2015
On 04/10/15 at 04:42pm, Li, Zhen-Hua wrote:
This patchset is an update of Bill Sumner's patchset, implements a fix for:
If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
when a panic happens, the kdump kernel will boot with these faults:
dmar: DRHD: handling
On Tue, Apr 14, 2015 at 3:31 PM, Yong Wu yong...@mediatek.com wrote:
+
+ piommu-protect_va = devm_kmalloc(piommu-dev,
MTK_PROTECT_PA_ALIGN*2,
style: Operators like * should have space on both sides.
+ GFP_KERNEL);
Shouldn't
On 04/15/2015 08:57 AM, Dave Young wrote:
Again, I think it is bad to use old page table, below issues need consider:
1) make sure old page table are reliable across crash
2) do not allow writing oldmem after crash
Please correct me if I'm wrong, or if above is not doable I think I will vote
On Tue, 2015-04-14 at 21:49 +0800, Yong Wu wrote:
Hi Mark,
On Tue, 2015-04-14 at 11:06 +0100, Mark Rutland wrote:
On Tue, Apr 14, 2015 at 10:07:54AM +0100, Yong Wu wrote:
Hi Mark,
Thanks very much for review.
About the clock name should be the PoV of _this_ device. Could
smi_common:smi@14022000 {
compatible = “mediate, mt8173-smi”;
reg = 0 0x14022000 0 0x1000;
clocks = mmsys MM_SMI_COMMON;
clocks-names = “smi_common”;
};
larb0: larb@14021000 {
Hi Mark,
On Tue, 2015-04-14 at 11:06 +0100, Mark Rutland wrote:
On Tue, Apr 14, 2015 at 10:07:54AM +0100, Yong Wu wrote:
Hi Mark,
Thanks very much for review.
About the clock name should be the PoV of _this_ device. Could you
help check below?
On Fri, 2015-03-06 at 11:13
11 matches
Mail list logo
