On Thu, May 02, 2019 at 10:59:38PM -0500, Frederick Lawler wrote:
> Cleanup dmesg logs.
To specific, I think you did this:
- Drop the kzalloc() failure message because those failures are logged
elsewhere.
- Convert other printk(KERN_DEBUG) to pci_info() or dev_err() as
appropriate be
Use udf as the guard instruction for the restartable sequence abort
handler.
Previously, the chosen signature was not a valid instruction, based
on the assumption that it could always sit in a literal pool. However,
there are compilation environments in which literal pools are not
available, for i
On Thu, May 2, 2019 at 4:19 PM Jayachandran Chandrasekharan Nair
wrote:
>>
> I don't really see the point your are making about hardware. If you
> look at the test case, you have about 64 cores doing CAS to the same
> location. At any point one of them will succeed and the other 63 will
> fail - a
On Fri, May 03, 2019 at 09:07:30PM +0200, Petr Štetiar wrote:
> Dan Carpenter [2019-05-03 13:34:56]:
>
> Hi,
>
> > On Fri, May 03, 2019 at 09:56:05AM +0200, Petr Štetiar wrote:
> > > There was NVMEM support added to of_get_mac_address, so it could now
> > > return NULL and ERR_PTR encoded error
This patch could also be routed via akpm, adding him.
On Thu, 02 May 2019, Deepa Dinamani wrote:
For all the syscalls that receive a sigmask from the userland,
the user sigmask is to be in effect through the syscall execution.
At the end of syscall, sigmask of the current process is restored
to
On Thu, May 02, 2019 at 10:59:39PM -0500, Frederick Lawler wrote:
> Prefix dmesg logs with PCIe service name.
The important thing about this patch is not so much that it adds a
prefix (actually, it basically *moves* the prefix from the driver name
("dpc") to being part of the messages ("DPC:")), b
Hello Kees, all,
Sorry for the delayed response, I haven't had time to see this until now.
On 25/04/2019 17:51, Kees Cook wrote:
> On Wed, Apr 24, 2019 at 10:42 PM Ingo Molnar wrote:
>> Just to make clear, is the change from the old behavior, in essence:
>>
>>
>>CPU: | lacks NX
From: Ross Zwisler
commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
Currently in sst_dsp_new() if we get an error return from sst_dma_new()
we just print an error message and then still complete the function
successfully. This means that we are trying to run without sst->dma
properly s
> -Original Message-
> From: Pierre-Louis Bossart [mailto:pierre-louis.boss...@linux.intel.com]
> Sent: Wednesday, May 1, 2019 5:53 AM
> To: alsa-de...@alsa-project.org
> Cc: linux-kernel@vger.kernel.org; ti...@suse.de; broo...@kernel.org;
> vk...@kernel.org; gre...@linuxfoundation.org;
On Thu, May 02, 2019 at 10:59:40PM -0500, Frederick Lawler wrote:
> Prefix dmesg logs with PCIe service name.
... to make it consistent with other PCIe services.
It's interesting that there are three uses here:
pci_dbg(port, "PME interrupt generated for non-existent device ...")
pci_dbg(port
Hi Mark,
On Fri, May 03, 2019 at 01:27:31PM +0900, Mark Brown wrote:
> On Thu, May 02, 2019 at 09:13:58AM +, S.j. Wang wrote:
>
> > I am checking, but I don't know why this patch failed in your side. I
> > Tried to apply this patch on for-5.1, for 5.2, for-linus and for-next,
> > all are
On 5/3/19 5:54 AM, kbuild test robot wrote:
> Hi Ming,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: ea9866793d1e925b4d320eaea409263b2a568f38
> commit: 6dc4f100c175dd0511ae8674786e7c9006cdfbfa block:
On Thu, May 02, 2019 at 10:59:43PM -0500, Frederick Lawler wrote:
> Prefix dmesg logs with PCIe service name.
>
> Signed-off-by: Frederick Lawler
> ---
> drivers/pci/hotplug/pciehp.h | 18 +-
> drivers/pci/hotplug/pciehp_core.c | 7 +--
> drivers/pci/hotplug/pciehp_ctrl
From: Randy Dunlap [mailto:rdun...@infradead.org]
>>ERROR: "paddr_to_nid" [drivers/block/brd.ko] undefined!
>>ERROR: "paddr_to_nid" [crypto/ccm.ko] undefined!
>>
>
> ---
> Exporting paddr_to_nid() in arch/ia64/mm/numa.c fixes all of these build
> errors.
> Is there a problem with doing t
>> Exporting paddr_to_nid() in arch/ia64/mm/numa.c fixes all of these build
>> errors.
>> Is there a problem with doing that?
>
> I don't see a problem with exporting it.
But I also don't see these build errors. I'm using the same HEAD commit. I
think the
same .config (derived from arch/ia64/co
On 23/04/2019 07:59, Zhang Rui wrote:
> Hi, Daniel,
>
> thanks for clarifying.
> It is true that we need to make thermal framework ready as early as
> possible. And a static table works for me as long as vmlinux.lds.h is
> the proper place.
>
> Arnd,
> are you okay with this patch? if yes, I supp
Since recent high resolution scrolling changes the A4Tech driver must
check for the "REL_WHEEL_HI_RES" usage code.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=203369
Fixes: 2dc702c991e3774af9d7ce410eef410ca9e2357e ("HID: input: use the
Resolution Multiplier for high-resolution scrolling")
S
Hi Marc,
On 30/04/2019 17:27, Marc Zyngier wrote:
> On 15/04/2019 13:16, Daniel Lezcano wrote:
>> On 08/04/2019 17:49, Marc Zyngier wrote:
>>> Instead of always going via arch_counter_get_cntvct_stable to
>>> access the counter workaround, let's have arch_timer_read_counter
>>> to point to the r
Hi Valentin,
On 30/04/2019 17:39, Valentin Schneider wrote:
> Hi,
>
> On 30/04/2019 16:27, Marc Zyngier wrote:
> [...]
@@ -372,6 +392,7 @@ static u32 notrace sun50i_a64_read_cntv_tval_el0(void)
DEFINE_PER_CPU(const struct arch_timer_erratum_workaround *,
timer_unstable_counter_
Hi,
On Fri, May 03, 2019 at 12:00:39PM -0500, Andrey Smirnov wrote:
> This small series adds a driver for UCS1002 Programmable USB Port
> Power Controller with Charger Emulation. See [page] for product page
> and [datasheet] for device dataseet. Hopefully each individual patch
> is self explanator
On Thu, May 02, 2019 at 10:59:44PM -0500, Frederick Lawler wrote:
> dbg() and ctrl_dbg() requires pciehp_debug module parameter to be set
> for debug log purposes. There are niche situations in pciehp_hpc.c where
> pciehp_debug is used: dbg_ctrl(), and pci_bus_check_dev().
>
> Enabling CONFIG_DYNA
On Fri, May 03, 2019 at 02:10:19PM -0400, Joel Savitz wrote:
> In the mainline kernel, there is no quick mechanism to get the virtual
> memory size of the current process from userspace.
>
> Despite the current state of affairs, this information is available to the
> user through several means, on
On 5/3/19 1:25 PM, Luck, Tony wrote:
>>> Exporting paddr_to_nid() in arch/ia64/mm/numa.c fixes all of these build
>>> errors.
>>> Is there a problem with doing that?
>>
>> I don't see a problem with exporting it.
>
> But I also don't see these build errors. I'm using the same HEAD commit. I
> t
Quoting Roger Lu (2019-05-01 23:19:31)
> On Tue, 2019-04-30 at 13:31 -0700, Stephen Boyd wrote:
> > Quoting Roger Lu (2019-04-30 04:20:10)
> > > diff --git a/Documentation/devicetree/bindings/power/mtk-svs.txt
> > > b/Documentation/devicetree/bindings/power/mtk-svs.txt
> > > new file mode 100644
>
On Fri, May 03, 2019 at 02:10:20PM -0400, Joel Savitz wrote:
> When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> copy the value of TASK_SIZE to the userspace address in arg2.
>
> It is important that we account for the case of the userspace task
> running in 32-bit compat mode
On 02/05/2019 20:32, Matthias Kaehlcke wrote:
> The CPU load values passed to the thermal_power_cpu_get_power
> tracepoint are zero for all CPUs, unless, unless the
> thermal_power_cpu_limit tracepoint is enabled too:
>
> irq/41-rockchip-98[000] 290.972410: thermal_power_cpu_get_power
The AP architecture does not preclude assignment of AP resources that are
not yet in the AP configuration (i.e., not available or not online).
Let's go ahead and implement this facet of the AP architecture for linux
guests.
The current implementation does not allow assignment of AP resources to
an
There is nothing preventing a root user from inadvertently unbinding an
AP queue device that is in use by a guest from the vfio_ap device driver
and binding it to a zcrypt driver. This can result in a queue being
accessible from both the host and a guest.
This patch introduces safeguards that prev
This patch updates the vfio-ap documentation to include the information
below.
Changes made to the mdev matrix assignment interfaces:
* We now allow assignment of APQNs that are not bound to the vfio-ap
device driver
* We now use assignment interfaces to hot plug AP resources into a
a runnin
This patch series extends the crypto adapter pass-through support to
provide safeguards against inadvertent sharing of AP resources between
guests and/or the host, and to implement more of the s390 AP
architecture related to provisioning and dynamic configuration of
AP resources.
Change log v2->v
This patch introduces a shadow of the CRYCB being used by a guest. This
will enable to more effectively manage dynamic changes to the AP
resources installed on the host that may be assigned to an mdev device
and being used by a guest. For example:
* AP adapter cards can be dynamically added to and
Let's allow AP resources to be assigned to or unassigned from an AP matrix
mdev device while it is in use by a guest. If a guest is using the mdev
device while assignment is taking place, the guest will be granted access
to the resource as long as the guest will not be given access to an AP
queue d
Refactors the AP queue reset function to wait until the queue is empty
after the PQAP(ZAPQ) instruction is executed to zero out the queue as
required by the AP architecture.
Signed-off-by: Tony Krowiak
---
drivers/s390/crypto/vfio_ap_ops.c | 35 ---
1 file changed
Introduces a sysfs interface on the matrix mdev device to display the
contents of the shadow of the guest's CRYCB
Signed-off-by: Tony Krowiak
---
drivers/s390/crypto/vfio_ap_ops.c | 59 +++
1 file changed, 59 insertions(+)
diff --git a/drivers/s390/crypto/vfi
On 5/2/19 9:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.12 release.
There are 101 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made b
On 5/2/19 9:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.39 release.
There are 72 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made b
On 5/2/19 9:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.116 release.
There are 49 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 5/2/19 9:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.173 release.
There are 32 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made b
At boot time, my rk3288-veyron devices yell with 8 lines that look
like this:
[0.00] rockchip_mmc_get_phase: invalid clk rate
This is because the clock framework at clk_register() time tries to
get the phase but we don't have a parent yet.
While the errors appear to be harmless they are
On Fri, May 03, 2019 at 03:48:26PM +0200, Ludovic Barre wrote:
> From: Ludovic Barre
>
> This patch allows to define the max prescaler by compatible.
> To set a large range of timeout, the prescaler should be set
> dynamically (from the timeout request) to improve the resolution
> in order to hav
On Thu 2019-05-02 17:21:19, Greg Kroah-Hartman wrote:
> [ Upstream commit 41f00e6e9e55546390031996b773e7f3c1d95928 ]
>
> of_match_device in usb251xb_probe can fail and returns a NULL pointer.
> The patch avoids a potential NULL pointer dereference in this scenario.
>
> Signed-off-by: Aditya Pakki
Linus,
The following changes since commit 7a223e06b1a411cef6c4cd7a9b9a33c8d225b10e:
KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in
tracing (2019-04-16 15:38:08 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linu
On Fri, 2019-05-03 at 15:22 -0400, Mathieu Desnoyers wrote:
> - On May 3, 2019, at 2:53 PM, shuah sh...@kernel.org wrote:
> > ERROR: need consistent spacing around '%' (ctx:WxV)
> > #227: FILE: tools/testing/selftests/rseq/rseq-x86.h:104:
> > + RSEQ_ASM_CMP_CPU_ID(cpu_id, RSEQ_CPU_ID_
Am Freitag, 3. Mai 2019, 23:22:08 CEST schrieb Douglas Anderson:
> At boot time, my rk3288-veyron devices yell with 8 lines that look
> like this:
> [0.00] rockchip_mmc_get_phase: invalid clk rate
>
> This is because the clock framework at clk_register() time tries to
> get the phase but
On Fri, May 3, 2019 at 12:24 PM Steven Rostedt wrote:
>
> The problem with this approach is that it would require doing the same
> for x86_64, as the int3 C code is the same for both. And that may be a
> bit more difficult on the x86_64 side because it's all done with a
> simple flag in the idtent
On Fri, May 03, 2019 at 02:08:31PM -0700, Yury Norov wrote:
> On Fri, May 03, 2019 at 02:10:20PM -0400, Joel Savitz wrote:
> > When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> > copy the value of TASK_SIZE to the userspace address in arg2.
> >
> > It is important that we acco
On Fri, May 03, 2019 at 01:49:12PM -0700, Yury Norov wrote:
> On Fri, May 03, 2019 at 02:10:19PM -0400, Joel Savitz wrote:
> > In the mainline kernel, there is no quick mechanism to get the virtual
> > memory size of the current process from userspace.
> >
> > Despite the current state of affairs,
Jerome Brunet writes:
> The patchset is bunch of clean-up found while debugging meson mmc.
>
> * The first 2 patches address the libretech-cc which actually uses 1.8v
> eMMC modules.
> * Patch 3 is a pin bias fixup depending on mmc pins.
> * Patch 4 lower the mmc max frequencies on gx chips. It
Quoting Douglas Anderson (2019-05-03 14:22:08)
> At boot time, my rk3288-veyron devices yell with 8 lines that look
> like this:
> [0.00] rockchip_mmc_get_phase: invalid clk rate
>
> This is because the clock framework at clk_register() time tries to
> get the phase but we don't have a p
This patchset solves readability issues in AD7150 code, such as clarify
register and mask definition, fashion improvement of mask uses, reduce
tedious operation and useless comments.
Melissa Wen (4):
staging: iio: ad7150: organize registers definition
staging: iio: ad7150: use FIELD_GET and GE
Use the suffix REG to make the register addresses clear
and indentation to highlight field names.
Signed-off-by: Melissa Wen
---
drivers/staging/iio/cdc/ad7150.c | 75
1 file changed, 37 insertions(+), 38 deletions(-)
diff --git a/drivers/staging/iio/cdc/ad7150.
Use the bitfield macro FIELD_GET, and GENMASK to do the shift and mask in
one go. This makes the code more readable than explicit masking followed
by a shift.
Signed-off-by: Melissa Wen
---
drivers/staging/iio/cdc/ad7150.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/
On Fri, May 03, 2019 at 02:08:31PM -0700, Yury Norov wrote:
> On Fri, May 03, 2019 at 02:10:20PM -0400, Joel Savitz wrote:
> > When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> > copy the value of TASK_SIZE to the userspace address in arg2.
> >
> > It is important that we acco
Since i2c_smbus_write_byte_data returns no-positive value, this commit
making the treatment of its return value less verbose.
Signed-off-by: Melissa Wen
---
drivers/staging/iio/cdc/ad7150.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/iio/cdc/ad7
General cleaning of comments to remove useless information or improve
description.
Signed-off-by: Melissa Wen
---
drivers/staging/iio/cdc/ad7150.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/iio/cdc/ad7150.c b/drivers/staging/iio/cdc/ad7150.c
i
From: Prakhar Srivastava
This change adds the buffer passed in to the xattr used for
template entries.
Signed-off-by: Prakhar Srivastava
---
security/integrity/ima/ima_main.c | 37 ---
security/integrity/ima/ima_template_lib.c | 3 +-
security/integrity/integrity.h
From: Prakhar Srivastava
prepend the kernel file name to the cmdline args
to avoid conflicrts in case of multiple kexec.
Pass the new generated buffer to ima for measurmenet.
Signed-off-by: Prakhar Srivastava
---
kernel/kexec_core.c | 57 +
kernel/ke
From: Prakhar Srivastava
For Kexec scenario(kexec_file_load) cmdline args are passed to the
next kerenel. These cmldine args used to load the next kernel can
have undesired/unwanted configs. To guard against any unwanted cmdline
args being passed to the next kernel. The current kernel should mea
From: Prakhar Srivastava
add a LAM hook for kexec_cmldine args to be made available to
other LSMs.
Signed-off-by: Prakhar Srivastava
---
include/linux/lsm_hooks.h | 3 +++
include/linux/security.h | 3 +++
kernel/kexec_internal.h | 4 +++-
security/security.c | 6 ++
4 files chang
From: Prakhar Srivastava
This change adds a new ima policy func buffer_check, and ima hook to
measure the buffer hash into ima log.
Signed-off-by: Prakhar Srivastava
---
Documentation/ABI/testing/ima_policy | 1 +
include/linux/ima.h | 5 ++
security/integrity/ima/ima.h
From: Prakhar Srivastava
Per suggestions from the community, removed the LSM hook.
and renamed the buffer_check func and policy to kexec_cmdline
[suggested by: Mimi Zohar]
Signed-off-by: Prakhar Srivastava
---
Documentation/ABI/testing/ima_policy | 2 +-
include/linux/ima.h |
Hi Mike,
On Fri, 3 May 2019 13:34:49 -0400 Mike Marshall wrote:
>
> I noticed the conflict too when I added Al's patch series to the orangefs
> tree we have on next. I understood Linus to say he'd fix the conflict the
> way you did during the merge window. I guess that means you'll have to
> keep
This reverts commit 356ff8a9a78fb35d6482584d260c3754dcbdf669.
Signed-off-by: Andrea Arcangeli
---
include/linux/gfp.h | 12
mm/huge_memory.c| 27 ++-
mm/mempolicy.c | 32 +++-
mm/shmem.c | 2 +-
4 files changed,
This reverts commit 2f0799a0ffc033bf3cc82d5032acc3ec633464c2.
commit 2f0799a0ffc033bf3cc82d5032acc3ec633464c2 was rightfully applied
to avoid the risk of a severe regression that was reported by the
kernel test robot at the end of the merge window. Now we understood
the regression was a false posi
Hello,
The fixes for what was originally reported as "pathological THP
behavior" we rightfully reverted to be sure not to introduced
regressions at end of a merge window after a severe regression report
from the kernel bot. We can safely re-apply them now that we had time
to analyze the problem.
Support receiving IPMB requests on a Satellite MC from the BMC.
Once a response is ready, this driver will send back a response
to the BMC via the IPMB channel.
Signed-off-by: Asmaa Mnebhi
---
Documentation/IPMB.txt | 103 ++
drivers/char/ipmi/Kconfig| 8 +
drivers/ch
Hi Vadim,
I apologize I forgot to address your previous comment concerning
the ACPI table. I have added the ACPI device id as well as documented
it for whomever wants to use either the ACPI table or device tree.
I did not need that for my testing due to our internal build tools/
code structure.
Bu
On Fri, 3 May 2019 14:46:11 -0700
Linus Torvalds wrote:
> On Fri, May 3, 2019 at 12:24 PM Steven Rostedt wrote:
> >
> > The problem with this approach is that it would require doing the same
> > for x86_64, as the int3 C code is the same for both. And that may be a
> > bit more difficult on the
The original patch was merged through the tip tree. Adding tglx just in case.
I will post the revised patch to everyone on this thread.
> >For all the syscalls that receive a sigmask from the userland,
> >the user sigmask is to be in effect through the syscall execution.
> >At the end of syscall,
> On May 3, 2019, at 2:46 PM, Linus Torvalds
> wrote:
>
>> On Fri, May 3, 2019 at 12:24 PM Steven Rostedt wrote:
>>
>> The problem with this approach is that it would require doing the same
>> for x86_64, as the int3 C code is the same for both. And that may be a
>> bit more difficult on th
On 5/3/19 1:22 PM, Mathieu Desnoyers wrote:
- On May 3, 2019, at 2:53 PM, shuah sh...@kernel.org wrote:
On 5/3/19 12:36 PM, Mathieu Desnoyers wrote:
- On Apr 29, 2019, at 11:27 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
Those rseq selftests updates are hereby submitt
From: Ben Zhang
This patch allows headphone plug detect and mic present
detect to be enabled at the same time. This patch implements
an irq_chip with irq_domain directly instead of using
regmap-irq, so that interrupt source line polarities can
be flipped to support irq sharing.
This patch does n
The rt5677 driver writes to the IRQ control register within the IRQ
handler in order to flip the polarity of the interrupts that have been
signalled. If an interrupt fires in the interval between the
regmap_read and the regmap_write, it will not trigger a new call to
rt5677_irq.
Add a bounded loo
The rt5677 driver uses ACPI-style property names to read from the
device API. However, these do not match the property names in _DSD
used on the Chromebook Pixel 2015, which are closer to the Device Tree
style. Unify the two functions for reading from the device API so that
they try ACPI-style nam
Headphone/mic jack detection doesn't work on the Chromebook Pixel 2015.
This patch changes the irq implementation to support polarity flipping
and fixes the configuration code so that correct GPIO pins are read
from ACPI.
With this series, plugging and unplugging the headphone jack switches
betwe
On Fri, May 3, 2019 at 3:49 PM Steven Rostedt wrote:
>
> You are saying that we have a do_int3() for user space int3, and
> do_kernel_int3() for kernel space. That would need to be done in asm
> for both, because having x86_64 call do_int3() for kernel and
> user would be interesting.
The clean/s
Now that the regulators are tied to the GPIO bank, we can remove the
unneeded regulator-always-on in reg_aldo2
Signed-off-by: Pablo Greco
---
arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts
b/
On Fri, May 3, 2019 at 2:12 PM Joel Savitz wrote:
> When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> copy the value of TASK_SIZE to the userspace address in arg2.
A commit message shouldn't just describe what you're doing, but also
why you're doing it. Is this intended for p
On Fri, May 3, 2019 at 3:55 PM Andy Lutomirski wrote:
>
> But I think this will end up worse than the version where the entry code
> fixes it up. This is because, if the C code moves pt_regs, then we need some
> way to pass the new pointer back to the asm.
What? I already posted that code. Let
MDSS and its friends complain about the DTS is using legacy clock names,
update these to silence the warnings.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/arch/arm64/boot
> On May 3, 2019, at 4:16 PM, Linus Torvalds
> wrote:
>
>> On Fri, May 3, 2019 at 3:55 PM Andy Lutomirski wrote:
>>
>> But I think this will end up worse than the version where the entry code
>> fixes it up. This is because, if the C code moves pt_regs, then we need
>> some way to pass t
If I run the following on rk3288-veyron-minnie (a 2GB machine)
cd /sys/bus/platform/drivers/dwmmc_rockchip
for i in $(seq 1 3000); do
echo "" $i
echo ff0f.dwmmc > unbind
sleep .5
echo ff0f.dwmmc > bind
while true; do
if [ -e /dev/mmcblk
On Thu, May 2, 2019 at 4:48 AM Greg Kroah-Hartman
wrote:
>
> On Tue, Apr 30, 2019 at 11:37:48AM +0200, Rafael J. Wysocki wrote:
> > On Tue, Apr 30, 2019 at 11:00 AM Mika Westerberg
> > wrote:
> > >
> > > +Rafael, Furquan and linux-acpi
> > >
> > > (The original thread is here
> > > https://lore.
As some point hs200 was failing on rk3288-veyron-minnie. See commit
984926781122 ("ARM: dts: rockchip: temporarily remove emmc hs200 speed
from rk3288 minnie"). Although I didn't track down exactly when it
started working, it seems to work OK now, so let's turn it back on.
To test this, I booted
When I try to boot rk3288-veyron-mickey I totally fail to make the
eMMC work. Specifically my logs (on Chrome OS 4.19):
mmc_host mmc1: card is non-removable.
mmc_host mmc1: Bus speed (slot 0) = 40Hz (slot req 40Hz, actual
40HZ div = 0)
mmc_host mmc1: Bus speed (slot 0) = 50
The rk3288-veyron-mickey device tree overrides the default "i2s" clock
settings to add the clock for "i2s_clk_out".
That clock is only present in the bindings downstream Chrome OS 3.14
tree. Upstream the i2s port bindings doesn't specify that as a
possible clock.
Let's remove it.
NOTE: for othe
Peter Zijlstra's on May 4, 2019 2:04 am:
> On Fri, May 03, 2019 at 08:34:57PM +0800, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>> sched/core
>> head: 65874bd36e6ae3028539e989bfb5c28ad457368e
>> commit: c2cb30bfceceba8a2a0d5713230a250dd6140e22
On Fri, May 03, 2019 at 04:35:26PM -0700, Douglas Anderson wrote:
> If I run the following on rk3288-veyron-minnie (a 2GB machine)
>
> cd /sys/bus/platform/drivers/dwmmc_rockchip
> for i in $(seq 1 3000); do
> echo "" $i
> echo ff0f.dwmmc > unbind
> slee
On Fri, May 03, 2019 at 10:47:37AM -0700, tip-bot for Nicholas Piggin wrote:
> Commit-ID: 9219565aa89033a9cfdae788c1940473a1253d6c
> Gitweb:
> https://git.kernel.org/tip/9219565aa89033a9cfdae788c1940473a1253d6c
> Author: Nicholas Piggin
> AuthorDate: Thu, 11 Apr 2019 13:34:47 +1000
> Com
On Fri, May 03, 2019 at 05:28:46PM +0100, Catalin Marinas wrote:
> Thanks Jason and Leon for the information.
>
> On Thu, May 02, 2019 at 03:44:42PM -0300, Jason Gunthorpe wrote:
> > On Tue, Apr 30, 2019 at 12:16:25PM +0100, Catalin Marinas wrote:
> > > > Interesting, the followup question is why
On Fri, May 03, 2019 at 04:48:14PM -0700, Douglas Anderson wrote:
> The rk3288-veyron-mickey device tree overrides the default "i2s" clock
> settings to add the clock for "i2s_clk_out".
>
> That clock is only present in the bindings downstream Chrome OS 3.14
> tree. Upstream the i2s port bindings
On Thu, May 02, 2019 at 04:01:16PM +0200, Ludovic Desroches wrote:
> On Tue, Apr 30, 2019 at 04:03:32AM +0530, Raag Jadav wrote:
> > External E-Mail
> >
> >
> > On Mon, Apr 29, 2019 at 11:00:05AM +0200, Ludovic Desroches wrote:
> > > Hello Raag,
> > >
> > > On Tue, Apr 23, 2019 at 01:06:48PM +05
The pull request you sent on Fri, 3 May 2019 15:46:14 -0600:
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/aa1be08f52585fe36ecfaf5bddfdc784eb4c94cf
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg
Failing to toggle a GDSC as the driver core is attaching the
power-domain to a device will cause a silent probe deferral. Provide an
explicit warning to the developer, in order to reduce the amount of time
it take to debug this.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gdsc.c | 4 +++-
On Fri, May 3, 2019 at 4:35 PM Douglas Anderson wrote:
>
> If I run the following on rk3288-veyron-minnie (a 2GB machine)
>
> cd /sys/bus/platform/drivers/dwmmc_rockchip
> for i in $(seq 1 3000); do
> echo "" $i
> echo ff0f.dwmmc > unbind
> sleep .5
>
On Fri, May 03, 2019 at 10:47:37AM -0700, tip-bot for Nicholas Piggin wrote:
> Commit-ID: 9219565aa89033a9cfdae788c1940473a1253d6c
> Gitweb:
> https://git.kernel.org/tip/9219565aa89033a9cfdae788c1940473a1253d6c
> Author: Nicholas Piggin
> AuthorDate: Thu, 11 Apr 2019 13:34:47 +1000
> Com
The master-count is only defined for a controller or a Slave in the
MIPI DisCo for SoundWire document.
rename all fields with 'freq' as 'clk_freq' to follow the MIPI
specification and avoid confusion between bus clock and audio clocks.
fix support for clock_stop_mode0 and 1. The existing code use
sdw_slave_read_dp0 was so far a static function, which prevented codec
drivers from using it. Expose as non-static function and add symbol
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/mipi_disco.c | 7 ---
include/linux/soundwire/sdw.h | 3 +++
2 files changed, 7 insertions(+),
The SoundWire and DisCo specifications do not define Master data ports
or related properties. Data ports are only defined for Slave devices,
so remove the unused member in properties.
Credits: this patch is based on an earlier internal contribution by
Vinod Koul, Sanyog Kale, Shreyas Nc and Hardik
sdw_slave_read_dpn was so far a static function, which prevented
codec drivers from using it. Expose as non-static function and add symbol
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/mipi_disco.c | 7 ---
include/linux/soundwire/sdw.h | 3 +++
2 files changed, 7 insertions(+),
401 - 500 of 542 matches
Mail list logo
