d.
- These additional properties now have "samsung,srom-XXX" format
- Fixed code style, now better understood.
v2 => v3:
- Fixed up SROMc region size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
---
arch/arm/mach-exynos/Kconfig
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Signed-off-by: Pavel Fedin
---
.../bindings/arm/samsung/exynos-srom.txt | 68 +-
1 file changed, 66 insertions(+), 2 deletions(-)
diff
This machine uses own SoC device tree file, add missing part.
We insert the complete description, with ranges, because we are going to
connect devices to it. Values in ranges are SoC-specific, so they go here
in order not to duplicate them for every machine.
Signed-off-by: Pavel Fedin
---
arch
Hello!
>> BTW, you could just combine both patches. I guess you didn't to
>> maintain authorship?
>OK. Will squash both of these patches, unless Pavel do not any objections.
I don't.
Kind regards.
Hello!
> From: Pavel Fedin
>
> After GICv2m was enabled for 32-bit ARM kernel, a warning popped up:
Thank you for the cooperation, i'm now back from my vacation.
What about the first patch in the series, which actually enables GICv2m on 32
bits? I don't see it anywhere
Hi!
> OK so both of you say the same thing. Will respin accordingly
You may also want to add this:
Tested-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
my modified qemu now has kvm_msi_flags global variable which
defaults to 0. ITS
code, then, if activated, changes it to KVM_MSI_VALID_DEVID, and qemu starts
supplying device IDs to
the related calls.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To u
_MSI_VALID_DEVID;
kvm_gsi_routing_allowed = true;
kvm_msi_via_irqfd_allowed = true;
}
--- cut ---
I can post my sets as RFCs to qemu mailing list, if you want to take a look at
the whole change
set.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To un
> Just so I'm sure I understand: The way the kernel differentiates between
> no-devid and devid==0, is whether or not the devid flag is set, correct?
Yes, exactly.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this lis
ID_DEVID and we
already have 'flags'
field. Using them would just make the API more consistent because
KVM_SIGNAL_MSI already uses them
in absolutely the same manner. That's my point and nothing more.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Researc
ld throw it away
completely and invent
KVM_SIGNAL_EXT_MSI ioctl for sending MSIs with device ID. This would also be
consistent IMO.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-ker
Certain platforms (e. g. BSD-based ones) define some ELF constants according
to host.
This patch fixes problems with cross-building Linux kernel on these platforms
(e. g. building ARM
32-bit version on x86-64 host).
Signed-off-by: Pavel Fedin
---
If you are not fond of mentioning Cygwin in
c code, which
> returns -EINVAL atm. So I plan to introduce this capability already with
> the ITS emulation series, so we can just pick it up in the IRQ routing
> series.
Then may be you follow https://lkml.org/lkml/2015/7/7/115 and replace flag
with something like
KVM_SIGNAL_EXT_MSI io
Hello!
> This patch should not be applied independently without the fix in
> mainline:
>
> 0de58f852875a0f0dcfb120bb8433e4e73c7803b
> (ARM/arm64: KVM: correct PTE uncachedness check, 2015-12-03)
It's ok, both are queued.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung
All series:
Reviewed-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-Original Message-
From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
Behalf Of Sunil Goutham
Sent: Thursday, December 10, 2015 10:55 AM
MSI window out of target's RAM. But how does this
work on a PC then? What if our host is PC, and we
want to emulate some ARM board, which has RAM at FE00 ? Or does it mean
that PC architecture is flawed and can reliably handle
PCI passthrough only for itself ?
Kind regards,
Pav
from what we are implementing now.
Just curious.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia
Commit-ID: 157add60cb35913b8a848a3d7e6456b8ed134796
Gitweb: http://git.kernel.org/tip/157add60cb35913b8a848a3d7e6456b8ed134796
Author: Pavel Fedin
AuthorDate: Sun, 13 Sep 2015 12:14:33 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
irqchip/GICv2m: Fix
101 - 119 of 119 matches
Mail list logo
