Describe cgroup v2 freezer interface in the cgroup v2 admin guide.
Signed-off-by: Roman Gushchin
Reviewed-by: Mike Rapoport
Cc: Tejun Heo
Cc: linux-doc@vger.kernel.org
Cc: kernel-t...@fb.com
---
Documentation/admin-guide/cgroup-v2.rst | 27 +
1 file changed, 27 insertio
Hi Peter,
On 19/12/2018 19:02, Peter Maydell wrote:
> On Mon, 17 Dec 2018 at 15:56, James Morse wrote:
>> I don't think this really matters. Its only the NMIlike notifications that
>> the
>> guest doesn't have to register or poll. The ones we support today extend the
>> architectures existing be
On Sat, Dec 15, 2018 at 1:23 PM Nathan Chancellor
wrote:
>
> While building arm32 allyesconfig, I ran into the following errors:
>
> arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with
> '-mfloat-abi=softfp -mfpu=neon'
>
> In file included from lib/raid6/neon1.c:27:
> /h
Hi! Am 17.12.18 um 19:24 schrieb Jonathan Corbet:
> On Mon, 17 Dec 2018 16:20:42 +0100
> Thorsten Leemhuis wrote:
>
>> +might be relevant later when investigating problems. Don't worry
>> +yourself too much about this, most of the time it's not a problem to run
> s/yourself//
Thx for this and oth
On Tue, 18 Dec 2018, Jae Hyun Yoo wrote:
> This commit adds a dt-bindings document for PECI client MFD.
>
> Cc: Lee Jones
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Andrew Jeffery
> Cc: James Feist
> Cc: Jason M Biils
> Cc: Joel Stanley
> Cc: Vernon Mauery
> Signed-off-by: Jae Hyun Yoo
>
On Tue, 18 Dec 2018, Jae Hyun Yoo wrote:
> This commit adds PECI client MFD driver.
>
> Cc: Lee Jones
> Cc: Randy Dunlap
> Cc: Rob Herring
> Cc: Andrew Jeffery
> Cc: James Feist
> Cc: Jason M Biils
> Cc: Joel Stanley
> Cc: Vernon Mauery
> Signed-off-by: Jae Hyun Yoo
> ---
> drivers/mfd/
On December 20, 2018 5:34:23 PM GMT+02:00, Jonathan Corbet
wrote:
>On Thu, 20 Dec 2018 09:59:13 +0200
>Mike Rapoport wrote:
>
>> ping?
>
>Sorry, been traveling,
No problem, I just wanted to make sure it didn't fall between the cracks.
> and I still don't really know what to do with
>patches
Hello,
> > I don't understand why this path needs to be optimized. To me it seems, a
> > straight-
> > forward userspace implementation with no additional code in the kernel
> > achieves
> > the same feature. Can you elaborate?
I was doing some benchmarking to figure out the overhead introduce
Am 20.12.18 um 21:10 schrieb Randy Dunlap:
> On 12/20/18 10:21 AM, Thorsten Leemhuis wrote:
>> Am 20.12.18 um 17:38 schrieb Randy Dunlap:
>>> On 12/20/18 7:28 AM, Jonathan Corbet wrote:
On Thu, 20 Dec 2018 16:23:38 +0100
Thorsten Leemhuis wrote:
> While at it: Jonathan, you mentioned
Add komeda_kms abstracton to attach komeda_dev to DRM-KMS
CRTC: according to the komeda_pipeline
PLANE: according to komeda_layer (layer input pipeline)
PRIVATE_OBJS: komeda_pipeline/component all will be treat as private_objs
komeda_kms is for connecting DRM-KMS and komeda_dev, like reporti
Implement a simple wrapper for platform module to build komeda to module,
Also add a very simple D71 layer code to show how to discover a product.
Komeda driver direct bind the product ENTRY function xxx_identity to DT
compatible name like:
d71_product = {
.product_id = MALIDP_D71_PRODUCT_
v2: Some editing changes according to Randy Dunlap's comments
Signed-off-by: James (Qian) Wang
---
Documentation/gpu/drivers.rst| 1 +
Documentation/gpu/komeda-kms.rst | 488 +++
2 files changed, 489 insertions(+)
create mode 100644 Documentation/gpu/komeda-kms
Implement a simple wrapper for platform module to build komeda to module,
Also add a very simple D71 layer code to show how to discover a product.
Komeda driver direct bind the product ENTRY function xxx_identity to DT
compatible name like:
d71_product = {
.product_id = MALIDP_D71_PRODUCT_
komeda_format_caps is for describing ARM display specific features and
limitations of a specific format, and format_caps will be linked into
&komeda_framebuffer like a extension of &drm_format_info.
And komed_format_caps_table will be initialized before the enum_resources,
since the layer features
Add komeda_kms abstracton to attach komeda_dev to DRM-KMS
CRTC: according to the komeda_pipeline
PLANE: according to komeda_layer (layer input pipeline)
PRIVATE_OBJS: komeda_pipeline/component all will be treat as private_objs
komeda_kms is for connecting DRM-KMS and komeda_dev, like reporti
v2: Adjusted the position of KOMEDA by alphabetical order
Signed-off-by: James (Qian) Wang
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 254b7b267731..e48c2e5fd29f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1124,6 +1124,15 @@ S:
1. Added a brief definition of komeda_dev/pipeline/component, this change
didn't add the detailed component features and capabilities, which will
be added in the following changes.
2. Corresponding resources discovery and initialzation functions.
Signed-off-by: James (Qian) Wang
Changes in
komeda_framebuffer is for extending drm_framebuffer to add komeda own
attributes and komeda specific fb handling.
Changes in v3:
- Fixed style problem found by checkpatch.pl --strict.
Signed-off-by: James (Qian) Wang
---
drivers/gpu/drm/arm/display/komeda/Makefile | 3 +-
.../arm/display/ko
Parse DT and initialize corresponding dev/pipeline attributes.
Changes in v3:
- Fixed style problem found by checkpatch.pl --strict.
Changes in v2:
- Unified abbreviation of "pipeline" to "pipe".
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_dev.c | 76 ++
Add DT bindings documentation for the ARM display processor D71 and later
IPs.
Signed-off-by: James (Qian) Wang
Changes in v3:
- Deleted unnecessary property: interrupt-names.
- Dropped 'ports' and moving 'port' up a level.
---
.../bindings/display/arm/arm,komeda.txt | 79
This is the first patchset of ARM new komeda display driver, this patchset
added all basic structure of komeda, relationship of DRM-KMS with komeda,
for tring to give a brife overview of komeda-driver.
komeda is for supporting the ARM display processor D71 and later IPs, Since from
D71, Arm displa
21 matches
Mail list logo
