The tool works nicely with hid-generic, but it ends up creating 9
different input nodes with most of them only having ABS_MISC set.
Filter the axis out, which reduces the amount of devices to 2. One is
the proper System Multi-axis collection, the other exported device
seems to provide SLEEP and
Looks like 4 was sufficient until now. However, the Surface Dial needs
a stack of 5 and simply fails at probing.
Dynamically add HID_COLLECTION_STACK_SIZE to the size of the stack if
we hit the upper bound.
Checkpatch complains about bare unsigned, so converting those to
'unsigned int' in struct
From: Dmitry Torokhov
According to Microsoft specification [1] for Precision Touchpads (and
Touchscreens) the devices use "confidence" reports to signal accidental
touches, or contacts that are "too large to be a finger". Instead of
simply marking contact inactive in this case (which causes
From: Dmitry Torokhov
Usually, there is no palm rejection for touchscreens. You don't rest
your palm on the touchscreen while interacting with it.
However, some wacom devices do so because you can rest your palm while
interacting with the stylus.
Unfortunately, the spec for touchscreens[1] is
The current way of handling multitouch data is not very straightforward:
- in mt_event() we do nothing
- in mt_report() we:
- do some gym to fetch the scantime and the contact count
- then iterate over the input fields where we copy the data to a
temporary place
- when we see the last
From: Dmitry Torokhov
According to [1] the confidence is used not only by touchpad devices,
but also by touchscreens.
[1]
https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchscreen-required-hid-top-level-collections
Acked-by: Peter Hutterer
Signed-off-by:
The tool works nicely with hid-generic, but it ends up creating 9
different input nodes with most of them only having ABS_MISC set.
Filter the axis out, which reduces the amount of devices to 2. One is
the proper System Multi-axis collection, the other exported device
seems to provide SLEEP and
Looks like 4 was sufficient until now. However, the Surface Dial needs
a stack of 5 and simply fails at probing.
Dynamically add HID_COLLECTION_STACK_SIZE to the size of the stack if
we hit the upper bound.
Checkpatch complains about bare unsigned, so converting those to
'unsigned int' in struct
From: Dmitry Torokhov
According to Microsoft specification [1] for Precision Touchpads (and
Touchscreens) the devices use "confidence" reports to signal accidental
touches, or contacts that are "too large to be a finger". Instead of
simply marking contact inactive in this case (which causes
From: Dmitry Torokhov
Usually, there is no palm rejection for touchscreens. You don't rest
your palm on the touchscreen while interacting with it.
However, some wacom devices do so because you can rest your palm while
interacting with the stylus.
Unfortunately, the spec for touchscreens[1] is
The current way of handling multitouch data is not very straightforward:
- in mt_event() we do nothing
- in mt_report() we:
- do some gym to fetch the scantime and the contact count
- then iterate over the input fields where we copy the data to a
temporary place
- when we see the last
From: Dmitry Torokhov
According to [1] the confidence is used not only by touchpad devices,
but also by touchscreens.
[1]
https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchscreen-required-hid-top-level-collections
Acked-by: Peter Hutterer
Signed-off-by:
Currently, hid-multitouch can only handle one multitouch collection at
a time. This is an issue for the Dell Canvas, as the Totem (a dial tool)
is also using a multitouch-like collection.
Factor out the multitouch collection data in their own struct.
Acked-by: Peter Hutterer
Signed-off-by:
Currently, hid-multitouch can only handle one multitouch collection at
a time. This is an issue for the Dell Canvas, as the Totem (a dial tool)
is also using a multitouch-like collection.
Factor out the multitouch collection data in their own struct.
Acked-by: Peter Hutterer
Signed-off-by:
If a device has more than one multitouch collection, there is a chance
we need per tool quirks. This is the case for the Totem on the Dell
Canvas.
Note that thesysfs attribute quirks can now get out of sync, but there
should not be much users of it as it's debugging only.
Acked-by: Peter
If a device has more than one multitouch collection, there is a chance
we need per tool quirks. This is the case for the Totem on the Dell
Canvas.
Note that thesysfs attribute quirks can now get out of sync, but there
should not be much users of it as it's debugging only.
Acked-by: Peter
A dial is a tool you place on a multitouch surface which reports its
orientation or a relative angle of rotation when rotating its knob.
Some examples are the Dell Totem (on the Canvas 27"), the Microsoft Dial,
or the Griffin Powermate, though the later can't be put on a touch surface.
We give
Hi,
this is the v4 of my hid-multitouch rewrite series.
Changes are:
- added Peter's rev-by / acked-by
- changed MT_TOOL_MAX value to be 0x0f
- dropped the touch major/minor modifications
Cheers,
Benjamin
Benjamin Tissoires (12):
input: add MT_TOOL_DIAL
HID: multitouch: make sure the
A dial is a tool you place on a multitouch surface which reports its
orientation or a relative angle of rotation when rotating its knob.
Some examples are the Dell Totem (on the Canvas 27"), the Microsoft Dial,
or the Griffin Powermate, though the later can't be put on a touch surface.
We give
Hi,
this is the v4 of my hid-multitouch rewrite series.
Changes are:
- added Peter's rev-by / acked-by
- changed MT_TOOL_MAX value to be 0x0f
- dropped the touch major/minor modifications
Cheers,
Benjamin
Benjamin Tissoires (12):
input: add MT_TOOL_DIAL
HID: multitouch: make sure the
On Wed, Jul 11, 2018 at 09:01:03AM +0100, Colin King wrote:
> From: Colin Ian King
>
> Variable mmc is being assigned but is never used hence it is redundant
> and can be removed.
>
> Cleans up clang warning:
> warning: variable 'mmc' set but not used [-Wunused-but-set-variable]
>
>
On Wed, Jul 11, 2018 at 09:01:03AM +0100, Colin King wrote:
> From: Colin Ian King
>
> Variable mmc is being assigned but is never used hence it is redundant
> and can be removed.
>
> Cleans up clang warning:
> warning: variable 'mmc' set but not used [-Wunused-but-set-variable]
>
>
On 7/13/18 8:07 AM, Vladimir Zapolskiy wrote:
> Remove blkdev_entry_to_request() macro, which remained unused through
> the observable history, also note that it repeats list_entry_rq() macro
> verbatim.
Applied, thanks.
--
Jens Axboe
On 7/13/18 8:07 AM, Vladimir Zapolskiy wrote:
> Remove blkdev_entry_to_request() macro, which remained unused through
> the observable history, also note that it repeats list_entry_rq() macro
> verbatim.
Applied, thanks.
--
Jens Axboe
Daniel Casini got this warn while running a DL task here at RetisLab:
[ 461.137582] [ cut here ]
[ 461.137583] rq->clock_update_flags < RQCF_ACT_SKIP
[ 461.137599] WARNING: CPU: 4 PID: 2354 at kernel/sched/sched.h:967
Daniel Casini got this warn while running a DL task here at RetisLab:
[ 461.137582] [ cut here ]
[ 461.137583] rq->clock_update_flags < RQCF_ACT_SKIP
[ 461.137599] WARNING: CPU: 4 PID: 2354 at kernel/sched/sched.h:967
Remove blkdev_entry_to_request() macro, which remained unused through
the observable history, also note that it repeats list_entry_rq() macro
verbatim.
Signed-off-by: Vladimir Zapolskiy
---
include/linux/blkdev.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/blkdev.h
Remove blkdev_entry_to_request() macro, which remained unused through
the observable history, also note that it repeats list_entry_rq() macro
verbatim.
Signed-off-by: Vladimir Zapolskiy
---
include/linux/blkdev.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/blkdev.h
Hi Linus,
Please pull a little more Kbuild fixes.
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
Hi Linus,
Please pull a little more Kbuild fixes.
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
On 13/07/18 13:55, Aapo Vienamo wrote:
> This happens because sdhci_pltfm_clk_get_max_clock() does not actually
> return the maximum clock rate but the current one, leading to smaller
> clock rates on some platforms. I'll send a patch that fixes this for
> sdhci-tegra. Although this raises the
On 13/07/18 13:55, Aapo Vienamo wrote:
> This happens because sdhci_pltfm_clk_get_max_clock() does not actually
> return the maximum clock rate but the current one, leading to smaller
> clock rates on some platforms. I'll send a patch that fixes this for
> sdhci-tegra. Although this raises the
On 13/07/18 14:17, Aapo Vienamo wrote:
> Implement and use tegra_sdhci_get_max_clock() which returns the true
> maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
Don't you mean sdhci_pltfm_clk_get_max_clock above? Does this function
need fixing then? Or at least should
On 13/07/18 14:17, Aapo Vienamo wrote:
> Implement and use tegra_sdhci_get_max_clock() which returns the true
> maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
Don't you mean sdhci_pltfm_clk_get_max_clock above? Does this function
need fixing then? Or at least should
On Fri, Jul 13, 2018 at 11:28:28AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Jul 12, 2018 at 12:30:01PM -0600, Tycho Andersen wrote:
> > On Thu, Jul 12, 2018 at 08:25:45PM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, Jul 12, 2018 at 12:18:46PM -0600, Tycho Andersen wrote:
> > > > On Thu, Jul
On Fri, Jul 13, 2018 at 11:28:28AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Jul 12, 2018 at 12:30:01PM -0600, Tycho Andersen wrote:
> > On Thu, Jul 12, 2018 at 08:25:45PM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, Jul 12, 2018 at 12:18:46PM -0600, Tycho Andersen wrote:
> > > > On Thu, Jul
> > Currently PCI_BRIDGE_CTL_SERR is being enabled only in ACPI flow.
> > This bit is required for forwarding errors reported by EP devices to
> > upstream device.
> > This patch enables SERR# for Type-1 PCI device.
> >
> > Signed-off-by: Bharat Kumar Gogada
> > ---
> > drivers/pci/pcie/aer.c |
> > Currently PCI_BRIDGE_CTL_SERR is being enabled only in ACPI flow.
> > This bit is required for forwarding errors reported by EP devices to
> > upstream device.
> > This patch enables SERR# for Type-1 PCI device.
> >
> > Signed-off-by: Bharat Kumar Gogada
> > ---
> > drivers/pci/pcie/aer.c |
We are a team, we can process 300+ images per day for you.
If you need any image editing, please let us know.
Photos cut out;
Photos clipping path;
Photos masking;
Photo shadow creation;
Photos retouching;
Beauty Model retouching on skin, face, body;
Glamour retouching;
Products retouching.
We
We are a team, we can process 300+ images per day for you.
If you need any image editing, please let us know.
Photos cut out;
Photos clipping path;
Photos masking;
Photo shadow creation;
Photos retouching;
Beauty Model retouching on skin, face, body;
Glamour retouching;
Products retouching.
We
On 07/13/2018 05:58 AM, Johannes Thumshirn wrote:
Add a driver for the MEN 16z069 Watchdog and Reset Controller IP-Core.
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig | 10 +++
drivers/watchdog/Makefile | 1 +
On 07/13/2018 05:58 AM, Johannes Thumshirn wrote:
Add a driver for the MEN 16z069 Watchdog and Reset Controller IP-Core.
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig | 10 +++
drivers/watchdog/Makefile | 1 +
Pavel Emelyanov writes:
> On 07/12/2018 07:33 PM, Eric W. Biederman wrote:
>>
>> Adrian Reber writes:
>>
>>> The CHECKPOINT_RESTORE configuration option was introduced in 2012 and
>>> combined with EXPERT. CHECKPOINT_RESTORE is already enabled in many
>>> distribution kernels and also part of
Pavel Emelyanov writes:
> On 07/12/2018 07:33 PM, Eric W. Biederman wrote:
>>
>> Adrian Reber writes:
>>
>>> The CHECKPOINT_RESTORE configuration option was introduced in 2012 and
>>> combined with EXPERT. CHECKPOINT_RESTORE is already enabled in many
>>> distribution kernels and also part of
Add braces around macro argument to avoid precedence problems.
This fixes the corresponding checkpatch warning.
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Add braces around macro argument to avoid precedence problems.
This fixes the corresponding checkpatch warning.
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: "Raju P.L.S.S.S.N"
The patch fixes the bug reported by Dan Carpenter.
It removes the unnecessary err check for ‘tcs’ reported by
static checker warning:
drivers/soc/qcom/rpmh-rsc.c:111 tcs_invalidate()
warn: 'tcs' isn't an ERR_PTR
See also:
drivers/soc/qcom/rpmh-rsc.c:178
From: "Raju P.L.S.S.S.N"
The patch fixes the bug reported by Dan Carpenter.
It removes the unnecessary err check for ‘tcs’ reported by
static checker warning:
drivers/soc/qcom/rpmh-rsc.c:111 tcs_invalidate()
warn: 'tcs' isn't an ERR_PTR
See also:
drivers/soc/qcom/rpmh-rsc.c:178
It was discovered that running the ltp openposix_testsuite sigqueue-09-1
test on a certain 8-sock IvyBridge system caused it to have a hard lockup
with a full debug kernel.
[89981.861500] NMI watchdog: Watchdog detected hard LOCKUP on cpu 17
:
[89981.939812] irq event stamp: 1166122
It was discovered that running the ltp openposix_testsuite sigqueue-09-1
test on a certain 8-sock IvyBridge system caused it to have a hard lockup
with a full debug kernel.
[89981.861500] NMI watchdog: Watchdog detected hard LOCKUP on cpu 17
:
[89981.939812] irq event stamp: 1166122
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
index c118d78..fbffa3e 100644
---
This fixes the following checkpatch warnings:
Use #include instead of
Use #include instead of
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
index c118d78..fbffa3e 100644
---
This fixes the following checkpatch warnings:
Use #include instead of
Use #include instead of
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Vanessa Borgmann
Fix errors: space errors, braces
Fix warnings: comment warnings
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 230
1 file changed, 112 insertions(+), 118 deletions(-)
diff
From: Vanessa Borgmann
Fix errors: space errors, braces
Fix warnings: comment warnings
Signed-off-by: Oliver Hübers
Signed-off-by: Vanessa Borgmann
---
drivers/staging/mt7621-pci/pci-mt7621.c | 230
1 file changed, 112 insertions(+), 118 deletions(-)
diff
Commit-ID: afed7bcf9487bb28e2e2b016a195085c07416c0b
Gitweb: https://git.kernel.org/tip/afed7bcf9487bb28e2e2b016a195085c07416c0b
Author: Mark Rutland
AuthorDate: Wed, 11 Jul 2018 10:36:07 +0100
Committer: Ingo Molnar
CommitDate: Fri, 13 Jul 2018 15:23:25 +0200
locking/refcount: Always
Commit-ID: afed7bcf9487bb28e2e2b016a195085c07416c0b
Gitweb: https://git.kernel.org/tip/afed7bcf9487bb28e2e2b016a195085c07416c0b
Author: Mark Rutland
AuthorDate: Wed, 11 Jul 2018 10:36:07 +0100
Committer: Ingo Molnar
CommitDate: Fri, 13 Jul 2018 15:23:25 +0200
locking/refcount: Always
Whilst I'm at it, do we want the option of doing the equivalent of mountat()?
I.e. offering the option to open all the device files used by a superblock
with dfd and AT_* flags in combination with the filename?
David
Whilst I'm at it, do we want the option of doing the equivalent of mountat()?
I.e. offering the option to open all the device files used by a superblock
with dfd and AT_* flags in combination with the filename?
David
On 07/13/2018 09:17 AM, Oscar Salvador wrote:
> On Thu, Jul 12, 2018 at 04:37:26PM -0400, Pavel Tatashin wrote:
>> +static void *sparsemap_buf __meminitdata;
>> +static void *sparsemap_buf_end __meminitdata;
>> +
>> +void __init sparse_buffer_init(unsigned long size, int nid)
>> +{
>> +
On 07/13/2018 09:17 AM, Oscar Salvador wrote:
> On Thu, Jul 12, 2018 at 04:37:26PM -0400, Pavel Tatashin wrote:
>> +static void *sparsemap_buf __meminitdata;
>> +static void *sparsemap_buf_end __meminitdata;
>> +
>> +void __init sparse_buffer_init(unsigned long size, int nid)
>> +{
>> +
On Mon, Mar 05, 2018 at 08:43:41PM +, Tomasz Kramkowski wrote:
> In September last year, Ben Hutchings submitted commit [9547837bdccb]
> for 3.16.48-rc1 and I informed him that it would be useless without
> [3f3752705dbd] (and that maybe [c3883fe06488] would be useful as well).
> Ben dropped
On Mon, Mar 05, 2018 at 08:43:41PM +, Tomasz Kramkowski wrote:
> In September last year, Ben Hutchings submitted commit [9547837bdccb]
> for 3.16.48-rc1 and I informed him that it would be useless without
> [3f3752705dbd] (and that maybe [c3883fe06488] would be useful as well).
> Ben dropped
Implement and use tegra_sdhci_get_max_clock() which returns the true
maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
that it returns the current clock rate of the host instead of the
maximum one, which can lead to unnecessarily small clock rates.
This differs from the
On Thu, Jul 12, 2018 at 04:37:26PM -0400, Pavel Tatashin wrote:
> +static void *sparsemap_buf __meminitdata;
> +static void *sparsemap_buf_end __meminitdata;
> +
> +void __init sparse_buffer_init(unsigned long size, int nid)
> +{
> + BUG_ON(sparsemap_buf);
Why do we need a BUG_ON() here?
Implement and use tegra_sdhci_get_max_clock() which returns the true
maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
that it returns the current clock rate of the host instead of the
maximum one, which can lead to unnecessarily small clock rates.
This differs from the
On Thu, Jul 12, 2018 at 04:37:26PM -0400, Pavel Tatashin wrote:
> +static void *sparsemap_buf __meminitdata;
> +static void *sparsemap_buf_end __meminitdata;
> +
> +void __init sparse_buffer_init(unsigned long size, int nid)
> +{
> + BUG_ON(sparsemap_buf);
Why do we need a BUG_ON() here?
Peter Zijlstra writes:
> On Thu, Jul 12, 2018 at 11:10:58AM -0700, Linus Torvalds wrote:
>> On Thu, Jul 12, 2018 at 11:05 AM Peter Zijlstra wrote:
>> >
>> > The locking pattern is fairly simple and shows where RCpc comes apart
>> > from expectation real nice.
>>
>> So who does RCpc right now
Peter Zijlstra writes:
> On Thu, Jul 12, 2018 at 11:10:58AM -0700, Linus Torvalds wrote:
>> On Thu, Jul 12, 2018 at 11:05 AM Peter Zijlstra wrote:
>> >
>> > The locking pattern is fairly simple and shows where RCpc comes apart
>> > from expectation real nice.
>>
>> So who does RCpc right now
On Fri 13-07-18 19:55:52, ufo19890...@gmail.com wrote:
> From: yuzhoujian
>
> The current oom report doesn't display victim's memcg context during the
> global OOM situation. While this information is not strictly needed, it
> can be really helpful for containerized environments to locate which
On Fri 13-07-18 19:55:52, ufo19890...@gmail.com wrote:
> From: yuzhoujian
>
> The current oom report doesn't display victim's memcg context during the
> global OOM situation. While this information is not strictly needed, it
> can be really helpful for containerized environments to locate which
Hi Linus,
Catalin's out enjoying the sunshine, so I'm sending the fixes for a couple
of weeks (although there hopefully won't be any more!). Summary is in the
tag, but we've got a revert of a previous fix because it broke the build
with some distro toolchains and a preemption fix when detemining
Hi Linus,
Catalin's out enjoying the sunshine, so I'm sending the fixes for a couple
of weeks (although there hopefully won't be any more!). Summary is in the
tag, but we've got a revert of a previous fix because it broke the build
with some distro toolchains and a preemption fix when detemining
The commit
297b64c74385 ("ras: acpi / apei: generate trace event for unrecognized CPER
section")
brought inconsistency in UUID types which are used across the RAS subsystem.
Fix this by moving to use guid_t everywhere.
Cc: Tyler Baicar
Signed-off-by: Andy Shevchenko
---
drivers/ras/ras.c
The commit
297b64c74385 ("ras: acpi / apei: generate trace event for unrecognized CPER
section")
brought inconsistency in UUID types which are used across the RAS subsystem.
Fix this by moving to use guid_t everywhere.
Cc: Tyler Baicar
Signed-off-by: Andy Shevchenko
---
drivers/ras/ras.c
On 07/13/2018 01:17 PM, Ulf Hansson wrote:
On 11 July 2018 at 17:19, Ludovic BARRE wrote:
On 07/05/2018 05:26 PM, Ulf Hansson wrote:
On 12 June 2018 at 15:14, Ludovic Barre wrote:
From: Ludovic Barre
This patch integrates qcom dml feature into mmci_dma file.
Qualcomm Data Mover
On 07/13/2018 01:17 PM, Ulf Hansson wrote:
On 11 July 2018 at 17:19, Ludovic BARRE wrote:
On 07/05/2018 05:26 PM, Ulf Hansson wrote:
On 12 June 2018 at 15:14, Ludovic Barre wrote:
From: Ludovic Barre
This patch integrates qcom dml feature into mmci_dma file.
Qualcomm Data Mover
On Fri, 2018-07-13 at 15:53 +0300, Andy Shevchenko wrote:
> There are new types and helpers that are supposed to be used in new
> code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> While here, update Copyright to reflect this change along with
>
On Fri, 2018-07-13 at 15:53 +0300, Andy Shevchenko wrote:
> There are new types and helpers that are supposed to be used in new
> code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> While here, update Copyright to reflect this change along with
>
On Fri, Jul 13, 2018 at 02:56:24PM +0200, Marco Felsch wrote:
> Currently _regulator_do_disable returns 0 if either the ena_pin nor the
> ops.disbale() isn't present. This assumes that the call was successful
> but it wasn't because disbaling isn't supported at all.
> The last case of the
On Fri, Jul 13, 2018 at 02:56:24PM +0200, Marco Felsch wrote:
> Currently _regulator_do_disable returns 0 if either the ena_pin nor the
> ops.disbale() isn't present. This assumes that the call was successful
> but it wasn't because disbaling isn't supported at all.
> The last case of the
On Mon, Jun 11, 2018 at 05:21:02PM -0700, Ray Jui wrote:
> This patch series improves the Broadcom PAXC support by 1) adding more
> quirks for specific versions of PAXC controllers; 2) adding logic to
> reject internally unconfigured physical functions from the embedded
> network processor acting
On Mon, Jun 11, 2018 at 05:21:02PM -0700, Ray Jui wrote:
> This patch series improves the Broadcom PAXC support by 1) adding more
> quirks for specific versions of PAXC controllers; 2) adding logic to
> reject internally unconfigured physical functions from the embedded
> network processor acting
Add a driver for the MEN 16z069 Watchdog and Reset Controller IP-Core.
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig | 10 +++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/menz69_wdt.c | 175
Add a driver for the MEN 16z069 Watchdog and Reset Controller IP-Core.
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig | 10 +++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/menz69_wdt.c | 175
Currently _regulator_do_disable returns 0 if either the ena_pin nor the
ops.disbale() isn't present. This assumes that the call was successful
but it wasn't because disbaling isn't supported at all.
The last case of the if-chain should return -EINVAL, because disabling
isn't supported by the
Currently _regulator_do_disable returns 0 if either the ena_pin nor the
ops.disbale() isn't present. This assumes that the call was successful
but it wasn't because disbaling isn't supported at all.
The last case of the if-chain should return -EINVAL, because disabling
isn't supported by the
On Fri, 13 Jul 2018 01:43:05 +
Marcel Ziswiler wrote:
> On Mon, 2018-07-02 at 15:16 +0200, Ulf Hansson wrote:
> > On 4 June 2018 at 17:35, Aapo Vienamo wrote:
> > > The sdhci get_max_clock callback is set to
> > > sdhci_pltfm_clk_get_max_clock
> > > and tegra_sdhci_get_max_clock is
On Fri, 13 Jul 2018 01:43:05 +
Marcel Ziswiler wrote:
> On Mon, 2018-07-02 at 15:16 +0200, Ulf Hansson wrote:
> > On 4 June 2018 at 17:35, Aapo Vienamo wrote:
> > > The sdhci get_max_clock callback is set to
> > > sdhci_pltfm_clk_get_max_clock
> > > and tegra_sdhci_get_max_clock is
There are new types and helpers that are supposed to be used in new code.
As a preparation to get rid of legacy types and API functions do
the conversion here.
While here, update Copyright to reflect this change along with previous
one for the topic.
Signed-off-by: Andy Shevchenko
---
There are new types and helpers that are supposed to be used in new code.
As a preparation to get rid of legacy types and API functions do
the conversion here.
While here, update Copyright to reflect this change along with previous
one for the topic.
Signed-off-by: Andy Shevchenko
---
This patchset add support in ASoC to pick up name prefix from the
component nodes when the component does not match the configuration
table provided to the card.
The need for this feature came from the platform I'm working on
(Amlogic A113). On this platform, the card is made of several instances
This patchset add support in ASoC to pick up name prefix from the
component nodes when the component does not match the configuration
table provided to the card.
The need for this feature came from the platform I'm working on
(Amlogic A113). On this platform, the card is made of several instances
Signed-off-by: Jerome Brunet
---
.../devicetree/bindings/sound/name-prefix.txt | 24 ++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/name-prefix.txt
diff --git a/Documentation/devicetree/bindings/sound/name-prefix.txt
Signed-off-by: Jerome Brunet
---
.../devicetree/bindings/sound/name-prefix.txt | 24 ++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/name-prefix.txt
diff --git a/Documentation/devicetree/bindings/sound/name-prefix.txt
When the component does not match the configuration table provided
by the card, let soc-core check the component node for a name prefix
Signed-off-by: Jerome Brunet
---
sound/soc/soc-core.c | 28 +++-
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git
When the component does not match the configuration table provided
by the card, let soc-core check the component node for a name prefix
Signed-off-by: Jerome Brunet
---
sound/soc/soc-core.c | 28 +++-
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git
Hi,
Anson had added the support to disable the switched regulators, but
there were regressions [1] with old dtb's, so the commit was reverted [2].
At all, the support to disable the switch regulators seems to me to be a
good feature. But we have to add a special dt-property to avoid
regressions
Hi,
Anson had added the support to disable the switched regulators, but
there were regressions [1] with old dtb's, so the commit was reverted [2].
At all, the support to disable the switch regulators seems to me to be a
good feature. But we have to add a special dt-property to avoid
regressions
501 - 600 of 944 matches
Mail list logo
