There are situations when we need to modify the delay of a delayed kthread
work. For example, when the work depends on an event and the initial delay
means a timeout. Then we want to queue the work immediately when the event
happens.
This patch implements mod_delayed_kthread_work() as inspired wor
flush_kthread_worker() returns when the currently queued works are proceed.
But some other works might have been queued in the meantime.
This patch adds drain_kthread_worker() that is inspired by
drain_workqueue(). It returns when the queue is completely
empty and warns when it takes too long.
Th
The current kthread worker users call flush() and stop() explicitly.
This function drains the worker, stops it, and frees the kthread_worker
struct in one call.
It is supposed to be used together with create_kthread_worker*() that
allocates struct kthread_worker.
Also note that drain() correctly
We are going to use kthread workers more widely and sometimes we will need
to make sure that the work is neither pending nor running.
This patch implements cancel_*_sync() operations as inspired by
workqueues. Well, we are synchronized against the other operations
via the worker lock, we use del_t
On Tue, May 24, 2016 at 3:13 PM, Laxman Dewangan wrote:
> Implement gpio_get_direction() callback for MAX77620 GPIO.
> This is useful for debugfs and the userspace ABI.
>
> Signed-off-by: Laxman Dewangan
> #include
> +#include
No. This is a sign that something is wrong, no driver should inc
On Mon, May 30, 2016 at 02:11:51PM +0200, Geert Uytterhoeven wrote:
> On Mon, May 30, 2016 at 1:26 PM, Mark Brown wrote:
> > On Thu, May 26, 2016 at 07:25:25PM -, Michal Suchanek wrote:
> >> - fallback to previous behaviour when DMA initialization fails
> >>
> >>+ this has the problem tha
On Tue, May 24, 2016 at 3:13 PM, Laxman Dewangan wrote:
> The MAX77620 have a GPIO pins which can act as open drain or
> push pull mode. Implement support for controlling this from GPIO
> descriptor tables or other hardware descriptions such as
> device tree by implementing the .set_single_ended(
On 05/24/2016 03:30 PM, fu@linaro.org wrote:
From: Fu Wei
This patch add a new enum "spi_nr" and use it in the driver.
Just for code's readability, no functional change.
Signed-off-by: Fu Wei
---
drivers/clocksource/arm_arch_timer.c | 4 ++--
include/clocksource/arm_arch_timer.h | 6 ++
On Sat, May 28, 2016 at 03:57:19PM -0400, George Spelvin wrote:
> +static inline unsigned int fold_hash(unsigned long x, unsigned long y)
> {
> + y ^= x * GOLDEN_RATIO_64;
> + y *= GOLDEN_RATIO_64;
> + return y >> 32;
> }
So does it make sense to use that pattern here too?
This cod
Hello,
this is the first time, when I would like to report kernel problem.
When switching my Debian 8 to kernel 4.4.x, I thought vmware modules
compilation will work smoothly forewer. Unfortunately when I tried 4.5.5
and 4.6, both failed on vmnet module compilation, moreover 4.6 failed
also o
To enable PCI legacy IRQs on platforms booting with ACPI, arch code
should include ACPI specific callbacks that parse and set-up the
device IRQ number, equivalent to the DT boot path. Owing to the current
ACPI core scan handlers implementation, ACPI PCI legacy IRQs bindings
cannot be parsed at devi
This patch implements pci_acpi_scan_root call so that ARM64 can start
using ACPI to setup and enumerate PCI buses.
The implementation of pci_acpi_scan_root() looks up config space regions
through MCFG interface. Then ECAM library is doing a new mapping
and attach generic ECAM ops which are used fo
This patch adds sound over HDMI feature in TDA998x.
The work was inspired in a Linaro repository:
https://git.linaro.org/kernel/linux-linaro-tracking.git/tree/4b131c9bf8af9bc7a25441251f60a8ca7fc69c07
Joao Pinto (3):
tda998x: adding sound support
tda998: adding sound support for Juno in the DT
In order to handle PCI config space regions properly in ACPI, new MCFG
interface is defined which does sanity checks on MCFG table and keeps its
root pointer. The user is able to lookup MCFG regions based on
host bridge root structure and domain:bus_start:bus_end touple.
Use pci_mmcfg_late_init old
>From the functionality point of view this series may be split into the
following logic parts:
1. Export ECAM API and add parent device to pci_config_window
2. Add IO resources handling to PCI core code
3. Support for generic domain assignment based on ACPI
4. New MCFG driver
5. Implement ARM64 ACP
ACPI requires to run acpi_pci_{add|remove}_bus while new PCI bus is created.
This allows to do some ACPI-specific additional configuration, like
PCI hotplug slot enumeration. In order to fulfill these requirements,
we implement arch-specific pcibios_{add|remove}_bus calls
and call acpi_pci_{add|rem
When using ffplay to reproduce video+sound it was noticed that sometimes the
sound was disabled. The cause was an initial EDID checksum error that disabled
the HDMI sound. By adding this tweak, it was noticed that the sound is not
even when initial EDID checksum error ocurres.
Signed-off-by: Joao
This patch adds the sound over HDMI feature to the Juno Device Tree.
Signed-off-by: Joao Pinto
---
arch/arm64/boot/dts/arm/juno-base.dtsi | 92 +++
1 file changed, 78 insertions(+), 14 deletions(-)
diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi
b/arch/arm64/boot/dts/ar
Platforms that have memory mapped IO port (such as ARM64) need special
handling for PCI I/O resources. For host bridge's resource probing case
these resources need to be fixed up with
pci_register_io_range/pci_remap_iospace etc.
The same I/O resources need to be released after hotplug
removal so
On Tue, May 24, 2016 at 3:18 PM, Laxman Dewangan wrote:
> When adding the gpiochip, the GPIO HW drivers' callback get_direction()
> get called in atomic context. Some of the GPIO HW drivers can sleep when
> accessing the register and hence it can create the sleeping call in
> atomic context.
>
>
From: Jayachandran C
Add a parent device field to struct pci_config_window. The parent
is not saved now, but will be useful to save it in some cases.
Specifically in case of ACPI for ARM64, it can be used to setup
ACPI companion and domain.
Since the parent dev is in struct pci_config_window now
PCI core code provides a config option (CONFIG_PCI_DOMAINS_GENERIC)
that allows assigning the PCI bus domain number generically by
relying on device tree bindings, and falling back to a simple counter
when the respective DT properties (ie "linux,pci-domain") are not
specified in the host bridge dev
This patch adds the sound over HDMI feature to the TDA998x driver.
Signed-off-by: Joao Pinto
---
drivers/gpu/drm/i2c/Makefile| 2 +-
drivers/gpu/drm/i2c/tda998x_codec.c | 248 +
drivers/gpu/drm/i2c/tda998x_drv.c | 103 ++
drivers/gpu/drm/i2c/tda998x_dr
From: Jayachandran C
This header will be used from arch/arm64 for ACPI PCI implementation
so it needs to be moved out of drivers/pci.
Update users of the header file to use the new name. No functional
changes.
Signed-off-by: Jayachandran C
---
drivers/pci/ecam.c | 3 +-
driv
This patch series adds support for selecting iio devices/triggers by numeric id
rather than just name. This is useful because the names are not actually
guaranteed to be unique.
Changes since v3:
* Rebase on top of latest jic23/testing
* Fix handling of --trigger-num 0. Initialize trig_num to -1 a
We need to release I/O resources so that the same I/O resources
can be allocated again (pci_remap_iospace), like in PCI hotplug removal
scenario. Therefore this patch implements new pci_unmap_iospace call which
unmaps I/O space as the symmetry to pci_remap_iospace.
Signed-off-by: Sinan Kaya
Signe
Signed-off-by: Crestez Dan Leonard
---
tools/iio/iio_generic_buffer.c | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/tools/iio/iio_generic_buffer.c b/tools/iio/iio_generic_buffer.c
index 3f16e9f..0e8a1f7 100644
--- a/tools/iio/iio_generic
This makes it possible to distinguish between iio devices with the same
name.
Signed-off-by: Crestez Dan Leonard
---
tools/iio/iio_generic_buffer.c | 69 +++---
1 file changed, 51 insertions(+), 18 deletions(-)
diff --git a/tools/iio/iio_generic_buffer.c b/to
On Mon, May 30, 2016 at 02:03:26PM +0200, Gerd Hoffmann wrote:
> Needed for multihead setups where we can have disabled
> outputs and therefore plane->crtc can be NULL.
>
> Signed-off-by: Gerd Hoffmann
See my reply in the other thread, but I think you have a more fundamental
issue here. I droppe
This will clean (disable buffer/trigger/channels) when doing
something like a CTRL-C. Otherwise restarting generic_buffer requires a
manual echo 0 > buffer/enable
This also cleanup up all the code freeing string buffers at
the end of main. We initialize all pointers to NULL so that cleanup can
all
On Mon, May 30, 2016 at 12:40:47PM +0530, Pramod Kumar wrote:
> Add DT binding doc for Broadcom MDIO bus mutiplexer driver.
>
> Signed-off-by: Pramod Kumar
> ---
> .../bindings/net/brcm,mdio-mux-iproc.txt | 64
> ++
> 1 file changed, 64 insertions(+)
> create mode
On 30/05/2016 11:32, Pali Rohár wrote:
> On Friday 27 May 2016 14:11:11 Gabriele Mazzotta wrote:
>> On 22/05/2016 13:50, Pali Rohár wrote:
>>> This patch exports standard hwmon pwmX_enable sysfs attribute for enabling
>>> or disabling automatic fan control by BIOS. Standard value "1" is for
>>> dis
On 05/28/2016 11:54 AM, Krzysztof Kozlowski wrote:
>
> The clock changes can go to clock tree. ARM changes to samsung-soc tree.
> Please provide me a tag with include/dt-bindings/clock commits so I can
> merge it.
I applied the clock tree patches and here is the tag for the three
include/dt-bindin
Hello,
On 30 May 2016 at 17:03, Mark Brown wrote:
> On Mon, May 30, 2016 at 02:11:51PM +0200, Geert Uytterhoeven wrote:
>> On Mon, May 30, 2016 at 1:26 PM, Mark Brown wrote:
>> > On Thu, May 26, 2016 at 07:25:25PM -, Michal Suchanek wrote:
>> >> - fallback to previous behaviour when DMA ini
I concur with Jani on all points, just want to follow-up here.
On Mon, May 30, 2016 at 4:46 PM, Jani Nikula wrote:
>> Many of the facts mentioned above have been covered in my POC at
>> https://github.com/return42/sphkerneldoc ... On others,
>> like 5. I'am working on
>>
>>> I've had a few m
This bug was found by strace test suite.
Fixes: 6b526ed70cf1 ("btrfs: introduce device delete by devid")
Signed-off-by: Dmitry V. Levin
---
include/uapi/linux/btrfs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
index
On Wed 2016-05-25 10:58:38, Miroslav Benes wrote:
> On Mon, 23 May 2016, Jessica Yu wrote:
>
> > +++ Petr Mladek [23/05/16 17:54 +0200]:
> > > There was a long discussion about a possible race with sysfs, kobjects
> > > when removing an unused livepatch, see
> > > https://lkml.kernel.org/g/%3c1462
On 30/05/16 05:19, HS Liao wrote:
This patch is first version of Mediatek Command Queue(CMDQ) driver. The
CMDQ is used to help read/write registers with critical time limitation,
such as updating display configuration during the vblank. It controls
Global Command Engine (GCE) hardware to achiev
On Thu, May 26, 2016 at 11:55:14AM +0530, Viresh Kumar wrote:
> On 25-05-16, 19:52, Steve Muckle wrote:
> > Cpufreq governors may need to know what a particular target frequency
> > maps to in the driver without necessarily wanting to set the frequency.
> > Support this operation via a new cpufreq
I clearly missed the !policy->fast_switch_enabled check in sugov_limit() and so
the confusion.
On 30-05-16, 16:25, Rafael J. Wysocki wrote:
> On Mon, May 30, 2016 at 12:18 PM, Viresh Kumar
> wrote:
> > Suppose this is the current range of frequencies supported by a
> > driver: 200, 400, 600, 800
Hillf Danton writes:
>> diff --git a/mm/memory.c b/mm/memory.c
>> index 15322b73636b..a01db5bc756b 100644
>> --- a/mm/memory.c
>> +++ b/mm/memory.c
>> @@ -292,23 +292,24 @@ void tlb_finish_mmu(struct mmu_gather *tlb, unsigned
>> long start, unsigned long e
>> * handling the additional races i
On Mon, May 30, 2016 at 05:59:33PM +0800, Jason Wang wrote:
>
>
> On 2016年05月23日 18:43, Michael S. Tsirkin wrote:
> >This is in response to the proposal by Jason to make tun
> >rx packet queue lockless using a circular buffer.
> >My testing seems to show that at least for the common usecase
> >in
On Monday, May 30, 2016 5:14:22 PM CEST Tomasz Nowicki wrote:
> + bsz = 1 << pci_generic_ecam_ops.bus_shift;
> + cfgres.start = root->mcfg_addr + bus_res->start * bsz;
> + cfgres.end = cfgres.start + resource_size(bus_res) * bsz - 1;
> + cfgres.flags = IORESOURCE_MEM;
> +
On Mon, May 30, 2016 at 8:59 PM, Chen-Yu Tsai wrote:
> On Mon, May 30, 2016 at 7:34 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 29-05-16 09:04, Chen-Yu Tsai wrote:
>>>
>>> The MMC clock timings were incorrectly calculated, when the conversion
>>> from delay value to delay phase was done.
>>>
>>> The
There are nine copies of the _rtl88ee_read_adapter_info() function,
and most but not all of them cause a build warning in some configurations:
rtl8192de/hw.c: In function '_rtl92de_read_adapter_info':
rtl8192de/hw.c:1767:12: error: 'hwinfo' may be used uninitialized in this
function [-Werror=mayb
On Sun, May 29, 2016 at 8:46 PM, Hector Martin "marcan"
wrote:
> On 2016-05-30 11:16, Kees Cook wrote:
>> On Sun, May 29, 2016 at 10:59 AM, Hector Martin wrote:
>>> On Mon, May 23, 2016 at 3:15 PM, Emese Revfy wrote:
+/*
+ * Copyright 2012-2016 by the PaX Team
+ * Copyright 2016
Hi Pascal,
On 05/30/2016 07:46 AM, Pascal Sachs wrote:
From: David Frey
This driver implements support for the Sensirion SHT3x-DIS chip,
a humidity and temperature sensor. Temperature is measured
in degrees celsius, relative humidity is expressed as a percentage.
In the sysfs interface, all va
gcc warns about qed_fill_link possibly accessing uninitialized data:
drivers/net/ethernet/qlogic/qed/qed_main.c: In function 'qed_fill_link':
drivers/net/ethernet/qlogic/qed/qed_main.c:1170:35: error: 'link_caps' may be
used uninitialized in this function [-Werror=maybe-uninitialized]
While this
On Mon, May 30, 2016 at 02:47:53AM -0400, Jason Wang wrote:
> We don't stop rx polling socket during rx processing, this will lead
> unnecessary wakeups from under layer net devices (E.g
> sock_def_readable() form tun). Rx will be slowed down in this
> way. This patch avoids this by stop polling so
On Mon, May 30, 2016 at 05:28:10PM +0200, Michal Suchanek wrote:
> On 30 May 2016 at 17:03, Mark Brown wrote:
> > I really don't think it's worth caring too much about cases where the
> > DMA driver hasn't been compiled in, it's not like SPI is the only thing
> It's what the driver did to start
The cfs_rq->avg.last_update_time is initialize to 0 with the main effect
that the 1st sched_entity that will be attached, will keep its
last_update_time set to 0 and will attached once again during the
enqueue.
Initialize cfs_rq->avg.last_update_time to 1 instead.
Signed-off-by: Vincent Guittot
-
On 27 May 2016 at 22:38, Dietmar Eggemann wrote:
> On 27/05/16 18:16, Vincent Guittot wrote:
>> On 27 May 2016 at 17:48, Dietmar Eggemann wrote:
>>> On 25/05/16 16:01, Vincent Guittot wrote:
The cfs_rq->avg.last_update_time is initialize to 0 with the main effect
that the 1st sched_enti
On Mon, May 30, 2016 at 02:47:54AM -0400, Jason Wang wrote:
> We always poll tx for socket, this is sub optimal since:
>
> - it will be only used when we exceed the sndbuf of the socket.
> - since we use two independent polls for tx and vq, this will slightly
> increase the waitqueue traversing
On Mon, May 30, 2016 at 03:13:40PM +0200, Geert Uytterhoeven wrote:
> > The benefit is negligible and the results are within the noise but each
> > cycle counts.
> >
> > Signed-off-by: Mel Gorman
> > Cc: Vlastimil Babka
> > Cc: Jesper Dangaard Brouer
> > Signed-off-by: An
The patch
regulator: max8973: Fix setting ramp delay
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sen
Em Tue, May 24, 2016 at 12:52:36PM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> Add basic plumbing for TopDown in perf stat
>
> TopDown is intended to replace the frontend cycles idle/
> backend cycles idle metrics in standard perf stat output.
> These metrics are not reliable in many work
On 05/30/2016 10:26 AM, Arnd Bergmann wrote:
There are nine copies of the _rtl88ee_read_adapter_info() function,
and most but not all of them cause a build warning in some configurations:
rtl8192de/hw.c: In function '_rtl92de_read_adapter_info':
rtl8192de/hw.c:1767:12: error: 'hwinfo' may be use
Em Sun, May 29, 2016 at 12:15:13AM +0900, Masami Hiramatsu escreveu:
> Introduce filename__readable to check readability by opening
> the file directly. Since the access(R_OK) just checks the
> readability based on real UID/GID, it is ignored that the
> effective UID/GID and capabilities for some s
> Which is a Broadwell-U, dual-core, 14 nm.
>
> [root@jouet linux]# echo 0 > /proc/sys/kernel/nmi_watchdog
> [root@jouet linux]# perf stat --topdown -a usleep 1
> System does not support topdown
> [root@jouet linux]# cat /proc/sys/kernel/nmi_watchdog
> 0
> [root@jouet linux]#
>
> Please advise.
On Mon, May 30, 2016 at 03:32:45PM +0800, Xing Zheng wrote:
> Hi,
> Could any guys help me to review this patch?
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
on so unless there is some reason for urg
Em Mon, May 30, 2016 at 01:03:17PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sun, May 29, 2016 at 12:15:13AM +0900, Masami Hiramatsu escreveu:
> > Introduce filename__readable to check readability by opening
> > the file directly. Since the access(R_OK) just checks the
> > readability based on
On Tue, May 17, 2016 at 07:40:45AM -0700, Eduardo Valentin wrote:
> >
> > Please remove these spaces.
> > BTW, there are also some warnings in the other patches, please fix the
> > checkpatch warnings/errors.
All the checkpatch complaints in this series are due to existing
problems. As you can se
Peter Zijlstra wrote:
> On Sat, May 28, 2016 at 03:57:19PM -0400, George Spelvin wrote:
>> +static inline unsigned int fold_hash(unsigned long x, unsigned long y)
>> {
>> +y ^= x * GOLDEN_RATIO_64;
>> +y *= GOLDEN_RATIO_64;
>> +return y >> 32;
>> }
> So does it make sense to use tha
Em Mon, May 30, 2016 at 12:54:58PM +0900, Namhyung Kim escreveu:
> Hi Masami,
>
> On Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu wrote:
> > Hi,
> >
> > Here is the 9th version of the patchset for probe-cache and
> > initial SDT support.
> >
> > The previous version is here; https://
On Sat, May 28, 2016 at 10:57:33PM +0200, Christer Weinigel wrote:
> On 05/27/2016 08:36 PM, Mark Brown wrote:
> > It is reasonable to provide and document something here but when there's
> > some fairly simple and obvious better things we could be doing it should
> > be those rather than the lega
Hi Kevin,
Am Donnerstag, den 26.05.2016, 11:42 -0700 schrieb Kevin Hilman:
[...]
> > Personally, I'd prefer if the driver could switch to only using
> > reset_control_reset(rstc);
>
> Then what would happen if that same driver is used on platforms that
> have ->assert and ->deassert but no -r
On Mon, May 30, 2016 at 9:08 PM, Arnd Bergmann wrote:
> On Monday, May 30, 2016 5:14:22 PM CEST Tomasz Nowicki wrote:
>> + bsz = 1 << pci_generic_ecam_ops.bus_shift;
>> + cfgres.start = root->mcfg_addr + bus_res->start * bsz;
>> + cfgres.end = cfgres.start + resource_size(bus_res
On Mon, May 30, 2016 at 11:55:19AM +0300, Peter Ujfalusi wrote:
> The pdmclk is needed for McPDM. It is generated by twl6040.
Please don't resubmit already applied patches. If any incremental
updates are needed please send them as such.
signature.asc
Description: PGP signature
Em Mon, May 30, 2016 at 09:04:02AM -0700, Andi Kleen escreveu:
> > Which is a Broadwell-U, dual-core, 14 nm.
> >
> > [root@jouet linux]# echo 0 > /proc/sys/kernel/nmi_watchdog
> > [root@jouet linux]# perf stat --topdown -a usleep 1
> > System does not support topdown
> > [root@jouet linux]# cat /p
On Thu, May 26, 2016 at 12:13:41PM +0530, Viresh Kumar wrote:
> On 25-05-16, 19:53, Steve Muckle wrote:
> > Support the new resolve_freq cpufreq callback which resolves a target
> > frequency to a driver-supported frequency without actually setting it.
>
> And here is the first abuser of this API
Em Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu escreveu:
> Hi,
>
> Here is the 9th version of the patchset for probe-cache and
> initial SDT support.
Ok, for completeness sake: Where does one learn more about "SDT", I
couldn't find a description of this in this patchkit, /me goes goo
On Mon, May 30, 2016 at 11:36:07AM +0200, Vlastimil Babka wrote:
> On 05/30/2016 03:39 AM, Minchan Kim wrote:
> >After isolation, VM calls migratepage of driver with isolated page.
> >The function of migratepage is to move content of the old page to new page
> >and set up fields of struct page newp
Hi Ram,
On 05/28/2016 05:36 AM, Ram Pai wrote:
> On Tue, May 24, 2016 at 06:45:12PM +0530, Shreyas B. Prabhu wrote:
[snip]
>> @@ -230,11 +236,18 @@ static DEVICE_ATTR(fastsleep_workaround_applyonce,
>> 0600,
>> show_fastsleep_workaround_applyonce,
>> stor
On 30/05/16 10:36, Pali Rohár wrote:
Hi Peter! Thank you for information! Are you able to try to call that
function on some old kernel (e.g. 3.12 or 3.14) to verify that it is
caused only and only by that function?
I have tried to use my old 3.19.0 kernel that did not have the problem
but now i
On Mon, May 30, 2016 at 12:06:18PM -0400, George Spelvin wrote:
> Not quite. The fold_hash() you quote is used only on 64-bit systems,
> which can be assumed to have a reasonable 64-bit multiply. On 32-bit
> platforms, I avoid using GOLDEN_RATIO_64 at all, since 64x64-bit
> multiplies are so expe
Em Mon, May 30, 2016 at 01:22:52PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu escreveu:
> > Hi,
> >
> > Here is the 9th version of the patchset for probe-cache and
> > initial SDT support.
>
> Ok, for completeness sake: Where does one l
On Thu, May 26, 2016 at 12:46:29PM +0530, Viresh Kumar wrote:
> On 25-05-16, 19:53, Steve Muckle wrote:
> > The slow-path frequency transition path is relatively expensive as it
> > requires waking up a thread to do work. Should support be added for
> > remote CPU cpufreq updates that is also expen
> + if (IS_ENABLED(CONFIG_QED_SRIOV) && !IS_PF(hwfn->cdev)) {
> + qed_vf_get_link_params(hwfn, params);
> + qed_vf_get_link_state(hwfn, link);
> + qed_vf_get_link_caps(hwfn, link_caps);
> +
> + return 0;
> + }
The IS_ENABLED here seems a bit
Am 30.05.2016 um 16:46 schrieb Jani Nikula :
> On Mon, 30 May 2016, Markus Heiser wrote:
>> Here my 5cents about Jani's patch series:
>>
>> 1. Migration implementations should not be a part of the kernel tree
>
> If you're referring to the conversion scripts, I don't care either
> way. It's pr
The series adds a driver that creates a drm_bridge and a drm_connector for the
LVDS to DP++ display bridge of the GE B850v3. There are two physical bridges on
the video signal pipeline: a STDP4028(LVDS to DP) and a STDP2690(DP to DP++).
However the physical bridges are automatically configured by t
This driver creates a drm_bridge and a drm_connector for the LVDS to DP++
display bridge of the GE B850v3(imx6q-b850v3.dts). There are two physical
bridges on the video signal pipeline: a STDP4028(LVDS to DP) and a
STDP2690(DP to DP++). However the physical bridges are automatically
configured by t
Configure the GE B850v3 to use the LVDS/DP++ bridge.
Signed-off-by: Peter Senna Tschudin
---
arch/arm/boot/dts/imx6q-b850v3.dts | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/imx6q-b850v3.dts
b/arch/arm/boot/dts/imx6q-b850v3.dts
index 88a7
Devicetree bindings documentation for the GE B850v3 LVDS/DP++
display bridge.
Signed-off-by: Peter Senna Tschudin
---
.../devicetree/bindings/ge/b850v3_lvds_dp.txt | 38 ++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ge/b850v3_l
Configure the IPU assignment order to assign one IPU per external
display. A single IPU can drive multiple external displays but there are
resolution restrictions. After this patch the GPU is capalbe of driving two
Full-HD monitors.
Signed-off-by: Peter Senna Tschudin
---
arch/arm/boot/dts/imx6q
Add support to attach a drm_bridge to imx-ldb in addition to
existing support to attach a LVDS panel.
Signed-off-by: Peter Senna Tschudin
---
drivers/gpu/drm/imx/imx-ldb.c | 75 +++
1 file changed, 54 insertions(+), 21 deletions(-)
diff --git a/drivers/gp
The config set is prepared by collecting
all configs from config files (i.e. user config
~/.perfconfig and system config $(sysconfdir)/perfconfig)
so the config set contains all config key-value pairs.
We need to use it as global variable to share it.
And in near future, the variable will be handl
Instead of perf_config(), This function initialize config set
collecting all configs from config files (i.e. user config
~/.perfconfig and system config $(sysconfdir)/perfconfig).
If there are the same config variable both user and system
config file, user config has higher priority than system co
Everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But we need to use 'struct perf_config_set config_set' variable
that already contains all config key-value pairs
to avoid this repetitive work
When first calling perf_config(), config set is
initialized collecting both user and system config files
(i.e. user config ~/.perfconfig and system config
$(sysconfdir)/perfconfig) so config set contains
not only user config but also system config key-value pairs.
(User config has higher priority t
show_config() was reimplemented using perf_config()
so it isn't needed to use perf_config_set__new() at cmd_config().
And perf_config_set__delete() isn't needed at cmd_config() because of
calling the function at run_builtin() when a sub-command finished.
And it isn't also needed to declare 'config
This function deleted allocated config set but
the global variable 'config_set' is used all around
so this directly remove 'config_set' instead of using local variable 'set'.
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Alexander Shishkin
Signed-off-by: Taeung Song
---
tools/perf/
Old show_config() directly use config set so
there are many duplicated code with perf_config_set__iter().
So reimplement show_config() using perf_config() that use
perf_config_set__iter() with config set that already
contains all configs.
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc:
Everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But we need to use the config set that already contains all config
key-value pairs to avoid this repetitive work reading the config files
in pe
This patch updates the driver to support 64-bit DMA addressing.
Signed-off-by: Nava kishore Manne
---
Changes for v4:
-Used boolen property insted of addrwith property in the DT
as suggested by Arnd Bergmann.
-Adopt the DT relevant changes into the
On Mon, May 30, 2016 at 1:39 PM, Peter Senna Tschudin
wrote:
> Configure the IPU assignment order to assign one IPU per external
> display. A single IPU can drive multiple external displays but there are
> resolution restrictions. After this patch the GPU is capalbe of driving two
I think you mea
On Fri, May 27, 2016 at 01:41:02PM +0800, Wanpeng Li wrote:
> 2016-05-26 10:53 GMT+08:00 Steve Muckle :
> > The slow-path frequency transition path is relatively expensive as it
> > requires waking up a thread to do work. Should support be added for
> > remote CPU cpufreq updates that is also expen
Only tangentially related, but... that bug had been discussed,
without any results: the fallback in ima_d_path() to ->d_name.name is
completely broken. There is no warranty whatsoever that dentry won't be
renamed, with its earlier (too long to be embedded into dentry itself)
->d_name.name
On 05/30/2016 06:29 AM, Neil Armstrong wrote:
Add watchdog specific driver for Amlogic Meson GXBB SoC.
Signed-off-by: Neil Armstrong
---
drivers/watchdog/Makefile | 1 +
drivers/watchdog/meson_gxbb_wdt.c | 277 ++
2 files changed, 278 insertions
On Mon, May 30, 2016 at 1:39 PM, Peter Senna Tschudin
wrote:
> +&mux2_i2c2 {
> + status = "okay";
> + clock-frequency = <10>;
> +
> + b850v3_lvds_dp_bridge {
> + compatible = "ge,b850v3_lvds_dp";
> + #address-cells = <1>;
> + #size-c
On unplugging this USB Touchscreen, everytime I get either:
[ 161.596055] BUG: unable to handle kernel NULL pointer dereference at 0015
[ 161.596093] IP: [] get_next_timer_interrupt+0x80/0x270
or
[ 155.892061] BUG: unable to handle kernel paging request at 30303046
[ 155.892101] IP: [] get
401 - 500 of 1124 matches
Mail list logo
