The EVM consists of a system on module (SOM) and baseboard, and LCD.
This patch adds a DTSI file for the SOM and baseboard separately,
then a wrapper to combine them and specify processor type and a
LCD information.
Signed-off-by: Adam Ford
---
V2: Make node names more generic and label names mo
On Tue, Jan 22, 2019 at 04:48:26PM +0200, Joonas Lahtinen wrote:
> According to our IOMMU folks there exists some desire to be able to assign
> the iGFX device aka have intel_iommu=on instead of intel_iommu=igfx_off
> due to how the devices might be grouped in IOMMU groups. Even when you
> would no
On Tue, Jan 22, 2019 at 5:37 PM Keith Busch wrote:
>
> On Sun, Jan 20, 2019 at 05:16:05PM +0100, Rafael J. Wysocki wrote:
> > On Sat, Jan 19, 2019 at 10:01 AM Greg Kroah-Hartman
> > wrote:
> > >
> > > If you do a subdirectory "correctly" (i.e. a name for an attribute
> > > group), that's fine.
>
On Tue, Jan 22, 2019 at 04:22:38PM +0800, Peter Xu wrote:
> On Mon, Jan 21, 2019 at 10:55:36AM -0500, Jerome Glisse wrote:
> > On Mon, Jan 21, 2019 at 03:57:01PM +0800, Peter Xu wrote:
> > > The idea comes from a discussion between Linus and Andrea [1].
> > >
> > > Before this patch we only allow
[Adding Tom to CC]
Dear Thomas, dear Tom,
On 01/14/19 11:09, Paul Menzel wrote:
> On 01/11/19 21:43, Thomas Gleixner wrote:
>
>> On Mon, 7 Jan 2019, Paul Menzel wrote:
>>> On 01/07/19 16:24, Thomas Gleixner wrote:
> Linux 4.19.13 from Debian Sid/unstable logs the message below on the
On Tue, Jan 22, 2019 at 5:51 PM Rafael J. Wysocki wrote:
>
> On Tue, Jan 22, 2019 at 5:37 PM Keith Busch wrote:
> >
> > On Sun, Jan 20, 2019 at 05:16:05PM +0100, Rafael J. Wysocki wrote:
> > > On Sat, Jan 19, 2019 at 10:01 AM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > If you do a subdirecto
Hi,
The first patch in this series fixes a potential NULL pointer
dereference by adding a NULL check. A tag for stable has been
added for this patch.
The second patch promotes the use of struct_size() in devm_kzalloc().
Both issues were detected with the help of Coccinelle.
Gustavo A. R. Silva
On Mon, Jan 21, 2019 at 02:50:49PM +0100, Roberto Sassu wrote:
> On 1/21/2019 1:37 PM, Jarkko Sakkinen wrote:
> > 3. The would be nothing wrong exposing struct tpm_chip in
> > include/linux/tpm.h. I would be totally fine with that.
>
> Should I do it in a separate patch (before 5/5)?
Yes.
>
There is a potential NULL pointer dereference in case devm_kzalloc()
fails and returns NULL.
Fix this by adding a NULL check on *lookup*
This bug was detected with the help of Coccinelle.
Fixes: b2e6392f ("i2c: gpio: Convert to use descriptors")
Cc: sta...@vger.kernel.org
Signed-off-by: Gust
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance = devm_kzalloc(dev, si
[[PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.] On 22/01/2019
(Tue 10:21) Sven Van Asbroeck wrote:
> Fieldbus device (client) adapters allow data exchange with a PLC aka.
> "Fieldbus Controller" over a fieldbus (Profinet, FLNet, etc.)
>
> They are typically used when a Linux device
On Sat, Jan 19, 2019 at 08:36:36PM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin
> ---
Acked-by: Charles Keepax
Thanks,
Charles
On Tue, Jan 22, 2019 at 05:15:51PM +0100, Oleg Nesterov wrote:
> I don't know... tried to google, found nothing.
>
> the comment in /usr/include/sys/ucontext.h mentions SysV/i386 ABI + historical
> reasons, this didn't help.
So I'm being told by one of the psABI folks that this is not really
writ
On Tue, Jan 22, 2019 at 11:29:52PM +0800, Changbin Du wrote:
> The commit c73da3f ("KVM: VMX: Properly handle dynamic VM Entry/Exit
> controls") has a typo that cause invalid vmexit controls. The
> VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL is against _vmentry_control.
>
> KVM: entry failed, hardware err
On Tue, Jan 22, 2019 at 05:39:35PM +0800, Peter Xu wrote:
> On Mon, Jan 21, 2019 at 09:05:35AM -0500, Jerome Glisse wrote:
>
> [...]
>
> > > + change_protection(dst_vma, start, start + len, newprot,
> > > + !enable_wp, 0);
> >
> > So setting dirty_accountable bring us to
On Mon, Jan 21, 2019 at 7:23 PM Robin Murphy wrote:
>
> On 21/01/2019 05:53, Vivek Gautam wrote:
> > A number of arm_smmu_domain's attributes can be assigned based
> > on the iommu domains's attributes. These local attributes better
> > be managed by a bitmap.
> > So remove boolean flags and move
This patch introduces the support for VIRTIO_F_ORDER_PLATFORM.
When this feature is negotiated, driver will use the barriers
suitable for hardware devices.
Signed-off-by: Tiwei Bie
---
drivers/virtio/virtio_ring.c | 8
include/uapi/linux/virtio_config.h | 6 ++
2 files changed
On Tue, Jan 22, 2019 at 07:47:50AM -0800, Guenter Roeck wrote:
> On Tue, Jan 22, 2019 at 11:48:36AM +0200, Matti Vaittinen wrote:
> > Initial support for watchdog block included in ROHM BD70528
> > power management IC.
> >
> > Configurations for low power states are still to be checked.
> >
> > S
> + PERF_OUTPUT_CODE_PAGE_SIZE = 1UL << 32,
That won't work on 32bit. You need 1ULL
Also might want to audit that noone puts these flags into
an int.
-Andi
Hi,
thanks for quick reply, this seems to fix it
no crash, xserver works, like revert of the commit...pushed the fix to below
github-repo
regards Frank
> Gesendet: Dienstag, 22. Januar 2019 um 17:49 Uhr
> Von: "Joerg Roedel"
> An: "Frank Wunderlich"
> Cc: "Matthias Brugger" ,
> io...@lists
Am 22.01.19 um 17:56 schrieb Paul Gortmaker:
> [[PATCH v7 1/6] fieldbus_dev: add Fieldbus Device subsystem.] On 22/01/2019
> (Tue 10:21) Sven Van Asbroeck wrote:
>
>> Fieldbus device (client) adapters allow data exchange with a PLC aka.
>> "Fieldbus Controller" over a fieldbus (Profinet, FLNet, e
On Tue, Jan 15, 2019 at 10:15:05AM +, Patrick Bellasi wrote:
> @@ -342,11 +350,24 @@ static void sugov_iowait_boost(struct sugov_cpu
> *sg_cpu, u64 time,
> return;
> sg_cpu->iowait_boost_pending = true;
>
> + /*
> + * Boost FAIR tasks only up to the CPU clamped u
On Tue 22-01-19 16:27:53, Dmitry Vyukov wrote:
> On Mon, Jan 21, 2019 at 9:37 AM Jan Kara wrote:
> >
> > On Thu 17-01-19 14:18:56, Dmitry Vyukov wrote:
> > > On Wed, Jan 16, 2019 at 5:28 PM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > On Wed, Jan 16, 2019 at 12:48:41PM +0100, Dmitry Vyukov wro
On 2019-01-22 17:25:03 [+0100], Greg Kroah-Hartman wrote:
> > > }
> > >
> > > static void bdi_debug_unregister(struct backing_dev_info *bdi)
> > > {
> > > - debugfs_remove(bdi->debug_stats);
> > > - debugfs_remove(bdi->debug_dir);
> > > + debugfs_remove_recursive(bdi->debug_dir);
> >
> > this
On Tue, Jan 22, 2019 at 04:21:50PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
What about wanting to make the debugfs all
On Wed, Jan 16, 2019 at 10:18:08PM +0100, Andreas Kemnade wrote:
> On the GTA04 mobile phone, it was observed that the gps was powered
> on sometimes intially. Generally a reboot without powering the device
> off (direct reset of the processor, reboot from a system where gps
> power toggle was done
On Tue, Jan 22, 2019 at 05:43:52PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 22, 2019 at 04:38:26PM +, Mark Brown wrote:
> > No, it also fails if there's already something with the same name in
> > debugfs which can happen as as a result of configuration. This gets
> > confusing for user
Make sure to put the receiver in hibernate mode in case it is already
active during probe in order to avoid wasting power until first open or
suspend.
This can happen, for example, after a reset or non-clean shutdown, and
possibly also due to glitches during power-on.
Reported-by: Andreas Kemnade
These patches fixes an issue where the sirf wakeup interrupt was
prematurely enabled during probe. As Andreas suggested, we should also
make sure that the receiver is indeed suspended at probe (to avoid
wasting power until first open or suspend).
Johan
Johan Hovold (3):
gnss: sirf: fix prematu
The active flag is of type bool so drop the redundant double negation
when storing the gpio state.
Signed-off-by: Johan Hovold
---
drivers/gnss/sirf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gnss/sirf.c b/drivers/gnss/sirf.c
index f9a9d00dec98..59cde7e923b8 10
Make sure the receiver is powered (and booted) before enabling the
wakeup interrupt to avoid spurious interrupts due to a floating input.
Similarly, disable the interrupt before powering off on probe errors and
on unbind.
Fixes: d2efbbd18b1e ("gnss: add driver for sirfstar-based receivers")
Cc: s
On Tue, Jan 22, 2019 at 09:21:02AM -0800, Sean Christopherson wrote:
> On Tue, Jan 22, 2019 at 04:21:50PM +0100, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do s
On Thu, 2019-01-10 at 17:48 +0200, 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.
>
> Signed-off-by: Andy Shevchenko
Acked-by: Srinivas Pandruvada
>
On Tue 22-01-19 17:27:49, Greg KH wrote:
> On Tue, Jan 22, 2019 at 05:07:01PM +0100, Michal Hocko wrote:
[...]
> > sounds like a poor design goal to me but not mine code to maintain so...
>
> The design goal was to make it as simple as possible to use, and that
> includes "you do not care about th
On Mon, Jan 21, 2019 at 08:45:39PM +, Rasmus Villemoes wrote:
> The watchdog framework takes care of feeding a hardware watchdog until
> userspace opens /dev/watchdogN. If that never happens for some reason
> (buggy init script, corrupt root filesystem or whatnot) but the kernel
> itself is fin
$1,000,000.00 dollars has been donated to you by Maureen David Kaltschmidt who
won the Powerball Jackpot of $758.7 million Dollars. Contact her via Email:
maureendavidkaltschmidt...@gmail.com for more details
Hello everyone,
Sincere apologies for chiming in a bit late here, but was off due to
some health issues.
Also, adding Daniel Vetter to the mix, since he has been one of the
core guys who shaped up dma-buf as it is today.
On Tue, 22 Jan 2019 at 02:51, Andrew F. Davis wrote:
>
> On 1/21/19 5:22 A
On Tue, Jan 22, 2019 at 07:10:23PM +0200, Matti Vaittinen wrote:
> On Tue, Jan 22, 2019 at 07:47:50AM -0800, Guenter Roeck wrote:
> > On Tue, Jan 22, 2019 at 11:48:36AM +0200, Matti Vaittinen wrote:
> > > Initial support for watchdog block included in ROHM BD70528
> > > power management IC.
> > >
On Tue, Jan 22, 2019 at 04:17:57PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Leon Romanovsky
> Cc: Doug Ledford
It has been observed that trace reading thread runs on the same hw thread
most of the time during perf record sampling collection. This scheduling
layout leads up to 30% profiling overhead in case when some cpu intensive
workload fully utilizes a large server system with NUMA. Overhead usually
ar
Allocate affinity option and masks for mmap data buffers and
record thread as well as initialize allocated objects.
Signed-off-by: Alexey Budankov
---
Changes in v3:
- converted PERF_AFFINITY_EOF to PERF_AFFINITY_MAX
Changes in v2:
- made debug affinity mode message user friendly
- converted a
On Tue, Jan 22, 2019 at 4:28 PM Greg Kroah-Hartman
wrote:
>
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Viresh Kumar
> Cc: Nishanth Menon
> Cc:
Allocate and bind AIO user space buffers to the memory nodes
that mmap kernel buffers are bound to.
Signed-off-by: Alexey Budankov
---
Changes in v4:
- fixed compilation issue converting pr_warn() to pr_warning()
- implemented stop if mbind() fails
Changes in v3:
- corrected code style issues
On Tue, Jan 22, 2019 at 12:39:36PM +0530, Viresh Kumar wrote:
> On 18-01-19, 14:45, Matthias Kaehlcke wrote:
> > On Fri, Jan 18, 2019 at 03:32:34PM +0530, Viresh Kumar wrote:
> > > On 17-01-19, 17:03, Matthias Kaehlcke wrote:
> > > > On Fri, Jan 11, 2019 at 02:48:34PM +0530, Viresh Kumar wrote:
> >
Build node cpu masks for mmap data buffers. Apply node cpu
masks to tool thread every time it references data buffers
cross node or cross cpu.
Signed-off-by: Alexey Budankov
---
Changes in v5:
- avoided multiple allocations of online cpu maps by
implementing it once in cpu_map__online()
Cha
Implement --affinity=node|cpu option for the record mode defaulting
to system affinity mask bouncing.
Signed-off-by: Alexey Budankov
---
Changes in v5:
- reduced indentation at record__parse_affinity()
Changes in v3:
- adjusted indentation at record__parse_affinity()
---
tools/perf/Documentat
On Wed, Jan 16, 2019 at 10:18:09PM +0100, Andreas Kemnade wrote:
> Some Wi2Wi devices do not have a wakeup output, so device state can
> only be indirectly detected by looking whether there is communitcation
communication
> over the serial lines.
> This approach requires a report cycle set to a l
Hi all,
The Pyra handheld PWM LCD regression in v5.0-rc1 reported by Nikolaus
goes back to v4.19 for pwm-omap-dmtimer. Here are patches against v4.19
to fix the issue that also makes pwm-vibra working again for droid 4.
Regards,
Tony
Tony Lindgren (3):
clocksource: timer-ti-dm: Fix pwm dmtim
Commit 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe
them with ti-sysc") moved some omap4 timers to probe with ti-sysc
interconnect target module. Turns out this broke pwm-omap-dmtimer
where we now try to reparent the clock to itself with the following:
omap_dm_timer_of_set_source
Commit 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe
them with ti-sysc") started producing a warning for pwm-omap-dmtimer:
WARNING: CPU: 0 PID: 77 at drivers/bus/omap_l3_noc.c:147
l3_interrupt_handler+0x2f8/0x388
4400.ocp:L3 Custom Error: MASTER MPU TARGET L4PER2 (Idle):
Data
Commit 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe
them with ti-sysc") moved some omap4 timers to probe with ti-sysc
interconnect target module. Turns out this broke pwm-omap-dmtimer
for reparenting of the timer clock.
With ti-sysc, we can now configure the clock sources in the
On Mon, 21 Jan 2019 12:51:14 +0100
Pierre Morel wrote:
> On 18/01/2019 14:51, Jean-Philippe Brucker wrote:
> > Hi Pierre,
> >
> > On 18/01/2019 13:29, Pierre Morel wrote:
> >> On 17/01/2019 14:02, Robin Murphy wrote:
> >>> On 15/01/2019 17:37, Pierre Morel wrote:
> The s390 iommu can
On 19/01/2019 10:00:25+0100, Sam Ravnborg wrote:
> Respin of patchset on top of v5.0-rc2 with feedback addressed (thanks!)
>
> Introduce a new generic property "quartz-load-femtofarad"
> to specify the quartz load.
> The default value is selected to match the current Linux
> drivers, so there are
On 25/12/2018 20:43:33-0600, Kangjie Lu wrote:
> clk_prepare() could fail, so let's check its status and if it fails
> return its error code upstream.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/rtc/rtc-coh901331.c | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
Applied, thanks
On Wed, Jan 16, 2019 at 10:18:11PM +0100, Andreas Kemnade wrote:
> Devices might have a separate lna between antenna input of the gps
> chip and the antenna which might have a separate supply.
>
> Signed-off-by: Andreas Kemnade
> ---
> Changes in v3:
> - improved error checking
> - style cleanu
On 25/12/2018 21:09:11-0600, Kangjie Lu wrote:
> When i2c_smbus_read_i2c_block_data() fails, the read data in "buf" could
> be incorrect and should not be used. The fix checks if
> i2c_smbus_read_i2c_block_data fails, and if so, return its error code
> upstream.
>
> Signed-off-by: Kangjie Lu
> --
On 06/01/2019 08:21:03+, Eric Wong wrote:
> Older versions of Libreboot and Coreboot had an invalid value
> (`3' in my case) in the century byte affecting the GM45 in
> the Thinkpad X200. Not everybody's updated their firmwares,
> and Linux <= 4.2 was able to read the RTC without problems,
> s
From: Ben Whitten
The SX130x family consumes two clocks, a 32 MHz clock provided by a
connected IQ transceiver, and a 133 MHz high speed clock.
In the example we connect the concentrator to a fixed clock providing
the 133 MHz high speed clock, and we connect to a connected transceiver
32 MHz clo
From: Ben Whitten
The SX125x consumes a clock (FXOSC) ranging from 32 to 36 MHz.
If the radio is coupled with an SX130x the radio is therefor operating in
master mode and it may also provide a gated version of this clock for the
concentrator. In this case the concentrator is expecting a 32 MHz in
Hello,
This series adds documentation for the SX130x and SX125x chips.
We are using the yaml binding format and this series builds with
'make dt_binding_check'.
Thanks,
Ben Whitten
Ben Whitten (4):
dt-bindings: lora: sx130x: add basic documentation
dt-bindings: lora: sx125x: add basic docume
From: Ben Whitten
Add basic documentation in YAML format for the SX130x series concentrators
from Semtech.
Required is; the location on the SPI bus and the compatible string.
Signed-off-by: Ben Whitten
---
v1 -> v2:
* Dropped reset-gpios, radio-spi from required.
* Dropped spi-max-frequency fro
From: Ben Whitten
The SX125x family are IQ radio transceivers from Semtech configured over
SPI, they are typically connected to an SX130x series concentrator however
may be connected to a host directly.
Required properties include the radio number of the host or concentrator
bus.
Signed-off-by:
On Wed, Jan 16, 2019 at 10:18:12PM +0100, Andreas Kemnade wrote:
> Add lna-supply property.
>
> Signed-off-by: Andreas Kemnade
> ---
> Changes in v3:
> - moved to gnss.txt
>
> Documentation/devicetree/bindings/gnss/gnss.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation
Hi Linus,
Please pull the following Kselftest update for Linux 5.0-rc4
This Kselftest update for Linux 5.0-rc4 consists of fixes to rtc,
seccomp and other tests.
diff is attached.
thanks,
-- Shuah
The following changes since co
This patch uses the information conveyed by perf_event::attr::config2
to select a sink to use for the session. That way a sink can easily be
selected to be used by more than one source, something that isn't currently
possible with the sysfs implementation.
Signed-off-by: Mathieu Poirier
---
...
Now that event's config2 attribute is used to communicate sink selection
to the kernel, remove the old set_drv_config() implementation since it
is no longer needed.
Signed-off-by: Mathieu Poirier
---
tools/perf/arch/arm/util/cs-etm.c | 54 ---
tools/perf/arch/arm/util
This is the second revision of a patchset allowing multiple sources to select
the same sink for a session which is a prerequisite for the support of CoreSight
CPU-wide trace scenarios.
The sink ID is communicated to the kernel by way of the event's configuration
attribute (event::attr:config2). T
The communication of sink information for a trace session doesn't work when
more than one CPU is involved in the scenario due to the static nature of
sysfs. As such communicate the sink information to each event by using the
perf_event::attr:config2 attribute. The information sent to the kernel i
Moving definition of EVENT_SOURCE_DEVICE_PATH to pmu.h so that it can be
used by other files than pmu.c
Signed-off-by: Mathieu Poirier
---
tools/perf/util/pmu.c | 2 --
tools/perf/util/pmu.h | 1 +
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/util/pmu.c b/tools/perf/u
CoreSight was the only client of the PMU's set_drv_config() API. Now
that it is no longer needed by CoreSight remove it from the code base.
Signed-off-by: Mathieu Poirier
---
tools/perf/builtin-record.c | 10 -
tools/perf/builtin-stat.c | 9
tools/perf/builtin-top.c | 13 --
When pmu::setup_aux() is called the coresight PMU needs to know which
sink to use for the session by looking up the information in the
event's attr::config2 field.
As such simply replace the cpu information by the complete perf_event
structure and change all affected customers.
Signed-off-by: Mat
Add a "sinks" directory entry so that users can see all the sinks
available in the system in a single place. Individual sink are added
as they are registered with the coresight bus.
Signed-off-by: Mathieu Poirier
---
.../hwtracing/coresight/coresight-etm-perf.c | 76 +++
.../hw
On Mon, Jan 21, 2019 at 4:25 PM Rob Herring wrote:
>
> On Fri, Jan 11, 2019 at 03:01:24PM -0800, Evan Green wrote:
> > Wire up the reset controller in the Qcom UFS controller for the PHY.
> > This will be used to toggle PHY reset during initialization of the PHY.
> >
> > Signed-off-by: Evan Green
Looks good to me.
Acked-by: Satish Kharat
Satish Kharat
TECHNICAL LEADER.ENGINEERING
satis...@cisco.com
-Original Message-
From: Greg Kroah-Hartman
Sent: Tuesday, January 22, 2019 7:09 AM
To: James Bottomley ; Martin Petersen
Cc: linux-kernel@vger.kernel.org; linux-s...@vger.kernel.
On Tue, Jan 22, 2019 at 09:40:56AM -0800, Guenter Roeck wrote:
> On Tue, Jan 22, 2019 at 07:10:23PM +0200, Matti Vaittinen wrote:
> > On Tue, Jan 22, 2019 at 07:47:50AM -0800, Guenter Roeck wrote:
> > > On Tue, Jan 22, 2019 at 11:48:36AM +0200, Matti Vaittinen wrote:
> > > > Initial support for wat
On 22-Jan 18:13, Peter Zijlstra wrote:
> On Tue, Jan 15, 2019 at 10:15:05AM +, Patrick Bellasi wrote:
> > @@ -342,11 +350,24 @@ static void sugov_iowait_boost(struct sugov_cpu
> > *sg_cpu, u64 time,
> > return;
> > sg_cpu->iowait_boost_pending = true;
> >
> > + /*
> > +
On Mon, Jan 21, 2019 at 11:40:45PM +0530, Amit Kucheria wrote:
> On Tue, Jan 15, 2019 at 3:31 AM Matthias Kaehlcke wrote:
> >
> > On Mon, Jan 14, 2019 at 03:51:10PM +0530, Amit Kucheria wrote:
> > > Since all cpus in the big and little clusters, respectively, are in the
> > > same frequency domain
On 22/01/2019 10:42:14+, Jan Kotas wrote:
> This patchset adds a driver support for Cadence RTC IP.
> It supports time, date and wakeups from sleep.
>
> Changes since v2:
> Fixed a typo in the bindings documentation.
>
> Changes since v1:
> Added devm_rtc_allocate_device before re
Hello,
syzbot found the following crash on:
HEAD commit:133bbb18ab1a virtio-net: per-queue RPS config
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=130be6cf40
kernel config: https://syzkaller.appspot.com/x/.config?x=8a4dffabfb4e36f9
dashboard link: h
Notificação de email do Web Admin
Esta mensagem é do nosso centro de mensagens do Web Admin para todos os nossos
proprietários de contas de e-mail. Estamos eliminando o acesso a todos os
nossos clientes de webmail. Sua conta de e-mail será atualizada para uma
interface de usuário de webmail n
On Wed, Jan 23, 2019 at 2:29 AM Jarkko Sakkinen
wrote:
>
> > >
> > > Fails on commit 170d13ca3a2fdaaa0283399247631b76b441cca2. Still works on
> > > preceding commit a959dc88f9c8900296ccf13e2f3e1cbc555a8917.
> >
> > This changes the IO access pattern in memcpy_to/fromio.. Presumably
> > CRB HW does
Notificação de email do Web Admin
Esta mensagem é do nosso centro de mensagens do Web Admin para todos os nossos
proprietários de contas de e-mail. Estamos eliminando o acesso a todos os
nossos clientes de webmail. Sua conta de e-mail será atualizada para uma
interface de usuário de webmail n
On Tue, Jan 22, 2019 at 06:19:08PM +0100, Sebastian Andrzej Siewior wrote:
> On 2019-01-22 17:25:03 [+0100], Greg Kroah-Hartman wrote:
> > > > }
> > > >
> > > > static void bdi_debug_unregister(struct backing_dev_info *bdi)
> > > > {
> > > > - debugfs_remove(bdi->debug_stats);
> > > > -
On Wed, Jan 16, 2019 at 1:29 PM Stephen Boyd wrote:
>
> Quoting Evan Green (2019-01-11 15:01:23)
> > diff --git a/Documentation/devicetree/bindings/ufs/ufs-qcom.txt
> > b/Documentation/devicetree/bindings/ufs/ufs-qcom.txt
> > index 21d9a93db2e97..985f5e99ab332 100644
> > --- a/Documentation/devic
Add an additional bit flag to the device_private struct named "dead".
This additional flag provides a guarantee that when a device_del is
executed on a given interface an async worker will not attempt to attach
the driver following the earlier device_del call. Previously this
guarantee was not pre
This patch set provides functionality that will help to improve the
locality of the async_schedule calls used to provide deferred
initialization.
This patch set originally started out focused on just the one call to
async_schedule_domain in the nvdimm tree that was being used to defer the
device_a
Call the asynchronous probe routines on a CPU local to the device node. By
doing this we should be able to improve our initialization time
significantly as we can avoid having to access the device from a remote
node which may introduce higher latency.
For example, in the case of initializing memor
Provide a new function, queue_work_node, which is meant to schedule work on
a "random" CPU of the requested NUMA node. The main motivation for this is
to help assist asynchronous init to better improve boot times for devices
that are local to a specific node.
For now we just default to the first C
On 01/22/2019 08:39 AM, Huazhong Tan wrote:
> From: Jian Shen
>
> This patch adds rx multicast packets statistic for each ring.
>
> Signed-off-by: Jian Shen
> Signed-off-by: Peng Li
> Signed-off-by: Huazhong Tan
> ---
> drivers/net/ethernet/hisilicon/hns3/hns3_enet.c| 9 +
> d
Introduce four new variants of the async_schedule_ functions that allow
scheduling on a specific NUMA node.
The first two functions are async_schedule_near and
async_schedule_near_domain end up mapping to async_schedule and
async_schedule_domain, but provide NUMA node specific functionality. They
Try to consolidate all of the locking and unlocking of both the parent and
device when attaching or removing a driver from a given device.
To do that I first consolidated the lock pattern into two functions
__device_driver_lock and __device_driver_unlock. After doing that I then
created functions
Use the device specific version of the async_schedule commands to defer
various tasks related to power management. By doing this we should see a
slight improvement in performance as any device that is sensitive to
latency/locality in the setup will now be initializing on the node closest
to the dev
The current async_probe test code is only testing one device allocated
prior to driver load and only loading one device afterwards. Instead of
doing things this way it makes much more sense to load one device per CPU
in order to actually stress the async infrastructure. By doing this we
should see
Probe devices asynchronously instead of the driver. This results in us
seeing the same behavior if the device is registered before the driver or
after. This way we can avoid serializing the initialization should the
driver not be loaded until after the devices have already been added.
The motivati
Force the device registration for nvdimm devices to be closer to the actual
device. This is achieved by using either the NUMA node ID of the region, or
of the parent. By doing this we can have everything above the region based
on the region, and everything below the region based on the nvdimm bus.
On Tue, Jan 22, 2019 at 09:29:07AM -0800, Sean Christopherson wrote:
> On Tue, Jan 22, 2019 at 09:21:02AM -0800, Sean Christopherson wrote:
> > On Tue, Jan 22, 2019 at 04:21:50PM +0100, Greg Kroah-Hartman wrote:
> > > When calling debugfs functions, there is no need to ever check the
> > > return v
> From: Kimberly Brown
> Sent: Monday, January 21, 2019 10:43 PM
> > > @@ -1421,7 +1422,10 @@ static ssize_t vmbus_chan_attr_show(struct
> > > kobject *kobj,
> > > if (chan->state != CHANNEL_OPENED_STATE)
> > > return -EINVAL;
> > >
> > > - return attribute->show(chan, buf);
> > > + mu
On Thu, Jan 10, 2019 at 03:06:10PM +, Srinivas Kandagatla wrote:
This all looks good apart from a couple of small things that should be
easy to fix:
> diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
> index 62bdb7e333b8..1c4904940621 100644
> --- a/sound/soc/codecs/Kconfig
>
On Tue, Jan 22, 2019 at 04:42:47PM +, Quentin Perret wrote:
> The recently introduced Energy Model (EM) framework manages power cost
> tables of CPUs. These tables are currently only visible from kernel
> space. However, in order to debug the behaviour of subsystems that use
> the EM (EAS for e
Hi Greg,
On 22/01/2019 15:21, Greg Kroah-Hartman wrote:
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Also delete the variables for the file dentries for the d
701 - 800 of 1233 matches
Mail list logo
