In commit ebc0f83c78a2 ("timers/nohz: Update NOHZ load in remote tick")
we got calc_load_nohz_remote(rq) as a one-line wrapper function around
calc_load_nohz_fold(rq) and with sched_tick_remote() as the only user.
However, we build the sched_tick_remote only for NO_HZ_FULL but the
wrapper inside
Hi,
On 6/9/20 10:13 PM, Dmitry Osipenko wrote:
> Tegra EMC driver was turned into a regular kernel driver, it also could
> be compiled as a loadable kernel module now. Hence EMC clock isn't
> guaranteed to be available and clk_get("emc") may return -EPROBE_DEFER and
> there is no good reason to
On Wed, Jul 1, 2020 at 1:51 PM Linus Torvalds
wrote:
>
> On Wed, Jul 1, 2020 at 1:36 PM Andy Lutomirski wrote:
> >
> > We ought to be able to do it the way I described and get decent code
> > generation too.
>
> No, we really can't.
>
> Each access really needs to jump to an exception label.
On Thu, 2020-07-02 at 10:43 +1000, Alexey Kardashevskiy wrote:
> > Or should one stick to #define in this case?
>
> imho a matter of taste but after some grepping it feels like #define is
> mostly used which does not mean it is a good idea. Keep it enum and see
> if it passed mpe's filter :)
In commit 0e3b8a81f5df ("spi: spi-geni-qcom: Add interconnect
support") the spi_geni_runtime_suspend() and spi_geni_runtime_resume()
became a bit slower. Measuring on my hardware I see numbers in the
hundreds of microseconds now.
Let's use autosuspend to help avoid some of the overhead. Now if
Every SPI transfer could have a different clock rate. The
spi-geni-qcom controller code to deal with this was never very well
optimized and has always had a lot of code plus some calls into the
clk framework which, at the very least, would grab a mutex. However,
until recently, the overhead
This series tries to reduce a whole bunch of overhead in each SPI
transfer. Much of this overhead is new with the recent interconnect
changes, but even without those changes we still had some overhead
that we could avoid. Let's avoid all of it.
These changes are atop the Qualcomm tree to avoid
There's a bunch of overhead in spi-geni-qcom's prepare_message. Get
rid of it. Before this change spi_geni_prepare_message() took around
14.5 us. After this change, spi_geni_prepare_message() takes about
1.75 us (as measured by ftrace).
What's here:
* We're always in FIFO mode, so no need to
Hi Dmitry,
On 6/9/20 10:13 PM, Dmitry Osipenko wrote:
> Tegra EMC driver was turned into a regular kernel driver, it also could
> be compiled as a loadable kernel module now. Hence EMC clock isn't
Looks good to me. But, you better to add the commit information
about Tegra EMC driver with
From: Danny Lin
Date: Wed, 1 Jul 2020 16:01:52 -0700
> Similar to fq_codel and the other qdiscs that can set as default,
> fq_pie is also suitable for general use without explicit configuration,
> which makes it a valid choice for this.
>
> This is useful in situations where a painless
On 02/07/2020 10:36, Leonardo Bras wrote:
> On Thu, 2020-07-02 at 10:21 +1000, Alexey Kardashevskiy wrote:
>>> enum {
>>>DDW_QUERY_PE_DMA_WIN,
>>>DDW_CREATE_PE_DMA_WIN,
>>>DDW_REMOVE_PE_DMA_WIN,
>>>
>>>DDW_APPLICABLE_SIZE
>>> }
>>> IMO, it looks better than all
On Wed, 1 Jul 2020 23:34:32 +0200 Michael Walle wrote:
> ENETC has ethernet MACs capable of SGMII, 2500BaseX and USXGMII. But in
> order to use these protocols some SerDes configurations need to be
> performed. The SerDes is configurable via an internal PCS PHY which is
> connected to an internal
On 2020/7/1 17:06, Christoph Hellwig wrote:
> Except for pktdvd, the only places setting congested bits are file
> systems that allocate their own backing_dev_info structures. And
> pktdvd is a deprecated driver that isn't useful in stack setup
> either. So remove the dead congested_fn stacking
On Thu, 2020-07-02 at 10:21 +1000, Alexey Kardashevskiy wrote:
> > enum {
> >DDW_QUERY_PE_DMA_WIN,
> >DDW_CREATE_PE_DMA_WIN,
> >DDW_REMOVE_PE_DMA_WIN,
> >
> >DDW_APPLICABLE_SIZE
> > }
> > IMO, it looks better than all the defines before.
> >
> > What do you think?
On Wed, Jul 01, 2020 at 10:09:47PM +0200, Christoph Hellwig wrote:
> From: "Matthew Wilcox (Oracle)"
>
> This error path returned directly instead of calling sysctl_head_finish().
>
> Fixes: ef9d965bc8b6 ("sysctl: reject gigantic reads/write to sysctl files")
> Signed-off-by: Matthew Wilcox
On 02/07/2020 09:48, Leonardo Bras wrote:
> On Wed, 2020-07-01 at 16:57 -0300, Leonardo Bras wrote:
>>> It is not necessarily "direct" anymore as the name suggests, you may
>>> want to change that. DMA64_PROPNAME, may be. Thanks,
>>>
>>
>> Yeah, you are right.
>> I will change this for next
On Thu, 2020-07-02 at 10:18 +1000, Alexey Kardashevskiy wrote:
>
> On 02/07/2020 00:04, Leonardo Bras wrote:
> > On Wed, 2020-07-01 at 18:17 +1000, Alexey Kardashevskiy wrote:
> > > > +#define DDW_EXT_SIZE 0
> > > > +#define DDW_EXT_RESET_DMA_WIN 1
> > > > +#define
In preparation for supporting the connector outside of the default
network namespace we switch to using these helpers now. As the connector
is still only supported in the default namespace this change is a no-op.
Signed-off-by: Matt Bennett
---
drivers/connector/cn_proc.c | 48
Move to storing the connector instance per network namespace. In doing
so the ability to use the connector functionality outside the default
namespace is now available.
Signed-off-by: Matt Bennett
---
drivers/connector/cn_proc.c | 49 ++
drivers/connector/connector.c | 171
Currently the entry itself appears to be being leaked.
Signed-off-by: Matt Bennett
---
drivers/connector/cn_queue.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/connector/cn_queue.c b/drivers/connector/cn_queue.c
index 49295052ba8b..a82ceeb37f26 100644
---
Extend the existing function definitions / call sites to start
passing the network namespace. For now we still only pass the
default namespace.
Signed-off-by: Matt Bennett
---
Documentation/driver-api/connector.rst | 6 +++---
drivers/connector/cn_proc.c| 5 +++--
In preparation for supporting the connector outside of the default
network namespace we switch to using this function now. As the connector
is still only supported in the default namespace this change is a no-op.
Signed-off-by: Matt Bennett
---
drivers/connector/cn_proc.c | 10 +-
1
Previously the connector functionality could only be used by processes running
in the
default network namespace. This meant that any process that uses the connector
functionality
could not operate correctly when run inside a container. This is a draft patch
series that
attempts to now allow
On 02/07/2020 05:48, Leonardo Bras wrote:
> On Wed, 2020-07-01 at 18:17 +1000, Alexey Kardashevskiy wrote:
>>
>> On 24/06/2020 16:24, Leonardo Bras wrote:
>>> On LoPAR "DMA Window Manipulation Calls", it's recommended to remove the
>>> default DMA window for the device, before attempting to
On 01/07/2020 23:28, Leonardo Bras wrote:
> On Wed, 2020-07-01 at 18:16 +1000, Alexey Kardashevskiy wrote:
>>
>> On 24/06/2020 16:24, Leonardo Bras wrote:
>>> Create defines to help handling ibm,ddw-applicable values, avoiding
>>> confusion about the index of given operations.
>>>
>>>
On 02/07/2020 00:04, Leonardo Bras wrote:
> On Wed, 2020-07-01 at 18:17 +1000, Alexey Kardashevskiy wrote:
>>
>>> +#define DDW_EXT_SIZE 0
>>> +#define DDW_EXT_RESET_DMA_WIN 1
>>> +#define DDW_EXT_QUERY_OUT_SIZE 2
>>
>> #define DDW_EXT_LAST (DDW_EXT_QUERY_OUT_SIZE + 1)
>>
Binding description for Intel Keem Bay eMMC PHY.
Signed-off-by: Wan Ahmad Zainie
---
.../bindings/phy/intel,keembay-emmc-phy.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml
diff --git
Add support for eMMC PHY on Intel Keem Bay SoC.
Signed-off-by: Wan Ahmad Zainie
---
drivers/phy/intel/Kconfig| 12 +
drivers/phy/intel/Makefile | 1 +
drivers/phy/intel/phy-keembay-emmc.c | 314 +++
3 files changed, 327 insertions(+)
create mode
Hi.
The first part is to document DT bindings for Keem Bay eMMC PHY.
The second is the driver file, loosely based on phy-rockchip-emmc.c
and phy-intel-emmc.c. The latter is not being reused as there are
quite a number of differences i.e. registers offset, supported clock
rates, bitfield to set.
On Wed, Jul 01, 2020 at 07:52:58AM -0700, Randy Dunlap wrote:
> On 7/1/20 6:32 AM, Markus Elfring wrote:
> >>> How do you think about to use the following command variant
> >>> for the adjustment of the software documentation?
> >>>
> >>> +make C=1 CHECK='scripts/coccicheck' 'path/to/file.o'
>
On Wed, Jul 1, 2020 at 12:30 PM Masahiro Yamada wrote:
>
> When you clean the build tree for ARCH=arm, you may see the following
> error message:
>
> $ make -j24 ARCH=arm clean
> CLEAN arch/arm/crypto
> CLEAN arch/arm/kernel
> CLEAN arch/arm/mach-at91
> CLEAN arch/arm/mach-omap2
>
On Wed, Jul 01, 2020 at 02:02:42PM -0700, Linus Torvalds wrote:
> So the objtool rule might be:
>
> - in a STAC region, no exception handlers at all except for that
> ex_handler_uaccess case
>
> - and that case will clear AC if it triggers.
>
> and maybe such an objtool check would show some
Will it affect TLB? I mean maybe cause TLB miss.
On Wed, 2020-07-01 at 16:57 -0300, Leonardo Bras wrote:
> > It is not necessarily "direct" anymore as the name suggests, you may
> > want to change that. DMA64_PROPNAME, may be. Thanks,
> >
>
> Yeah, you are right.
> I will change this for next version, also changing the string name to
> reflect
On Wed, 01 Jul 2020 19:17:24 -0400
Steven Rostedt wrote:
> +}
> +
> +$mail_command =~ s/\$HEADER_FILE/$header_file/g;
> $mail_command =~ s/\$MAILER/$mailer/g;
> $mail_command =~ s/\$MAIL_PATH/$mail_path/g;
> $mail_command =~ s/\$MAILTO/$mailto/g;
> $mail_command =~
01.07.2020 20:10, Georgi Djakov пишет:
> Hi Dmitry,
>
> On 6/9/20 16:13, Dmitry Osipenko wrote:
>> From: Artur Świgoń
>>
>> This patch relaxes the condition in of_icc_get_from_provider() so that it
>> is no longer required to set #interconnect-cells = <1> in the DT. In case
>> of the devfreq
01.07.2020 20:12, Georgi Djakov пишет:
> Hi Dmitry,
>
> Thank you for updating the patches!
Hello, Georgi!
Thank you for the review!
> On 6/9/20 16:13, Dmitry Osipenko wrote:
>> Now memory controller is a memory interconnection provider. This allows us
>> to use interconnect API in order to
On Tue, Jun 30, 2020 at 09:32:27PM +, Vineeth Remanan Pillai wrote:
> From: Peter Zijlstra
>
> Instead of only selecting a local task, select a task for all SMT
> siblings for every reschedule on the core (irrespective which logical
> CPU does the reschedule).
>
> There could be races in
From: Dan Carpenter
If the second exfat_get_dentry() call fails then we need to release
"old_bh" before returning. There is a similar bug in exfat_move_file().
Fixes: 5f2aa075070c ("exfat: add inode operations")
Cc: sta...@vger.kernel.org # v5.7
Reported-by: Markus Elfring
Signed-off-by: Dan
Could you please push exfat stable patches into 5.7.y kernel tree ?
Thanks!
Dan Carpenter (1):
exfat: add missing brelse() calls on error paths
Hyeongseok.Kim (1):
exfat: Set the unused characters of FileName field to the value h
Hyunchul Lee (1):
exfat: call sync_filesystem for
From: Sungjong Seo
generic_file_fsync() exfat used could not guarantee the consistency of
a file because it has flushed not dirty metadata but only dirty data pages
for a file.
Instead of that, use exfat_file_fsync() for files and directories so that
it guarantees to commit both the metadata
Move setting VOL_DIRTY over exfat_remove_entries() to avoid unneeded
leaving VOL_DIRTY on -ENOTEMPTY.
Fixes: 5f2aa075070c ("exfat: add inode operations")
Cc: sta...@vger.kernel.org # v5.7
Reported-by: Tetsuhiro Kohada
Reviewed-by: Sungjong Seo
Signed-off-by: Namjae Jeon
---
fs/exfat/namei.c |
From: "Hyeongseok.Kim"
Some fsck tool complain that padding part of the FileName field
is not set to the value h. So let's maintain filesystem cleaner,
as exfat's spec. recommendation.
Fixes: ca06197382bd ("exfat: add directory operations")
Cc: sta...@vger.kernel.org # v5.7
Signed-off-by:
From: Hyunchul Lee
We need to commit dirty metadata and pages to disk
before remounting exfat as read-only.
This fixes a failure in xfstests generic/452
generic/452 does the following:
cp something /
mount -o remount,ro
the /something is corrupted. because while
exfat is remounted as
On Wed, Jul 01, 2020 at 06:35:04PM +0200, Juri Lelli wrote:
> Guess you might be faster to understand what I'm missing. :-)
So, did you port only this patch or the whole set in order to
trigger this?
If it was the whole set, can you try this patch alone?
Thanks!
From: "Steven Rostedt (VMware)"
Currently, if a PRE_TEST is defined and ran, but fails, there's nothing
currently available to make the test fail too. Add a PRE_TEST_DIE option that
when set, if a PRE_TEST is defined and fails, the test will die too.
Signed-off-by: Steven Rostedt (VMware)
---
From: "Steven Rostedt (VMware)"
There is a NOT DEFINED operator, but there is not an operator that can
negate any other expression.
For example: NOT (${FOO} == boot || ${BAR} == run)
Add the keyword NOT to allow the ktest.pl config files to negate operators.
Signed-off-by: Steven Rostedt
From: "Steven Rostedt (VMware)"
Currently, every write to the log file is done by opening the file, writing
to it, then closing the file. This rather expensive. Just open it at the
beginning and close it at the end.
Signed-off-by: Steven Rostedt (VMware)
---
tools/testing/ktest/ktest.pl | 24
Steven Rostedt (VMware) (8):
ktest.pl: Have config-bisect save each config used in the bisect
ktest.pl: Always show log file location if defined even on success
ktest.pl: Define PRE_TEST_DIE to kill the test if the PRE_TEST fails
ktest.pl: Add a NOT operator
From: "Steven Rostedt (VMware)"
When performing a automatic config bisect via ktest.pl, it is very useful to
have a copy of each of the bisects used. This way, if a bisect were to go
wrong, it is possible to retrace the steps and continue at the location
before the error was made.
The ktest.pl
From: "Steven Rostedt (VMware)"
If a log file is defined and the test were to error, a print statement is
made that shows the user where the log file is to examine it further. But
this is not done if the test were to succeed.
I find it annoying that it does not show where the log file is on
From: "Steven Rostedt (VMware)"
The log file should be up to date to whatever is happening in ktest.
Disable buffering to the LOG output file handle.
Signed-off-by: Steven Rostedt (VMware)
---
tools/testing/ktest/ktest.pl | 2 ++
1 file changed, 2 insertions(+)
diff --git
From: "Steven Rostedt (VMware)"
If a failure happens and an email is sent, show the contents of the log of
the last test that failed in the email.
Cc: Greg KH
Signed-off-by: Steven Rostedt (VMware)
---
tools/testing/ktest/ktest.pl | 44
1 file changed, 40
From: "Steven Rostedt (VMware)"
Add the ktest config option MAIL_MAX_SIZE that will limit the size of the
log file that is placed into the email on failure.
Cc: Greg KH
Signed-off-by: Steven Rostedt (VMware)
---
tools/testing/ktest/ktest.pl| 12 +++-
Hi Kaaira,
On 01/07/2020 14:29, Kaaira Gupta wrote:
> Change the argument of type char * to const char * for function
> tpg_gen_text().
>
> This function should take in a const char pointer as opposed to a char
> * as there is no modification. This issue was found while passing the
> order of
Hi Kaaira,
On 01/07/2020 14:29, Kaaira Gupta wrote:
> Add a control in VIMC to display information such as the correct order of
> colors for a given test pattern, counter, brightness, hue, saturation,
> contrast, width and height at sensor over test image.
>
> Signed-off-by: Kaaira Gupta
>
On Wed, Jul 1, 2020 at 7:33 AM Laurent Pinchart
wrote:
>
> Hi Rob,
>
> On Mon, Jun 29, 2020 at 04:30:11PM -0600, Rob Herring wrote:
> > On Mon, 29 Jun 2020 15:00:52 +0300, Laurent Pinchart wrote:
> > > From: Anurag Kumar Vulisha
> > >
> > > Add DT bindings for the Xilinx ZynqMP PHY. ZynqMP SoCs
On Saturday, June 27, 2020 12:24 CEST, David Laight wrote:
> The code quoted (using strset()) is almost certainly wrong.
> The caller is unlikely to expect the input be modified.
> Since it doesn't fault the string must be in read-write memory.
I tried writing a patch that avoids the
Similar to fq_codel and the other qdiscs that can set as default,
fq_pie is also suitable for general use without explicit configuration,
which makes it a valid choice for this.
This is useful in situations where a painless out-of-the-box solution
for reducing bufferbloat is desired but fq_codel
Nouveau currently only supports mapping PAGE_SIZE sized pages of system
memory when shared virtual memory (SVM) is enabled. Use the new
hmm_pfn_to_map_order() function to support mapping system memory pages
that are PMD_SIZE.
Signed-off-by: Ralph Campbell
---
Add a sanity test for hmm_range_fault() returning the page mapping size
order.
Signed-off-by: Ralph Campbell
---
lib/test_hmm.c | 4 ++
lib/test_hmm_uapi.h| 4 ++
tools/testing/selftests/vm/hmm-tests.c | 76 ++
3 files
The nvif_object_ioctl() method NVIF_VMM_V0_PFNMAP wasn't correctly
setting the hardware specific GPU page table entries for 2MB sized
pages. Fix this by adding functions to set and clear PD0 GPU page
table entries.
Signed-off-by: Ralph Campbell
---
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c
hmm_range_fault() returns an array of page frame numbers and flags for
how the pages are mapped in the requested process' page tables. The PFN
can be used to get the struct page with hmm_pfn_to_page() and the page
size order can be determined with compound_order(page) but if the page
is larger
The goal for this series is to introduce the hmm_pfn_to_map_order()
function. This allows a device driver to know that a given 4K PFN is
actually mapped by the CPU using a larger sized CPU page table entry and
therefore the device driver can safely map system memory using larger
device MMU PTEs.
The SVM page fault handler groups faults into a range of contiguous
virtual addresses and requests hmm_range_fault() to populate and
return the page frame number of system memory mapped by the CPU.
In preparation for supporting large pages to be mapped by the GPU,
process faults one page at a
From: Jarod Wilson
Date: Tue, 30 Jun 2020 14:49:41 -0400
> At the moment, bonding xfrm crypto offload can only be set up if the bonding
> module is loaded with active-backup mode already set. We need to be able to
> make this work with bonds set to AB after the bonding driver has already
> been
On 2020-07-01 13:36, Rob Clark wrote:
From: Rob Clark
This can happen a lot when things go pear shaped. Lets not flood dmesg
when this happens.
Signed-off-by: Rob Clark
Reviewed-by: Abhinav Kumar
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1
[+cc Rob, LKML for visibility & archive]
On Wed, Jul 01, 2020 at 12:32:48PM -0300, Fabio Estevam wrote:
> On Tue, Jun 16, 2020 at 8:52 PM Fabio Estevam wrote:
> > I am seeing the following warning on a imx28-evk running linux-next:
> >
> > [7.625012] [ cut here ]
> >
These are not modified so make them const to allow the compiler to put
them in read-only memory.
Before:
textdata bss dec hex filename
255097928 64 3350182dd drivers/video/fbdev/vt8623fb.o
After:
textdata bss dec hex filename
265336904
The PCA9665 datasheet says that I2CSTA = 78h indicates that SCL is stuck
low, this differs to the PCA9564 which uses 90h for this indication.
Treat either 0x78 or 0x90 as an indication that the SCL line is stuck.
Based on looking through the PCA9564 and PCA9665 datasheets this should
be safe for
Hi Randy,
On Wed, 1 Jul 2020 08:47:30 -0700 Randy Dunlap wrote:
>
> From: Randy Dunlap
>
> This stub is no longer needed since the function is no longer
> inside an #ifdef/#endif block.
>
> Fixes this build error:
>
> ../mm/memory-failure.c:180:13: error: redefinition of ‘page_handle_poison’
On Wed, Jul 01, 2020 at 02:13:36PM -0700, Daniel Winkler wrote:
>
> This change regresses the QCA6174A-3 bluetooth chip, preventing
> firmware from being properly loaded. Without this change, the
> chip works as intended.
>
> The device is the Kukui Chromebook using the Mediatek chipset
> and
From: Tao Ren
Create all the i2c switches in device tree and use aliases to assign
child channels with consistent bus numbers.
Besides, "i2c-mux-idle-disconnect" is set for all the i2c switches to
avoid potential conflicts when multiple devices (beind the switches)
use the same device address.
From: Alex Elder
Date: Tue, 30 Jun 2020 08:32:59 -0500
> This series updates code that configures IPA endpoints. The changes
> made mainly affect access to registers that are valid only for RX, or
> only for TX endpoints.
>
> The first three patches avoid writing endpoint registers if they are
allmodconfig
powerpc allnoconfig
i386 randconfig-a011-20200701
i386 randconfig-a015-20200701
i386 randconfig-a014-20200701
i386 randconfig-a016-20200701
i386 randconfig-a012-20200701
i386 randconfi
> Any conclusion on this? I'm still suggesting that just treating 0x78
> and 0x90 as SCL stuck for either chip is the cleanest solution. I
> think I could do something with a fall-through that repeats the check
> with an if which wouldn't be too ugly.
I tried as well and also came up with code
From: Alex Elder
Date: Tue, 30 Jun 2020 07:58:43 -0500
> This series contains two patches that improve the error output
> that's reported when an error occurs while changing the state of a
> GSI channel or event ring. The first ensures all such error
> conditions report an error, and the second
On 7/1/20 12:58 PM, Cong Wang wrote:
On Wed, Jul 1, 2020 at 9:05 AM Cong Wang wrote:
On Tue, Jun 30, 2020 at 2:08 PM Josh Hunt wrote:
Do either of you know if there's been any development on a fix for this
issue? If not we can propose something.
If you have a reproducer, I can look into
From: Alex Elder
Date: Mon, 29 Jun 2020 16:55:20 -0500
> This series makes three small changes to some endpoint configuration
> code. The first uses a constant to represent the frequency of an
> internal clock used for timers in the IPA. The second modifies a
> limit used so it matches
On Wed, 1 Jul 2020 17:00:20 +0800, Leilk Liu wrote:
> this patch use correct SPI_CFG2_REG offset.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: mediatek: use correct SPI_CFG2_REG MACRO
commit:
On Tue, 16 Jun 2020 01:09:26 +0100, Robin Murphy wrote:
> Although Florian was concerned about a trivial inline check to deal with
> shared IRQs adding overhead, the reality is that it would be so small as
> to not be worth even thinking about unless the driver was already tuned
> to squeeze out
On Mon, 22 Jun 2020 18:26:11 +0200, Luc Van Oostenryck wrote:
> The field mspi->reg_base is annotated as an __iomem pointer. Good.
>
> However, this field is often assigned to a temporary variable:
> before being used. For example:
> struct fsl_spi_reg *reg_base = mspi->reg_base;
>
> But
On Mon, 29 Jun 2020 16:41:06 -0700, Douglas Anderson wrote:
> On some SPI controllers (like spi-geni-qcom) setting the chip select
> is a heavy operation. For instance on spi-geni-qcom, with the current
> code, is was measured as taking upwards of 20 us. Even on SPI
> controllers that aren't as
On Mon, 29 Jun 2020 21:46:30 +0200, Rikard Falkeborn wrote:
> Constify some static structs to allow the compiler to put them in
> read-only memory.
>
> Rikard Falkeborn (2):
> regulator: qcom_rpm: Constify struct regulator_ops
> regulator: qcom_spmi: Constify struct regulator_ops
>
> [...]
On Tue, 16 Jun 2020 18:02:32 -0700, Nathan Chancellor wrote:
> Clang warns:
>
> In file included from sound/soc/intel/keembay/kmb_platform.c:14:
> sound/soc/intel/keembay/kmb_platform.h:9:9: warning: 'KMB_PLATFORM_H_'
> is used as a header guard here, followed by #define of a different
>
On Tue, 23 Jun 2020 10:47:46 +0530, Kathiravan T wrote:
> IPQ6018 SoC uses the PMIC MP5496. SMPA2 and LDOA2 regulator of MP5496
> controls the APSS and SDCC voltage scaling respectively. Add support
> for the same.
>
> changes since V1:
> - Moved YAML conversion to the last as per Mark's
On Tue, 30 Jun 2020 14:52:38 +0530, Ravulapati Vishnu vardhan rao wrote:
> When snd_pci_acp3x driver loads we see:
>
> WARNING kernel:snd_pci_acp3x :04:00.5: Unbalanced pm_runtime_enable!
> at boot time.
> same can be observed in /var/log/messages/.
>
> Modifying pm runtime sequence for
On Wed, 1 Jul 2020 17:36:51 +0800, Brent Lu wrote:
> Support MAX98390 speaker amplifier on cometlake platform. Driver now
> detects amplifier type in the probe function and installs corresponding
> controls and DAPM widgets/routes in the late_probe function.
Applied to
On Mon, 22 Jun 2020 22:43:25 +0200, Luca Ceresoli wrote:
> the first patch in this series is a small but significant variation in how
> the lp87565 driver enables the output rails, to allow the kernel to always
> know when it is enabling an output. However it can change existing
> behaviour
On 19 Jun 2020 14:33:36 +0900, Kuninori Morimoto wrote:
> Audio Graph Card is using "audio-graph-card" prefix instead of
> "simple-graph-card", and moreover "widgets / routing" doesn't need it.
> This patch removes unsupported "simple-graph-card" prefix from
> motorola-mapphone-common.dtsi and
On Fri, 26 Jun 2020 11:55:10 -0700, Wesley Cheng wrote:
> Changes in v4:
> - Modified qcom,pmic-typec binding to include the SS mux and the DRD remote
>endpoint nodes underneath port@1, which is assigned to the SSUSB path
>according to usb-connector
> - Added usb-connector reference to
On Wed, 1 Jul 2020 00:07:46 +0530, Akshu Agrawal wrote:
> Fixes interrupt enable condition check with which now
> interrupt gets enabled in dma_open.
> Prior to this patch it was getting enabled in runtime_resume only.
Applied to
On Tue, 30 Jun 2020 17:16:15 +0800, Yu-Hsuan Hsu wrote:
> S8 and S24 formats does not work on this machine driver so force to use
> S16_LE instead.
>
> In addition, add constraint to limit the max value of rate because the
> rate higher than 96000(172000, 192000) is not stable either.
Applied to
On Mon, 29 Jun 2020 14:42:33 +0800, Shengjiu Wang wrote:
> When there is dedicated power domain bound with device, after probing
> the power will be disabled, then registers are not accessible in
> fsl_sai_dai_probe(), so regcache only need to be enabled in end of
> probe() and regcache_mark_dirty
On Tue, 30 Jun 2020 15:58:40 +0300, Peter Ujfalusi wrote:
> Changes since v3:
> - Fix the single clock source handling and typo
>
> Changes since v2:
> - DT binding:
> - use proper (?) patch subject for the binding docuemtn patch
> - drop pll4 and pll15 from DT - driver should check the rate
On Tue, 30 Jun 2020 21:56:07 +0800, Shengjiu Wang wrote:
> The ASRC not only supports ideal ratio mode, but also supports
> internal ratio mode.
>
> For internal rato mode, the rate of clock source should be divided
> with no remainder by sample rate, otherwise there is sound
> distortion.
>
>
On Wed, Jul 1, 2020 at 11:04 AM Yonghong Song wrote:
>
>
>
> On 7/1/20 10:53 AM, Hao Luo wrote:
> > The test_vmlinux test uses hrtimer_nanosleep as hook to test tracing
> > programs. But in a kernel built by clang, which performs more aggresive
> > inlining, that function gets inlined into its
Prabhakar reported an OOPS inside mem_cgroup_get_nr_swap_pages()
function in a corner case seen on some arm64 boards when kdump kernel
runs with "cgroup_disable=memory" passed to the kdump kernel via
bootargs.
The root-cause behind the same is that currently mem_cgroup_swap_init()
function is
Prabhakar recently reported a kdump kernel boot failure on ThunderX2
arm64 plaforms (which I was able to reproduce on ampere arm64 machines
as well), (see [1]), which is seen when a corner case is hit on some
arm64 boards when kdump kernel runs with "cgroup_disable=memory" passed
to the kdump
commit bff3b04460a8 ("arm64: mm: reserve CMA and crashkernel in
ZONE_DMA32") allocates crashkernel for arm64 in the ZONE_DMA32.
However as reported by Prabhakar, this breaks kdump kernel booting in
ThunderX2 like arm64 systems. I have noticed this on another ampere
arm64 machine. The OOM log in
301 - 400 of 1601 matches
Mail list logo
