CC MST who touched this file in last commit on it.
On 03/22/2017 01:48 PM, Linas Vepstas wrote:
> Hi,
>
> On Tue, Mar 21, 2017 at 9:24 PM, Cao jin wrote:
>> Include whitespace shooting; correction; typo fix; superfluous word
>> dropping.
>
>>
>> diff --git a/Documentation/PCI/pci-error-recovery
Add initial SX3000b platform related documentation to document tree:
- Vendor prefix
- Platform binding documentation
- Interrupt Controller Unit binding documentation.
Signed-off-by: Amit Kama
diff --git
a/Documentation/devicetree/bindings/interrupt-controller/satixfy-icu.txt
b/Documentati
Hi,
On Tue, Mar 21, 2017 at 9:24 PM, Cao jin wrote:
> Include whitespace shooting; correction; typo fix; superfluous word
> dropping.
>
> diff --git a/Documentation/PCI/pci-error-recovery.txt
> b/Documentation/PCI/pci-error-recovery.txt
> index da3b217..0b6bb3e 100644
> --- a/Documentation/PCI/
Add initial support for boards based on Satixfy's SX3000b (Catniss) SoC.
The SoC includes a MIPS interAptiv dual core 4 VPE processor and boots
using device-tree.
Signed-off-by: Amit Kama
The irqchip file (irq-sx3000b.c) is pertinent to the platform.
IRQCHIP maintainers - is it possible to mer
Thanks for this, I'm getting enough questions about this, so it's nice to
have a link :)
First comment: I don't think rst requires unwrapped lines, so please break
those up.
Second comment: I'd really like to have a link to libevdev here. It has a
uinput interface that's a bit more obvious and ta
Signed-off-by: Marcos Paulo de Souza
---
Documentation/input/uinput.rst | 158 +
1 file changed, 158 insertions(+)
create mode 100644 Documentation/input/uinput.rst
diff --git a/Documentation/input/uinput.rst b/Documentation/input/uinput.rst
new file mode
Hi guys,
so, after taking some time to understand how to work with uinput, and to grab
some examples
on web, I discovered that kernel doesn't have any "official" documentation
about it.
So, here we are :)
I added some examples based in my tests, there are samples of EV_REL and
EV_KEY, but
we
> On Mar 21, 2017, at 3:51 PM, Gabriel Somlo wrote:
>
> And I get the exact same results on the MacBookAir4,2 (which exhibits
> no freezing or extreme sluggishness when running OS X 10.7 smp with
> Michael's KVM MWAIT-in-L1 patch)...
Sorry for my confusion. I didn’t read the entire thread and t
On Tue, Mar 21, 2017 at 08:22:39PM +0100, Radim Krčmář wrote:
> 2017-03-21 10:29-0700, Nadav Amit:
> >
> > > On Mar 21, 2017, at 9:58 AM, Radim Krčmář wrote:
> >
> > > In '-smp 2', the writing VCPU always does 1 wakeups by writing into
> > > monitored memory, but the mwaiting VCPU can be als
On Tue, Mar 21, 2017 at 04:52:28PM +0100, Daniel Vetter wrote:
> The discussion pretty much concluded without objections, let's
> document what we agreed on.
>
> Cc'ing linux-doc for the new tag in Documentation/process/index.rst.
>
> Cc: Jonathan Corbet
> Cc: linux-doc@vger.kernel.org
> Cc: Dav
2017-03-21 10:29-0700, Nadav Amit:
>
> > On Mar 21, 2017, at 9:58 AM, Radim Krčmář wrote:
>
> > In '-smp 2', the writing VCPU always does 1 wakeups by writing into
> > monitored memory, but the mwaiting VCPU can be also woken up by host
> > interrupts, which might add a few exits depending o
On Tue, Mar 21, 2017 at 05:16:32PM +0100, Joerg Roedel wrote:
> On Wed, Mar 15, 2017 at 11:22:18PM +0200, Michael S. Tsirkin wrote:
> > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> > index d1efe2c..18e53bc 100644
> > --- a/arch/x86/kvm/svm.c
> > +++ b/arch/x86/kvm/svm.c
> > @@ -1198,8 +11
> On Mar 21, 2017, at 9:58 AM, Radim Krčmář wrote:
> In '-smp 2', the writing VCPU always does 1 wakeups by writing into
> monitored memory, but the mwaiting VCPU can be also woken up by host
> interrupts, which might add a few exits depending on timing.
>
> I didn't spend much time in maki
2017-03-21 05:22+0200, Michael S. Tsirkin:
> On Fri, Mar 17, 2017 at 09:23:56AM -0400, Gabriel L. Somlo wrote:
>> OK, now on to Radim's test, on the MacPro1,1:
>>
>> [kvm-unit-tests]$ time TIMEOUT=20 ./x86-run x86/mwait.flat -append '240 1 1'
>> timeout -k 1s --foreground 20 qemu-kvm -nodefaults -
On Wed, Mar 15, 2017 at 11:22:18PM +0200, Michael S. Tsirkin wrote:
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index d1efe2c..18e53bc 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -1198,8 +1198,6 @@ static void init_vmcb(struct vcpu_svm *svm)
> set_intercept(
The discussion pretty much concluded without objections, let's
document what we agreed on.
Cc'ing linux-doc for the new tag in Documentation/process/index.rst.
Cc: Jonathan Corbet
Cc: linux-doc@vger.kernel.org
Cc: Dave Airlie
Cc: Sean Paul
Cc: Jani Nikula
Cc: Alex Deucher
Cc: Lukas Wunner
S
This patch adds a new DRM documentation entry and links to the input
format table added in the dw_hdmi header.
Signed-off-by: Neil Armstrong
---
Documentation/gpu/bridge/dw-hdmi.rst | 15 +++
Documentation/gpu/index.rst | 1 +
2 files changed, 16 insertions(+)
create mode
Some display pipelines can only provide non-RBG input pixels to the HDMI TX
Controller, this patch takes the pixel format from the plat_data if provided.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 326 +-
include/drm/bridge/dw_hdmi.h
The HDMI TX controller support HPD and RXSENSE signaling from the PHY
via it's STAT0 PHY interface, but some vendor PHYs can manage these
signals independently from the controller, thus these STAT0 handling
should be moved to PHY specific operations and become optional.
The existing STAT0 HPD and
Add documentation for added Bus Formats to describe RGB and YUV formats used
as input to the Synopsys DesignWare HDMI TX Controller.
Signed-off-by: Neil Armstrong
---
Documentation/media/uapi/v4l/subdev-formats.rst | 871 +++-
1 file changed, 857 insertions(+), 14 deletions(-
The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller
in combination with a very custom PHY.
Thanks to Laurent Pinchart's changes, the HW report the following :
Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
The following differs from common PHY integration as
Hi,
On Fri, Mar 10, 2017 at 01:27:39AM -0500, Anurup M wrote:
> +HiP0x chips are encapsulated by multiple CPU and IO die's. The CPU die is
Nit: that apostrophe shouldn't be there.
[...]
> +The current driver doesnot support sampling. so "perf record" is unsupported.
Nit: spacing
Otherwise, t
Include whitespace shooting; correction; typo fix; superfluous word
dropping.
Signed-off-by: Cao jin
---
This patch was sent in last December, which is not quite suitable at that time,
because link reset is not clear. Now the section "Link Reset" has been cleaned,
submit this patch again.
Docum
On 21 March 2017 at 15:33, Alexander Shishkin
wrote:
> On 21 March 2017 at 07:57, Chunyan Zhang wrote:
>> On 20 March 2017 at 19:09, Alexander Shishkin
>> wrote:
>>> Chunyan Zhang writes:
>>>
Hi Alex,
On 20 March 2017 at 16:49, Alexander Shishkin
wrote:
> Hi Chunyan,
>>
Add Documentation/usb/usb3-debug-port.rst. This document includes
the guide for using USB3 debug port.
Cc: linux-doc@vger.kernel.org
Signed-off-by: Lu Baolu
---
Documentation/usb/usb3-debug-port.rst | 100 ++
1 file changed, 100 insertions(+)
create mode 100644 D
On 21 March 2017 at 07:57, Chunyan Zhang wrote:
> On 20 March 2017 at 19:09, Alexander Shishkin
> wrote:
>> Chunyan Zhang writes:
>>
>>> Hi Alex,
>>>
>>> On 20 March 2017 at 16:49, Alexander Shishkin
>>> wrote:
Hi Chunyan,
A couple of clarifications: iirc this applies to the func
Kees Cook writes:
> On Mon, Mar 20, 2017 at 1:39 AM, Michael Ellerman wrote:
>> Andrew Donnellan writes:
>>
>>> Commit 65c059bcaa73 ("powerpc: Enable support for GCC plugins") enabled GCC
>>> plugins on powerpc, but neglected to update the architecture list in the
>>> docs. Rectify this.
>>>
>>
27 matches
Mail list logo
