One of the responsibility of the ->verify() callback is to make sure
that the policy's min frequency is <= max frequency as this isn't
guaranteed by the QoS framework which gave us those values.
Update the comment in cpufreq_set_policy() to clarify that.
Suggested-by: Rafael J. Wysocki
On 22/10/2019 04.24, Qiang Zhao wrote:
> On Mon, Oct 22, 2019 at 6:11 AM Leo Li wrote
>> Right. I'm really interested in getting this applied to my tree and make it
>> upstream. Zhao Qiang, can you help to review Rasmus's patches and
>> comment?
>
> As you know, I maintained a similar patchset
On 22/10/19 2:30 PM, Philipp Zabel wrote:
> Hi Kishon,
>
> On Tue, 2019-10-22 at 14:06 +0530, Kishon Vijay Abraham I wrote:
>> Memory allocated for 'struct reset_control_array' in
>> of_reset_control_array_get() is never freed in
>> reset_control_array_put() resulting in kmemleak showing
>>
Hi Andrew Murray,
On 10/21/2019 7:19 PM, Andrew Murray wrote:
On Mon, Oct 21, 2019 at 02:39:18PM +0800, Dilip Kota wrote:
Add YAML shcemas for PCIe RC controller on Intel Gateway SoCs
s/shcemas/schemas/
which is Synopsys DesignWare based PCIe core.
The revision history below doesn't need
Hi Mazin,
On Sun, Oct 20, 2019 at 6:41 AM Mazin Rezk wrote:
>
> This patch allows short reports to be translated into long reports.
>
> hidpp_validate_device now returns a u8 instead of a bool which represents
> the supported reports. The corresponding bits (i.e.
> HIDPP_REPORT_*_SUPPORTED) are
The MC(Management Complex) exports the DPDMAI(Data Path DMA Interface)
object as an interface to operate the DPAA2(Data Path Acceleration
Architecture 2) qDMA Engine. The DPDMAI enables sending frame-based
requests to qDMA and receiving back confirmation response on transaction
completion,
On Tue, 22 Oct 2019 at 09:45, Borislav Petkov wrote:
>
> On Tue, Oct 22, 2019 at 08:13:56AM +0200, Ard Biesheuvel wrote:
> > On Thu, 17 Oct 2019 at 11:30, Kairui Song wrote:
> > >
> > > Currently, kernel fails to boot on some HyperV VMs when using EFI.
> > > And it's a potential issue on all
DPPA2(Data Path Acceleration Architecture 2) qDMA supports
virtualized channel by allowing DMA jobs to be enqueued into
different work queues. Core can initiate a DMA transaction by
preparing a frame descriptor(FD) for each DMA job and enqueuing
this job through a hardware portal. DPAA2 components
On Mon, 21 Oct 2019 14:47:18 +0200
Bartosz Golaszewski wrote:
> sob., 12 paź 2019 o 15:37 Jonathan Cameron napisał(a):
> >
> > On Mon, 7 Oct 2019 04:41:31 +0200
> > Bartosz Golaszewski wrote:
> >
> > > From: Bartosz Golaszewski
> > >
> > > We can drop some duplicate code if we use
On 22/10/2019 00.11, Li Yang wrote:
> On Mon, Oct 21, 2019 at 3:46 AM Rasmus Villemoes
> wrote:
>>
>>> Can you try the 4.14 branch from a newer LSDK release? LS1021a should
>>> be supported platform on LSDK. If it is broken, something is wrong.
>>
>> What newer release? LSDK-18.06-V4.14 is the
On 22-10-19, 11:46, Rafael J. Wysocki wrote:
> On Tue, Oct 22, 2019 at 4:25 AM Viresh Kumar wrote:
> >
> > On 21-10-19, 14:28, Sudeep Holla wrote:
> > > Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
> > > freeing")
> > > added cancel_work_sync(policy->update) after
On 21/10/19 7:53, Gwendal Grignou wrote:
> From: Enrico Granata
>
> Add a layer of sanity checking to cros_ec_register against attempting to
> register IRQ values that are not strictly greater than 0.
>
> Signed-off-by: Enrico Granata
> Signed-off-by: Gwendal Grignou
Enrico, Gwendal, this
On Sun, 6 Oct 2019 10:49:18 +0100
Jonathan Cameron wrote:
> On Wed, 2 Oct 2019 17:57:30 +0200
> Bartosz Golaszewski wrote:
>
> > śr., 2 paź 2019 o 15:06 kbuild test robot napisał(a):
> > >
> > > Hi Bartosz,
> > >
> > > I love your patch! Yet something to improve:
> > >
> > > [auto build
On Tue, Oct 22, 2019 at 11:20:18AM +0200, Peter Zijlstra wrote:
> Andi reported that when creating a lot of events, a lot of time is
> spend in IPIs and asked if it would be possible to elide some of that.
>
> Now when, as for example the perf-tool always does, events are created
> disabled, then
Hi Gwendal,
Cc'ing some ISHTP people as I don't have the hardware. If possible, could any of
you give us your Tested-by tag?
On 21/10/19 7:53, Gwendal Grignou wrote:
> To improve sensor timestamp precision, given EC and AP are in
> different time domains, the AP needs to try to record the exact
+++ Masahiro Yamada [22/10/19 13:37 +0900]:
On Tue, Oct 22, 2019 at 1:05 AM Jessica Yu wrote:
When doing an out of tree build with O=, the nsdeps script constructs
the absolute pathname of the module source file so that it can insert
MODULE_IMPORT_NS statements in the right place. However,
On Sat, Oct 19, 2019 at 11:44 AM Miquel Raynal
wrote:
>
> Hi Arnd,
>
> Arnd Bergmann wrote on Fri, 18 Oct 2019 17:41:26 +0200:
>
> > The driver traditionally hardcodes the MMIO register address and
> > the GPIO numbers from data defined in platform header files.
> >
> > To make it indepdendent
On Tue, 22 Oct 2019 09:27:15 +0530
Rishi Gupta wrote:
> veml6030 is an ambient light sensor from Vishay semiconductors.
> It has 16-bit resolution, supports both ambient light measurement
> and white channel which is more responsive to wider wavelength
> spectrum. It has flexible power saving,
Add AUX sampling support to the PT PMU: implement an NMI-safe callback
that takes a snapshot of the buffer without touching the event states.
This is done for PT events that don't use PMIs, that is, snapshot mode
(RO mapping of the AUX area).
Signed-off-by: Alexander Shishkin
---
Most of PT implementations support Single Range Output mode, which is
an alternative to ToPA that can be used for a single contiguous buffer
and if we don't require an interrupt, that is, in AUX snapshot mode.
Now that perf core will use high order allocations for the AUX buffer,
in many cases
AUX data can be used to annotate perf events such as performance counters
or tracepoints/breakpoints by including it in sample records when
PERF_SAMPLE_AUX flag is set. Such samples would be instrumental in debugging
and profiling by providing, for example, a history of instruction flow
leading up
PT trace is now enabled at the bottom of the event configuration
function that takes care of all configuration bits related to a given
event, including the address filter update. This is only needed where
the event configuration changes, that is, in ->add()/->start().
In the interrupt path we can
Hi Peter,
Here's a new version of the AUX sampling. Since the previous one [3],
it addresses the issues of NMI-safety and sampling hardware events.
The former is addressed by adding a new PMU callback, the latter by
making use of grouping. It also depends on the AUX output stop fix
[4] to work
On Tue, Oct 22, 2019 at 11:22:56AM +0200, Michal Hocko wrote:
> Hmm, that might be a misunderstanding on my end. I thought that it is
> the MCE handler to say whether the failure is recoverable or not. If yes
> then we can touch the content of the memory (that would imply the
> migration). Other
This patch introduces a mdev based hardware vhost backend.
This backend is built on top of the same abstraction used
in virtio-mdev and provides a generic vhost interface for
userspace to accelerate the virtio devices in guest.
This backend is implemented as a mdev device driver on top
of the
On Tue, 22 Oct 2019, Suwan Kim wrote:
> iso_buffer should be set to NULL after use and free in the while loop.
> In the case of isochronous URB in the while loop, iso_buffer is
> allocated and after sending it to server, buffer is deallocated. And
> then, if the next URB in the while loop is
Is it ok now? It seems not yet merged to next. Other code is based on this.
Am 10. September 2019 09:04:41 MESZ schrieb Frank Wunderlich
:
>From: Josef Friedl
>
>move code to separate header-file to reuse definitions later
>in poweroff-driver (drivers/power/reset/mt6323-poweroff.c)
>
(Resending since Gmail mobile client converts email to HTML)
Hi Stephen,
On Tue, Oct 22, 2019 at 4:53 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the thermal tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from
On Tue, 22 Oct 2019 09:28:25 +0530
Rishi Gupta wrote:
> The driver for veml6030 light sensor provides custom sysfs entries
> used to know parameters supported by the driver and to configure
> sensor like setting power saving mode and persistence etc. This
> commit document them.
>
>
Hi Candle,
On Mon, Oct 21, 2019 at 9:54 AM Candle Sun wrote:
>
> Hi,
>
>
> On Mon, Oct 21, 2019 at 3:38 PM Candle Sun wrote:
> >
> > From: Candle Sun
> >
> > Upstream commit 58e75155009c ("HID: core: move Usage Page concatenation
> > to Main item") adds support for Usage Page item after Usage
On Tue, Oct 22, 2019 at 4:25 AM Viresh Kumar wrote:
>
> On 21-10-19, 14:28, Sudeep Holla wrote:
> > Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
> > freeing")
> > added cancel_work_sync(policy->update) after the frequency QoS were
> > removed. We can cancel the work
Will it be merged on rc-cycle?
I ask because i see it only in mfd-next but not in fixes/torvalds-master
Regards Frank
Am 16. Oktober 2019 11:53:38 MESZ schrieb Lee Jones :
>On Thu, 03 Oct 2019, Frank Wunderlich wrote:
>
>> Part 3 from this series [1] was not merged due to wrong splitting
>> and
On Sat, Oct 19, 2019 at 4:07 PM Guenter Roeck wrote:
> > @@ -319,10 +316,13 @@ static struct platform_device *sa11x0_devices[]
> > __initdata = {
> >
> > static int __init sa1100_init(void)
> > {
> > + struct resource wdt_res = DEFINE_RES_MEM(0x9000, 0x20);
> > pm_power_off =
On Tue, Oct 22, 2019 at 09:01:11AM +0300, Alexey Budankov wrote:
> swap(ctx->task_ctx_data, next_ctx->task_ctx_data);
>
> + /*
> + * PMU specific parts of task perf context can require
> + * additional
On Mon, Oct 21, 2019 at 07:13:32PM -0500, Alex G. wrote:
> I think it's clearer if this is explained in a comment. That it doesn't
> break anything, and we're okay this applies to all hotplug ports, even those
> that are not in front of an NVMe backplane.
I agree.
Hello!
On 21.10.2019 15:18, Krzysztof Hałasa wrote:
Fix a bug where the mac80211 RX aggregation code sets a new aggregation
"session" at the remote station's request, but the head_seq_num
(the sequence number the receiver expects to receive) isn't reset.
Spotted on a pair of AR9580 in IBSS
On Tue, Oct 22, 2019 at 10:30:02AM +0200, Michal Hocko wrote:
> But we have destructors for compound pages. Can we do the heavy lifting
> there?
Yes, we could.
Actually, I tried that approach, but I thought it was simpler this way.
Since there is no hurry in this, I will try to take that up again
Hi Gwendal,
On 21/10/19 18:00, Jonathan Cameron wrote:
> On Sun, 20 Oct 2019 22:53:49 -0700
> Gwendal Grignou wrote:
>
>> - Remove duplicate code in mfd, since mfd just register
>> cros_ec_sensorhub if at least one sensor is present
>> - Change iio cros_ec driver to get the pointer to the
On Mon, Oct 21, 2019 at 01:03:02PM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> In LBR call stack mode, the depth of reconstructed LBR call stack limits
> to the number of LBR registers. With LBR Top-of-Stack (TOS) information,
> perf tool may stitch the stacks of two samples.
pon., 21 paź 2019 o 22:26 Navid Emamdoost
napisał(a):
>
> In the impelementation of davinci_timer_register() the allocated memory
> for clockevent should be released if request_irq() fails.
>
> Fixes: 721154f972aa ("clocksource/drivers/davinci: Add support for
> clockevents")
> Signed-off-by:
iso_buffer should be set to NULL after use and free in the while loop.
In the case of isochronous URB in the while loop, iso_buffer is
allocated and after sending it to server, buffer is deallocated. And
then, if the next URB in the while loop is not a isochronous pipe,
iso_buffer still holds the
On 22.10.19 11:24, Michal Hocko wrote:
On Tue 22-10-19 11:17:24, David Hildenbrand wrote:
On 22.10.19 11:14, Michal Hocko wrote:
On Tue 22-10-19 10:32:11, David Hildenbrand wrote:
[...]
E.g., arch/x86/kvm/mmu.c:kvm_is_mmio_pfn()
Thanks for these references. I am not really familiar with kvm
Hi Bjorn Helgaas,
On 10/22/2019 1:18 AM, Bjorn Helgaas wrote:
On Mon, Oct 21, 2019 at 02:38:50PM +0100, Andrew Murray wrote:
On Mon, Oct 21, 2019 at 02:39:20PM +0800, Dilip Kota wrote:
PCIe RC driver on Intel Gateway SoCs have a requirement
of changing link width and speed on the fly.
Please
On Thu, 17 Oct 2019 at 08:16, Peng Ma wrote:
>
> Hi Vinod,
>
> Thanks very much for your reply.
>
> Best Regards,
> Peng
> >-Original Message-
> >From: Vinod Koul
> >Sent: 2019年10月17日 12:11
> >To: Peng Ma
> >Cc: dan.j.willi...@intel.com; Leo Li ;
> >linux-kernel@vger.kernel.org;
On Tue, Oct 22, 2019 at 9:51 AM Ran Wang wrote:
>
> Some user might want to go through all registered wakeup sources
> and doing things accordingly. For example, SoC PM driver might need to
> do HW programming to prevent powering down specific IP which wakeup
> source depending on. So add this
On Mon, Oct 21, 2019 at 01:28:54PM -0600, shuah wrote:
> On 10/21/19 9:08 AM, Julia Lawall wrote:
> >
> >
> > On Mon, 21 Oct 2019, Suwan Kim wrote:
> >
> > > iso_buffer should be set to NULL after use and free in the while loop.
> > > In the case of isochronous URB in the while loop, iso_buffer
From: "Liang, Kan"
Andi reported that he was hitting the linear search in
perf_init_event() a lot. Now that all !TYPE_SOFTWARE events should hit
the IDR, make sure the TYPE_SOFTWARE events are at the head of the
list such that we'll quickly find the right PMU (provided a valid
event was given).
Andi reported that when creating a lot of events, a lot of time is
spend in IPIs and asked if it would be possible to elide some of that.
Now when, as for example the perf-tool always does, events are created
disabled, then these events will not need to be scheduled when added
to the context
Andi reported that he was hitting the linear search in
perf_init_event() a lot. Make more agressive use of the IDR lookup to
avoid hitting the linear search.
With exception of PERF_TYPE_SOFTWARE (which relies on a hideous hack),
we can put everything in the IDR. On top of that, we can alias
Hi,
There here patches are the result of Andi looking at perf event creation
bottlenecks. And while he's solved much of it with his recent perf-stat patch
set that moves event creation to CPU affine threads, these patches do still
help and can also cover other workloads.
Please consider.
On Tue 22-10-19 11:17:24, David Hildenbrand wrote:
> On 22.10.19 11:14, Michal Hocko wrote:
> > On Tue 22-10-19 10:32:11, David Hildenbrand wrote:
> > [...]
> > > E.g., arch/x86/kvm/mmu.c:kvm_is_mmio_pfn()
> >
> > Thanks for these references. I am not really familiar with kvm so I
> > cannot
On Tue 22-10-19 10:35:17, Oscar Salvador wrote:
> On Tue, Oct 22, 2019 at 10:26:11AM +0200, Michal Hocko wrote:
> > On Tue 22-10-19 09:46:20, Oscar Salvador wrote:
> > [...]
> > > So, opposite to hard-offline, in soft-offline we do not fiddle with pages
> > > unless we are sure the page is not
Hi Andrew Murray,
On 10/21/2019 9:38 PM, Andrew Murray wrote:
On Mon, Oct 21, 2019 at 02:39:20PM +0800, Dilip Kota wrote:
PCIe RC driver on Intel Gateway SoCs have a requirement
of changing link width and speed on the fly.
So add the sysfs attributes to show and store the link
properties.
Add
On Tue, Oct 22, 2019 at 9:52 AM Ran Wang wrote:
>
> The NXP's QorIQ Processors based on ARM Core have RCPM module
> (Run Control and Power Management), which performs system level
> tasks associated with power management such as wakeup source control.
>
> This driver depends on PM wakeup source
On 22.10.19 11:14, Michal Hocko wrote:
On Tue 22-10-19 10:32:11, David Hildenbrand wrote:
[...]
E.g., arch/x86/kvm/mmu.c:kvm_is_mmio_pfn()
Thanks for these references. I am not really familiar with kvm so I
cannot really comment on the specific code but I am wondering why
it simply doesn't
On Tue 22-10-19 10:32:11, David Hildenbrand wrote:
[...]
> E.g., arch/x86/kvm/mmu.c:kvm_is_mmio_pfn()
Thanks for these references. I am not really familiar with kvm so I
cannot really comment on the specific code but I am wondering why
it simply doesn't check for ZONE_DEVICE explicitly? Also we
> In the impelementation of davinci_timer_register() the allocated memory
> for clockevent should be released if request_irq() fails.
* Please avoid the copying of typos from previous change descriptions.
* Under which circumstances will an “imperative mood” matter for you here?
Hi,
On Tue 15 Oct 19, 19:16, Jernej Škrabec wrote:
> Please understand that I was working on this on and off for almost half a
> year
> and checked many times all register values. At one point I tried libvdpau-
> sunxi which has no problem with sample video. Still, all relevant register
>
There are cases where a guest tries to switch spinlocks to bare metal
behavior (e.g. by setting "xen_nopvspin" on XEN platform and
"hv_nopvspin" on HYPER_V).
That feature is missed on KVM, add a new parameter "nopvspin" to disable
PV spinlocks for KVM guest.
The new 'nopvspin' parameter will
On Mon, 2019-10-14 at 10:18 -0500, Dinh Nguyen wrote:
> The Intel SoCFPGA Agilex platform shares the same reset controller that
> is on the Stratix10.
>
> Signed-off-by: Dinh Nguyen
> ---
> v2: rebase to v5.4-rc1
> ---
> drivers/reset/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1
pr_*() is preferred than printk(KERN_* ...), after change all the print
in arch/x86/kernel/kvm.c will have "kvm_guest: xxx" style.
No functional change.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Vitaly Kuznetsov
Cc: Paolo Bonzini
Cc: Radim Krcmar
Cc: Sean Christopherson
Cc: Vitaly
Map "xen_nopvspin" to "nopvspin", fix stale description of "xen_nopvspin"
as we use qspinlock now.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Boris Ostrovsky
Cc: Jonathan Corbet
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav
Map "hv_nopvspin" to "nopvspin".
Signed-off-by: Zhenzhong Duan
Reviewed-by: Michael Kelley
Cc: Jonathan Corbet
Cc: "K. Y. Srinivasan"
Cc: Haiyang Zhang
Cc: Stephen Hemminger
Cc: Sasha Levin
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
---
All the patches have Reviewed-by now, I think v7 could be the final
version.
There are cases folks want to disable spinlock optimization for
debug/test purpose. Xen and hyperv already have parameters "xen_nopvspin"
and "hv_nopvspin" to support that, but kvm doesn't.
The first patch adds that
This reverts commit 34226b6b70980a8f81fff3c09a2c889f77edeeff.
Commit 8990cac6e5ea ("x86/jump_label: Initialize static branching
early") adds jump_label_init() call in setup_arch() to make static
keys initialized early, so we could use the original simpler code
again.
The similar change for XEN
On Fri, Oct 18, 2019 at 02:23:52PM +0200, Gerd Hoffmann wrote:
> Be consistent with the rest of the code base.
>
> Signed-off-by: Gerd Hoffmann
Assuming sparse is all still pleased:
Reviewed-by: Daniel Vetter
> ---
> drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++--
>
Hi Bjorn Helgaas,
On 10/22/2019 1:17 AM, Bjorn Helgaas wrote:
On Mon, Oct 21, 2019 at 02:39:19PM +0800, Dilip Kota wrote:
Add support to PCIe RC controller on Intel Gateway SoCs.
PCIe controller is based of Synopsys DesignWare pci core.
Intel PCIe driver requires Upconfig support, fast
On Tue, 2019-10-22 at 10:03 +0200, Geert Uytterhoeven wrote:
> Hi Joe,
Hey again Geert.
> On Mon, Oct 21, 2019 at 5:37 PM Joe Perches wrote:
> > On Mon, 2019-10-21 at 16:37 +0200, Geert Uytterhoeven wrote:
> > > The existing debugfs_create_ulong() function supports objects of
> > > type
- and I remember that PG_reserved on memory holes is relevant to
detect MMIO pages. (e.g., looking at KVM code ...)
I can see kvm_is_reserved_pfn() which checks both pfn_valid and
PageReserved. How does this help to detect memory holes though?
Any driver might be setting the page reserved.
Hi Andrew Murray,
On 10/21/2019 9:03 PM, Andrew Murray wrote:
On Mon, Oct 21, 2019 at 02:39:19PM +0800, Dilip Kota wrote:
Add support to PCIe RC controller on Intel Gateway SoCs.
PCIe controller is based of Synopsys DesignWare pci core.
Intel PCIe driver requires Upconfig support, fast
Hi Thara,
On Monday 21 Oct 2019 at 17:03:56 (-0400), Thara Gopinath wrote:
> On 10/15/2019 06:14 AM, Quentin Perret wrote:
> > Hi Thara,
> >
> > On Sunday 13 Oct 2019 at 20:58:25 (-0400), Thara Gopinath wrote:
> >> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> >> index 00fcea2..5056c08 100644
pon., 21 paź 2019 o 08:44 Manivannan Sadhasivam
napisał(a):
>
> Add support for GPIO controller from RDA Micro. This GPIO controller
> is an in house IP, developed by RDA Micro (now Unisoc) for the use in
> RDA88* series of SoCs. There are multiple GPIO ports present in all SoCs,
> each capable
Le 21/10/2019 à 23:29, Thomas Gleixner a écrit :
On Mon, 21 Oct 2019, Christophe Leroy wrote:
This is a tentative to switch powerpc/32 vdso to generic C implementation.
It will likely not work on 64 bits or even build properly at the moment.
powerpc is a bit special for VDSO as well as
Hi Kishon,
On Tue, 2019-10-22 at 14:06 +0530, Kishon Vijay Abraham I wrote:
> Memory allocated for 'struct reset_control_array' in
> of_reset_control_array_get() is never freed in
> reset_control_array_put() resulting in kmemleak showing
> the following backtrace.
>
> backtrace:
>
Export the Type-C connector orientation so that user space
can get this information.
Signed-off-by: Puma Hsu
---
Documentation/ABI/testing/sysfs-class-typec | 11 +++
drivers/usb/typec/class.c | 18 ++
2 files changed, 29 insertions(+)
diff --git
On Tue 22-10-19 10:23:37, David Hildenbrand wrote:
> On 22.10.19 10:20, Michal Hocko wrote:
> > On Mon 21-10-19 17:54:35, David Hildenbrand wrote:
> > > On 21.10.19 17:47, Michal Hocko wrote:
> > > > On Mon 21-10-19 17:39:36, David Hildenbrand wrote:
> > > > > On 21.10.19 16:43, Michal Hocko
Hi,
I already send a patch on 2019-09-09 to this mailing list with a similar
issue[1].
Sadly no replies, although this is a huge bug in the rt kernel.
I fixed it a bit differently, using smaller locked regions.
You have also propably a bug in your patch, because trans->queue.lock is
no
On Sun, Oct 20, 2019 at 12:36:50PM -0700, Joe Perches wrote:
> > It's sort of tricky to know what "one thing per patch means".
>
> It seems somewhat arbitrary and based on Greg's understanding
> of the experience of the patch submitter and also the language
> of the potential commit message.
Of
Hi Heikki,
It’s not necessary to know the cable orientation for a normal user,
but we can have statistical analysis at Application layer. For example,
it may help investigating user behavior in the future if we can have the
count of plugging direction.
Besides, we also want to make the unified
On Mon, Oct 21, 2019 at 10:15:29PM -0700, Nathan Chancellor wrote:
> On Fri, Oct 18, 2019 at 03:02:10PM -0500, Segher Boessenkool wrote:
> > I think the proper solution is for the kernel to *do* use -ffreestanding,
> > and then somehow tell the kernel that memcpy etc. are the standard
> >
Hi Linus,
here is a bunch of pin control fixes. I was lagging behind
on this one, some fixes should have come in earlier,
sorry about that.
Anyways here it is, pretty straight-forward fixes, the Strago
fix stand out as something serious affecting a lot of
machines.
Yours,
Linus Walleij
The
2019-10-16 18:04 GMT+08:00, Lee Jones :
> On Tue, 15 Oct 2019, Gene Chen wrote:
>
>> Hi Lee,
>>
>> we find OF_MFD_CELL is not defined in mfd/core.h, which is ready to
>> merge to next kernel version
>>
Hi,
is no one interested in this?
Hi,
I was looking thoroughly at the realtime testcase sched_football,
because it sometimes fails and like to know your opinion on the test case.
A short introduction to how the test works:
It creates nThreads threads called offense and n threads called
On 22. 10. 19 10:26, Markus Elfring wrote:
>> In the impelementation of ttc_setup_clockevent() the allocated memory
>> for ttcce should be released if clk_notifier_register() fails.
>
> * Please avoid the copying of typos from previous change descriptions.
>
> * Under which circumstances will an
On Tue, Oct 22, 2019 at 09:43:23AM +0100, Ben Dooks (Codethink) wrote:
> The parse_acpi_topology() is not declared anywhere which
> causes the following sparse warning:
>
> drivers/base/arch_topology.c:522:19: warning: symbol 'parse_acpi_topology'
> was not declared. Should it be static?
>
>
On Thu, Oct 17, 2019 at 04:47:48PM -0700, Andrei Vagin wrote:
>
> In my table, the "before" column is actually for the upstream kernel
> with the 18-th patch. Here is the table with the real "before" column:
>
> | before| with 18/33 | CONFIG_TIME_NS=n | host | inside
> timens
>
On Wed, 16 Oct 2019, Peter Zijlstra wrote:
> On Wed, Oct 16, 2019 at 08:51:27AM +0200, Miroslav Benes wrote:
> > On Tue, 15 Oct 2019, Joe Lawrence wrote:
> >
> > > On 10/15/19 10:13 AM, Miroslav Benes wrote:
> > > > Yes, it does. klp_module_coming() calls module_disable_ro() on all
> > > >
From: Bartosz Golaszewski
Provide a variant of devm_platform_ioremap_resource() that allows to
lookup resources from platform devices by name rather than by index.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Arnd Bergmann
---
.../driver-api/driver-model/devres.rst| 1 +
From: Bartosz Golaszewski
Use the devm_platform_ioremap_resource_byname() helper instead of
calling platform_get_resource_byname() and devm_ioremap_resource()
separately.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Arnd Bergmann
---
drivers/gpio/gpio-tegra186.c | 4 +---
1 file changed,
The parse_acpi_topology() is not declared anywhere which
causes the following sparse warning:
drivers/base/arch_topology.c:522:19: warning: symbol 'parse_acpi_topology' was
not declared. Should it be static?
Signed-off-by: Ben Dooks (Codethink)
---
Cc: Sudeep Holla
Cc:
From: Bartosz Golaszewski
devm_platform_ioremap_resource() should be documented in devres.rst.
Add the missing entry.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Arnd Bergmann
---
Documentation/driver-api/driver-model/devres.rst | 1 +
1 file changed, 1 insertion(+)
diff --git
On 22.10.19 05:56, Andrey Smirnov wrote:
> Current wording in the binding documentation doesn't make it 100%
> clear that only one of "INT1" and "INT2" will ever be used by the
> driver and that specifying both has no advantages. Re-word it to make
> this aspect a bit more explicit.
>
>
On 21/10/2019 17:52, Sudeep Holla wrote:
On Mon, Oct 21, 2019 at 05:25:30PM +0100, Ben Dooks (Codethink) wrote:
The parse_acpi_topology() is not declared anywhere which
causes the following sparse warning:
drivers/base/arch_topology.c:522:19: warning: symbol 'parse_acpi_topology' was
not
On Mon, 21 Oct 2019 at 16:30, Ram Prakash Gupta wrote:
>
> This change adds the use of devfreq based clock scaling to MMC.
> This applicable for eMMC and SDCard.
> For some workloads, such as video playback, it isn't necessary
> for these cards to run at high speed. Running at lower
> frequency,
On Thu, Oct 17, 2019 at 12:41:37PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Oct 17, 2019 at 10:48:12AM +, Brian Starkey wrote:
> > On Thu, Oct 17, 2019 at 10:21:03AM +, james qian wang (Arm Technology
> > China) wrote:
> > > On Thu, Oct 17, 2019 at 08:20:56AM +, Brian
On 22-10-19, 16:33, Anson Huang wrote:
> i.MX8MN has different speed grade definition compared to
> i.MX8MQ/i.MX8MM, when fuses are NOT written, the default
> speed_grade should be set to minimum available OPP defined
> in DT which is 1.2GHz, the corresponding speed_grade value
> should be 0xb.
>
On 22.10.19 10:32, David Hildenbrand wrote:
On 22.10.19 10:21, Michal Hocko wrote:
On Tue 22-10-19 10:15:07, David Hildenbrand wrote:
On 22.10.19 10:08, Michal Hocko wrote:
On Tue 22-10-19 08:52:28, David Hildenbrand wrote:
On 21.10.19 19:23, David Hildenbrand wrote:
Two cleanups that
Memory allocated for 'struct reset_control_array' in
of_reset_control_array_get() is never freed in
reset_control_array_put() resulting in kmemleak showing
the following backtrace.
backtrace:
[] __kmalloc+0x1b0/0x2b0
[]
Guenter Roeck wrote:
> The `ar_usb` field of `ath10k_usb_pipe_usb_pipe` objects
> are initialized to point to the containing `ath10k_usb` object
> according to endpoint descriptors read from the device side, as shown
> below in `ath10k_usb_setup_pipe_resources`:
>
> for (i = 0; i <
From: Bartosz Golaszewski
The GPIO backlight driver currently requests the line 'as is', without
acively setting its direction. This can lead to problems: if the line
is in input mode by default, we won't be able to drive it later when
updating the status and also reading its initial value
701 - 800 of 891 matches
Mail list logo
