It is not guaranteed that I2S RX is disabled when the kernel booting.
For example, if the kernel crashes while it is enabled, it will keep
enabled until the next time EC reboots. Reset I2S RX when probing to
fix this issue.
Signed-off-by: Yu-Hsuan Hsu
---
Updated the info message.
Add the new command EC_CODEC_I2S_RX_RESET in ec_codec_i2s_rx_subcmd,
which is used for resetting the EC codec.
Signed-off-by: Yu-Hsuan Hsu
---
include/linux/platform_data/cros_ec_commands.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/platform_data/cros_ec_commands.h
On Thu, 14 Jan 2021, Steven Rostedt wrote:
> [ Forgot to add those on the commit itself ]
>
> -- Steve
>
>
> On Thu, 14 Jan 2021 16:32:06 -0500
> Steven Rostedt wrote:
>
>> On reboot, one of my test boxes now triggers the following warning:
>>
>> [ cut here ]
>> RPM
On 13-01-21, 16:18, Ionela Voinescu wrote:
> On Tuesday 15 Dec 2020 at 16:46:35 (+0530), Viresh Kumar wrote:
> > +void topology_scale_freq_tick(void)
> > +{
> > + struct scale_freq_tick_data *sftd = *this_cpu_ptr(_data);
> > +
> > + if (sftd)
> > + sftd->scale_freq();
> > +}
>
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 146620506274bd24d52fb1c589110a30eed8240b
commit: 4104a562e0ca62e971089db9d3c47794a0d7d4eb sched/core: Annotate curr
pointer in rq with __rcu
date: 11 months ago
config: x86_64-randconfig-s032-20210115
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: b86cb29287be07041b81f5611e37ae9ffabff876
Gitweb:
https://git.kernel.org/tip/b86cb29287be07041b81f5611e37ae9ffabff876
Author:Tom Rix
AuthorDate:Thu, 14 Jan 2021 13:28:27 -08:00
Committer:
On 2021/1/13 2:37, Hans de Goede wrote:
Hi,
I know there already is a v3 out and I will try to get around to reviewing
that soon, still 1 remark about the discussion surrounding v2:
On 1/11/21 2:42 PM, Perry Yuan wrote:
*The flow is like this:
1) User presses key. HW does stuff with this
On 1/14/21 11:10 PM, Valdis Klētnieks wrote:
> Correct the spelling of Nagle's name in a comment.
>
> Signed-off-by: Valdis Kletnieks
Looks good.
Reviewed-by: Chaitanya Kulkarni
Hi Ian,
On Fri, Jan 15, 2021 at 6:23 AM Ian Rogers wrote:
>
> The variable bf is read (for a write call) without being initialized
> triggering a memory sanitizer warning. Use bf in the read and switch the
> write to reading from a string.
>
> Signed-off-by: Ian Rogers
Acked-by: Namhyung Kim
From: Palmer Dabbelt
cdn_dp_resume is only used under PM_SLEEP, and now that it's static an
unused function warning is triggered undner !PM_SLEEP. This
conditionally enables the function to avoid the warning.
Fixes: 7c49abb4c2f8 ("drm/rockchip: cdn-dp-core: Make
cdn_dp_core_suspend/resume
On Thu, 14 Jan 2021, Russ Weight wrote:
> Create two sysfs entries for exposing the MAC address
> and count from the MAX10 BMC register space. The MAC
> address is the first in a sequential block of MAC addresses
> reserved for the FPGA card. The MAC count is the number
> of MAC addresses in the
Hello,
On Thu, Jan 14, 2021 at 8:17 PM Michael Ellerman wrote:
>
> Namhyung Kim writes:
> > On Wed, Jan 13, 2021 at 8:43 PM Jiri Slaby wrote:
> >>
> >> On 13. 01. 21, 11:46, Jiri Olsa wrote:
> >> > On Wed, Jan 13, 2021 at 09:01:28AM +0100, Jiri Slaby wrote:
> >> >> With LTO, there are symbols
This patch adds dts entry for some peripherials:
- i2c: temperature sensor ADT7461
- i2c: eeprom m24256
- i2c: eeprom at24c01
- i2c: pmic zl2006
- i2c: gpio expander
- phy: reset pins for phy
- dsa: switch vsc7385
It was required to adjust rgmii settings for enet0 because switch with
dsa driver
On Fri, Jan 15, 2021 at 1:41 AM Alexander Antonov
wrote:
> On 1/14/2021 6:39 AM, Namhyung Kim wrote:
> > On Wed, Jan 13, 2021 at 9:08 PM Alexander Antonov
> > wrote:
> >>
> >> On 1/6/2021 12:02 PM, Namhyung Kim wrote:
> >>> On Wed, Dec 23, 2020 at 10:03 PM Alexander Antonov
> diff --git
On Fri, 15 Jan 2021, Gene Chen wrote:
> Matthias Brugger 於 2021年1月12日 週二 下午8:32寫道：
> >
> >
> >
> > On 12/11/2020 11:39, Gene Chen wrote:
> > > From: Gene Chen
> > >
> > > Combine mt6360 pmic/ldo resources into mt6360 regulator resources
> > > to simplify the similar resources object.
> > >
> >
Hello,
On Fri, Jan 15, 2021 at 12:46 AM Leo Yan wrote:
>
> This patch series is for several minor code refactoring, which is
> extracted from the patch series "perf c2c: Sort cacheline with all
> loads" [1].
>
> There has a known issue for Arm SPE store operations and Arm SPE is
> the only
Hi,
There is currently a bit of a debate about the kernel direct map. Does
using 2M/1G pages aggressively for the kernel direct map help
performance? Or, is it an old optimization which is not as helpful on
modern CPUs as it was in the old days? What is the penalty of a kernel
feature that
From: Ryan Houdek
Problem presented:
A backwards compatibility layer that allows running x86-64 and x86
processes inside of an AArch64 process.
- CPU is emulated
- Syscall interface is mostly passthrough
- Some syscalls require patching or emulation depending on behaviour
- Not viable
As of now it doesn't consider cgroups when collecting shadow stats and
metrics so counter values from different cgroups will be saved in a
same slot. This resulted in an incorrect numbers when those cgroups
have different workloads.
For example, let's look at the below - the cgroup A and C runs
To pass more info to the saved_value in the runtime_stat, add a new
struct runtime_stat_data. Currently it only has 'ctx' field but later
patch will add more.
Note that we intentionally pass 0 as ctx to clock-related events for
compatibility. It was already there in a few places. So move the
Hi Arnd,
On 2021/1/14 0:14, Arnd Bergmann wrote:
> On Fri, Jan 8, 2021 at 11:55 PM Arnd Bergmann wrote:
>
> Just to catch up on the replies I received on my initial email, here
> is the updated status of all the Arm platforms I listed earlier, thanks
> for everyone that contributed information
Correct the spelling of Nagle's name in a comment.
Signed-off-by: Valdis Kletnieks
diff --git a/drivers/target/iscsi/iscsi_target_login.c
b/drivers/target/iscsi/iscsi_target_login.c
index 893d1b406c29..1a9c50401bdb 100644
--- a/drivers/target/iscsi/iscsi_target_login.c
+++
When suspending the driver, anx7625_power_standby() will be called to
turn off reset-gpios and enable-gpios. However, power supplies are not
disabled. To save power, the driver can get the power supply regulators
and turn off them in anx7625_power_standby().
Signed-off-by: Hsin-Yi Wang
---
On Thu, 14 Jan 2021 at 22:54, Fangrui Song wrote:
> clang-12 -fno-pic (since
> https://github.com/llvm/llvm-project/commit/a084c0388e2a59b9556f2de008232da3f1d6)
> can emit `call __stack_chk_fail@PLT` instead of `call __stack_chk_fail`
> on x86. The two forms should have identical behaviors
From: Ryan Houdek
Problem presented:
A backwards compatibility layer that allows running x86-64 and x86
processes inside of an AArch64 process.
- CPU is emulated
- Syscall interface is mostly passthrough
- Some syscalls require patching or emulation depending on behaviour
- Not viable
anx7625 requires 3 power supply regulators.
Signed-off-by: Hsin-Yi Wang
Reviewed-by: Rob Herring
---
.../bindings/display/bridge/analogix,anx7625.yaml | 15 +++
1 file changed, 15 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
On Thu, Jan 14, 2021 at 10:22 PM Jiri Olsa wrote:
>
> On Thu, Jan 14, 2021 at 12:25:39PM +0900, Namhyung Kim wrote:
> > Hi Jiri,
> >
> > On Wed, Jan 13, 2021 at 8:19 PM Jiri Olsa wrote:
> > >
> > > On Tue, Jan 12, 2021 at 03:14:30PM +0900, Namhyung Kim wrote:
> > > > To pass more info to the
On 1/12/21 8:01 AM, Paolo Bonzini wrote:
> On 12/01/21 07:37, Wei Huang wrote:
>> static int gp_interception(struct vcpu_svm *svm)
>> {
>> struct kvm_vcpu *vcpu = >vcpu;
>> u32 error_code = svm->vmcb->control.exit_info_1;
>> -
>> - WARN_ON_ONCE(!enable_vmware_backdoor);
>> +
Hi Jonathan,
thanks for your interesting article, MAINTAINERS truth and fiction,
https://lwn.net/Articles/842415/.
Just some pointers to related work:
Pia Eichinger has done some related analysis and work in this area as
part of her bachelor's thesis on Maintainers Expectations vs.
Maintainers
Adding appropriate mailing list to cc...
My wild guess is that as soon as socket got created:
socket(PF_PACKET, SOCK_RAW, htons(ETH_P_ALL));
the packets were already queued to it.
So later setsockopt() is too late to filter.
Eric, thoughts?
On Wed, Jan 6, 2021 at 6:55 AM Tom Cook wrote:
>
>
Hi all,
Changes since 20210114:
The drm tree still had its build failure so I used the version from
next-20210107.
The amdgpu tree gained a conflict against Linus' tree. It also gained
a build failure for which I disabled CONFIG_DRM_AMDGPU.
The drm-intel tree still had its build failure from
Hi Eric,
On Tue, Jan 12, 2021 at 2:52 PM Auger Eric wrote:
>
> Hi Vikas,
>
> On 12/14/20 6:45 PM, Vikas Gupta wrote:
> > Add msi support for Broadcom platform devices
> >
> > Signed-off-by: Vikas Gupta
> > ---
> > drivers/vfio/platform/Kconfig | 1 +
> >
OR on linus/master]
> [also build test ERROR on v5.11-rc3 next-20210114]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
>
> url:
> h
On Jan 15 07:30, Klaus Jensen wrote:
> From: Klaus Jensen
>
> Since NVMe v1.4 the Controller Memory Buffer must be explicitly enabled
> by the host.
>
Sorry, messed up and missed adding the changes for v2.
v2:
- Do not explicitly check the NVMe version, rely on the presence of
the new
On Fri, Jan 15, 2021 at 07:49:47AM +0800, Lu Baolu wrote:
> Hi Leon,
>
> On 1/14/21 9:26 PM, Leon Romanovsky wrote:
> > On Thu, Jan 14, 2021 at 09:30:02AM +0800, Lu Baolu wrote:
> > > Some vendor IOMMU drivers are able to declare that it is running in a VM
> > > context. This is very valuable for
From: Klaus Jensen
Since NVMe v1.4 the Controller Memory Buffer must be explicitly enabled
by the host.
Signed-off-by: Klaus Jensen
---
drivers/nvme/host/pci.c | 13 -
include/linux/nvme.h| 6 ++
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git
On Fri, Jan 15, 2021 at 02:32:39AM +, zhangqiumiao wrote:
> On Thu, Jan 14, 2021 at 08:28:30PM +0800, zhangqiumi...@huawei.com wrote:
> > From: Qiumiao Zhang
> >
> > make pl011 serial port support 485 mode full duplex communication
> >
> > Signed-off-by: Qiumiao Zhang
> > ---
> > Changes
Hi Eric,
On Tue, Jan 12, 2021 at 2:30 PM Auger Eric wrote:
>
> Hi Vikas,
>
> On 1/5/21 6:53 AM, Vikas Gupta wrote:
> > On Tue, Dec 22, 2020 at 10:57 PM Auger Eric wrote:
> >>
> >> Hi Vikas,
> >>
> >> On 12/14/20 6:45 PM, Vikas Gupta wrote:
> >>> MSI support for platform devices.The MSI block
>
allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a002-20210114
i386 randconfig-a005
On Fri, 8 Jan 2021 16:16:53 +, Mark Brown wrote:
> On Fri, Jan 08, 2021 at 03:16:48PM +, Timon Baetz wrote:
>
> > Muic needs a node to be used with extcon_get_edev_by_phandle().
> > Charger needs a node to reference a regulator.
>
> The pattern is to use the parent device's node.
So
From: Pierre-Louis Bossart
The resume operation relies on multiple transactions to synchronize
the regmap state, make sure the timeout is one order of magnitude
larger than an individual transaction, so that timeouts of failed
transactions are detected first.
Signed-off-by: Pierre-Louis Bossart
From: Pierre-Louis Bossart
Currently the timeout for SoundWire individual transactions is 2s.
This is too large in comparison with the enumeration and completion
timeouts used in codec drivers.
A command will typically be handled in less than 100us, so 500ms for
the command completion is more
The timeout for an individual transaction w/ the Cadence IP is the same as
the entire resume operation for codecs.
This doesn't make sense, we need to have at least one order of magnitude
between individual transactions and the entire resume operation.
Set the timeout on the Cadence side to 500ms
On 30-12-20, 10:12, Viresh Kumar wrote:
> This patch fixes a bunch of sparse warnings in the newly added arm_mhuv2
> driver.
>
> drivers/mailbox/arm_mhuv2.c:506:24: warning: incorrect type in argument 1
> (different address spaces)
> drivers/mailbox/arm_mhuv2.c:506:24:expected void const
[reduced the recipient list to the main responsible ones and list]
Hi Mauro, hi Jonathan,
We both, Mauro and I, have been submitting patches to address the
documentation warnings on linux-next. If it is okay with you, Mauro, I
would like to take responsibility for the task to send out the
UDP/IP header of UDP GROed frag_skbs are not updated even after NAT
forwarding. Only the header of head_skb from ip_finish_output_gso ->
skb_gso_segment is updated but following frag_skbs are not updated.
A call path skb_mac_gso_segment -> inet_gso_segment ->
udp4_ufo_fragment ->
From: Hongtao Wu
This series adds PCIe bindings for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Reviewed-by: Rob Herring
Signed-off-by: Hongtao Wu
---
.../devicetree/bindings/pci/sprd-pcie.yaml | 93 ++
1 file changed, 93 insertions(+)
create
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Changes from v1:
1) Test this patch on top of Rob Herring's 40 part series of DWC clean-ups:
https://lore.kernel.org/linux-pci/20200821035420.380495-1-r...@kernel.org/
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Signed-off-by: Hongtao Wu
---
drivers/pci/controller/dwc/Kconfig | 12 ++
drivers/pci/controller/dwc/Makefile| 1 +
drivers/pci/controller/dwc/pcie-sprd.c | 293
On Thu, 14 Jan 2021 at 07:35, Jarkko Sakkinen wrote:
>
> On Wed, Jan 13, 2021 at 04:47:00PM +0530, Sumit Garg wrote:
> > Hi Jarkko,
> >
> > On Mon, 11 Jan 2021 at 22:05, Jarkko Sakkinen wrote:
> > >
> > > On Tue, Nov 03, 2020 at 09:31:44PM +0530, Sumit Garg wrote:
> > > > Add support for TEE
On 2021/1/15 11:17, Tejun Heo wrote:
> Hello,
>
> On Fri, Jan 15, 2021 at 09:55:43AM +0800, chenzhou wrote:
>> Yeah, this will select all enabled controllers, but which doesn't the
>> behavior we want.
>> I think the case should return error with information "Disabled controller
>> xx" rather
On 14-01-21, 01:20, mda...@codeaurora.org wrote:
> On 2021-01-12 15:40, Vinod Koul wrote:
> > On 12-01-21, 15:01, mda...@codeaurora.org wrote:
> > > On 2020-12-21 23:03, mda...@codeaurora.org wrote:
> > > > On 2020-12-21 14:53, Vinod Koul wrote:
> > > > > Hello,
> > > > >
> > > > > On 17-12-20,
On Fri, Jan 15, 2021 at 01:35:05PM +0800, Stephen Rothwell wrote:
> Hi all,
>
> After merging the amdgpu tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c: In function
> 'vangogh_get_smu_metrics_data':
>
On 14-01-21, 10:11, Jon Hunter wrote:
>
> On 06/08/2020 08:30, Rajesh Gumasta wrote:
> > Changes in patch v2:
> > Addressed review comments in patch v1
>
>
> Is there any update on this series? Would be good to get this upstream.
Not sure why, this is is not in my queue, can someone please
GL9763E enters ASPM L1 state after a very short idle in default,
even during a burst of request. So the R/W performance of GL9763E
is low with some platforms, which support ASPM mechanism, due to
entering ASPM L1 state very frequently in R/W process. Set the L1
entry delay bits in vendor-specific
> Ulf Hansson 於 2021年1月14日 週四 下午8:04寫道：
>
> On Thu, 14 Jan 2021 at 07:25, 陳建宏 wrote:
> >
> > > Ulf Hansson 於 2021年1月13日 週三 下午6:53寫道：
> > >
> > > On Wed, 6 Jan 2021 at 10:27, Renius Chen wrote:
> > > >
> > > > The R/W performance of GL9763E is low with some platforms, which
> > > > support ASPM
On 1/15/2021 12:59 PM, Bae, Chang Seok wrote:
On Jan 11, 2021, at 18:52, Liu, Jing2 wrote:
On 1/8/2021 2:40 AM, Bae, Chang Seok wrote:
On Jan 7, 2021, at 17:41, Liu, Jing2 wrote:
static void kvm_save_current_fpu(struct fpu *fpu) {
+ struct fpu *src_fpu = >thread.fpu;
+
/*
Hello Mathieu, Suzuki
On 2020-10-15 21:32, Mathieu Poirier wrote:
On Thu, Oct 15, 2020 at 06:15:22PM +0530, Sai Prakash Ranjan wrote:
On production systems with ETMs enabled, it is preferred to
exclude kernel mode(NS EL1) tracing for security concerns and
support only userspace(NS EL0)
This adds transport ops and removes ignore of non-stream type of packets.
Signed-off-by: Arseny Krasnov
---
drivers/vhost/vsock.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c
index 5e78fb719602..4d60a99aed14 100644
---
This adds two tests of SOCK_SEQPACKET socket: both transfer data and then
test MSG_EOR and MSG_TRUNC flags. Cases for connect(), bind(), etc. are
not tested, because it is same as for stream socket.
Signed-off-by: Arseny Krasnov
---
tools/testing/vsock/util.c | 32 ++--
+David,
On 14-01-21, 09:01, Rob Herring wrote:
> On Wed, Jan 13, 2021 at 11:03 PM Viresh Kumar wrote:
> >
> > On 11-01-21, 09:46, Rob Herring wrote:
> > > On Fri, Jan 8, 2021 at 2:41 AM Viresh Kumar
> > > wrote:
> > > >
> > > > Now that fdtoverlay is part of the kernel build, start using it to
On 2021/1/15 10:33, Palmer Dabbelt wrote:
On Wed, 13 Jan 2021 18:33:58 PST (-0800), wangkefeng.w...@huawei.com
wrote:
The ARM and riscv have same logic to check and reserve
the memory of initrd, let's provide a common function to
reduce duplicated code.
Add __LINUX_INITRD_H define in
This adds rest of logic for SEQPACKET:
1) Shared functions for packet sending now set valid type of packet
according socket type.
2) SEQPACKET specific function like SEQ_BEGIN send and data dequeue.
3) Ops for virtio transport.
4) TAP support for SEQPACKET is not so easy if it is necessary to
This modifies current receive logic for SEQPACKET support:
1) Add 'SEQ_BEGIN' packet to socket's rx queue.
2) Add 'RW' packet to rx queue, but without merging inside buffer of last
packet in queue.
3) Perform check for packet type and socket type on receive(if mismatch,
then reset
This adds transport callback and it's logic for SEQPACKET dequeue.
Callback fetches RW packets from rx queue of socket until whole record
is copied(if user's buffer is full, user is not woken up). This is done
to not stall sender, because if we wake up user and it leaves syscall,
nobody will send
This adds transport callback which tries to fetch record begin marker from
socket's rx queue. It is called from af_vsock.c before reading data
packets of record.
Signed-off-by: Arseny Krasnov
---
include/linux/virtio_vsock.h| 1 +
net/vmw_vsock/virtio_transport_common.c | 33
This replaces 'stream' to 'connect oriented' in comments as SEQPACKET is
also connect oriented.
Signed-off-by: Arseny Krasnov
---
net/vmw_vsock/af_vsock.c | 31 +--
1 file changed, 17 insertions(+), 14 deletions(-)
diff --git a/net/vmw_vsock/af_vsock.c
This adds socket operations for SOCK_SEQPACKET and adds this type of
socket for conditions where SOCK_STREAM is involved because both type of
sockets are connect oriented.
Signed-off-by: Arseny Krasnov
---
net/vmw_vsock/af_vsock.c | 108 +--
1 file changed,
This adds some logic to current stream enqueue function for SEQPACKET
support:
1) Send record begin marker with length of record.
2) Return value from enqueue function is wholevrecord length or error for
SOCK_SEQPACKET.
Signed-off-by: Arseny Krasnov
---
include/net/af_vsock.h | 1 +
This forces reading the base folded state anytime the device is
probed, to make sure it's in sync.
This is useful after a reboot, if the device re-enumerates for
any reason (e.g. ESD shock), or if the driver is unbound/rebound
(debugging/testing).
Without this, the tablet switch state is only
This removes previous 'vsock_stream_recvmsg()' and uses newly implemented
receive loops. Moved to separate patch to make review easier.
Signed-off-by: Arseny Krasnov
---
net/vmw_vsock/af_vsock.c | 184 +++
1 file changed, 12 insertions(+), 172 deletions(-)
This adds entry point for STREAM/SEQPACKET rx loops. As both types are
connect oriented, so there are same checks before reading data from
socket. All this checks are performed in this entry point, then specific
rx loop is called.
Signed-off-by: Arseny Krasnov
---
net/vmw_vsock/af_vsock.c | 55
This adds two receive loops: for SOCK_STREAM and SOCK_SEQPACKET. Both are
look like twins, but SEQPACKET is a little bit different from STREAM:
1) It doesn't call notify callbacks.
2) It doesn't care about 'SO_SNDLOWAT' and 'SO_RCVLOWAT' values, because
there is no sense for these values in
Some architectures(eg, ARM and riscv) have similar logic to
check and reserve the memory of initrd, let's provide a common
function reserve_initrd_mem() to reduce duplicated code.
Signed-off-by: Kefeng Wang
---
include/linux/initrd.h | 6 ++
init/initramfs.c | 45
Covert to the generic reserve_initrd_mem() function.
Signed-off-by: Kefeng Wang
---
arch/riscv/mm/init.c | 54 +---
1 file changed, 1 insertion(+), 53 deletions(-)
diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index bf5379135e39..1eaae54c8ea1
Covert to the generic reserve_initrd_mem() function.
Signed-off-by: Kefeng Wang
---
arch/arm/mm/init.c | 43 +--
1 file changed, 1 insertion(+), 42 deletions(-)
diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
index 828a2561b229..a29e14cd626c 100644
Add the preprocessor guard in initrd.h to prevent possible
build error from the multiple inclusion of same header file
multiple time.
Signed-off-by: Kefeng Wang
---
include/linux/initrd.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/linux/initrd.h b/include/linux/initrd.h
Use the same implementation of initrd reserve to avoid duplication.
v3:
- split into four patches, suggested-by Palmer Dabbelt
v2:
- fix build error found by kernel test robot
Kefeng Wang (4):
initrd: Add the preprocessor guard in initrd.h
initramfs: Provide a common initrd reserve function
This adds 'vsock_wait_data()' function which is called from user's read
syscall and waits until new socket data is arrived. It was based on code
from stream dequeue logic and moved to separate function because it will
be called both from SOCK_STREAM and SOCK_SEQPACKET receive loops.
From: Pierre-Louis Bossart
There are too many logs on startup, e.g.
[ 8811.851497] cdns_fill_msg_resp: 2 callbacks suppressed
[ 8811.851497] intel-sdw intel-sdw.0: Msg Ack not received
[ 8811.851498] intel-sdw intel-sdw.0: Msg Ack not received
[ 8811.851499] intel-sdw intel-sdw.0: Msg Ack not
From: Pierre-Louis Bossart
The existing code reports a NAK only when ACK=0
This is not aligned with the SoundWire 1.x specifications.
Table 32 in the SoundWire 1.2 specification shows that a Device shall
not set NAK=1 if ACK=1. But Table 33 shows the Combined Response
may very well be
The current error log does not provide details on the type of
transfers and which address/count was requested. All this information
can help locate in which parts of the configuration process an error
occurred.
Co-developed-by: Pierre-Louis Bossart
Signed-off-by: Pierre-Louis Bossart
From: Pierre-Louis Bossart
The existing debug log only mentions a state change, without providing
any details. For integration and stress-tests, it's helpful to see in
the dmesg log the reason for the state change.
The value is intended for power users and isn't converted as
human-readable
From: Pierre-Louis Bossart
We mix decimal and hexadecimal values, this leads to confusions in
dmesg logs and bug reports. Let's add a 0x prefix for all hexadecimal
values and a format when more than 4 bits are used.
Signed-off-by: Pierre-Louis Bossart
Reviewed-by: Rander Wang
Signed-off-by:
The existing code reports a NAK only when ACK=0
This is not aligned with the SoundWire 1.x specifications.
Table 32 in the SoundWire 1.2 specification shows that a Device shall
not set NAK=1 if ACK=1. But Table 33 shows the Combined Response
may very well be NAK=1/ACK=1, e.g. if another Device
This patchset impelements support of SOCK_SEQPACKET for virtio
transport.
As SOCK_SEQPACKET guarantees to save record boundaries, so to
do it, new packet operation was added: it marks start of record (with
record length in header), such packet doesn't carry any data. To send
On Wed 13 Jan 13:42 CST 2021, AngeloGioacchino Del Regno wrote:
> In commit 208921bae696 ("arm64: dts: qcom: pmi8998: Add nodes for
> LAB and IBB regulators") bindings for the lab/ibb regulators were
> added to the pmi8998 dt, but the original committer has never
> specified what the interrupts
Hi all,
After merging the amdgpu tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c: In function
'vangogh_get_smu_metrics_data':
drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c:300:10: error:
On Wed 13 Jan 13:42 CST 2021, AngeloGioacchino Del Regno wrote:
> Short-Circuit Protection (SCP) and Over-Current Protection (OCP) are
> now implemented in the driver: document the interrupts.
> This also fixes wrong documentation about the SCP interrupt for LAB.
>
Reviewed-by: Bjorn Andersson
On Thu, Jan 14, 2021 at 8:15 PM Jiri Kosina wrote:
>
> On Thu, 24 Dec 2020, Nicolas Boichat wrote:
>
> > This forces reading the base folded status anytime the device is
> > probed.
>
> Could you please provide a little bit more verbose changelog (namely what
> is the actual problem this patch is
On Wed 13 Jan 13:42 CST 2021, AngeloGioacchino Del Regno wrote:
> Short-Circuit Protection (SCP) and Over-Current Protection (OCP) are
> very important for regulators like LAB and IBB, which are designed to
> provide from very small to relatively big amounts of current to the
> device (normally,
On Thu, 2021-01-14 at 13:27 -0600, Rob Herring wrote:
> On Mon, Jan 11, 2021 at 07:18:47PM +0800, Yong Wu wrote:
> > "dev->dma_range_map" contains the devices' dma_ranges information,
> > This patch moves dma_range_map before of_iommu_configure. The iommu
> > driver may need to know the
On 1/13/21 8:58 PM, Suzuki K Poulose wrote:
> Hi Anshuman,
>
> The driver looks overall good to me. Please find some minor comments below
>
> On 1/13/21 4:18 AM, Anshuman Khandual wrote:
>> Trace Buffer Extension (TRBE) implements a trace buffer per CPU which is
>> accessible via the system
On 14.01.21 20:40, Josh Poimboeuf wrote:
It's kernel policy to not have (unannotated) indirect jumps because of
Spectre v2. This one's probably harmless, but better safe than sorry.
Convert it to a retpoline.
Cc: Boris Ostrovsky
Cc: Juergen Gross
Signed-off-by: Josh Poimboeuf
---
On Fri, Jan 15, 2021 at 5:51 AM Sedat Dilek wrote:
>
> On Thu, Jan 14, 2021 at 8:40 PM Josh Poimboeuf wrote:
> >
> > Add support for proper vmlinux.o validation, which will be needed for
> > Sami's upcoming x86 LTO set. (And vmlinux validation is the future for
> > objtool anyway, for other
On 14.01.21 20:40, Josh Poimboeuf wrote:
The Xen hypercall page is filled with zeros, causing objtool to fall
through all the empty hypercall functions until it reaches a real
function, resulting in a stack state mismatch.
The build-time contents of the hypercall page don't matter, since it
> On Jan 11, 2021, at 18:52, Liu, Jing2 wrote:
>
> On 1/8/2021 2:40 AM, Bae, Chang Seok wrote:
>>> On Jan 7, 2021, at 17:41, Liu, Jing2 wrote:
>>>
>>> static void kvm_save_current_fpu(struct fpu *fpu) {
>>> + struct fpu *src_fpu = >thread.fpu;
>>> +
>>> /*
>>> * If the target FPU
Hi Linus,
As mentioned in the previous pull, Ben has requested if we can include
Ampere modesetting support under fixes, it's for new GPUs and
shouldn't affect existing hardware. It's a bit bigger than just adding
a PCI ID, and I'm fine if you think we should hold it off until later.
Dave.
On Wed 13 Jan 13:42 CST 2021, AngeloGioacchino Del Regno wrote:
> Document properties to configure soft start and discharge resistor
> for LAB and IBB respectively.
>
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
>
On Wed 13 Jan 13:42 CST 2021, AngeloGioacchino Del Regno wrote:
> Soft start is required to avoid inrush current during LAB ramp-up and
> IBB ramp-down, protecting connected hardware to which we supply voltage.
>
> Since soft start is configurable on both LAB and IBB regulators, it
> was
1 - 100 of 1491 matches
Mail list logo
