Hello Linus,
Here are 2 fixes for 5.0 (or -rc8 if you end up delaying the release).
Regards,
Boris
The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)
are available in the Git repository at:
The Rockchip RK3288 SoC (v2.00a) and RK3328/RK3399 SoCs (v2.11a) have
also been identified as needing this workaround with a single iteration.
Fixes: be41fc55f1aa ("drm: bridge: dw-hdmi: Handle overflow workaround based on
device version")
Signed-off-by: Jonas Karlman
---
On 19/02/19 18:19, Sebastian Andrzej Siewior wrote:
> On 2019-02-14 14:37:14 [+0100], Juri Lelli wrote:
> > Hi,
> Hi,
>
> > Now, I'm sending this and an RFC, as I'm wondering if the first behavior
> > is actually what we want, and it is not odd at all for reasons that are
> > not evident to me at
> From: Anson Huang
> Sent: Wednesday, February 20, 2019 2:54 PM
>
> NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as system
> controller, the system controller is in charge of system power, clock and
> thermal sensors etc. management, Linux kernel has to communicate with
> system
Add devicetree for Milbeaut M10V SoC and M10V Evaluation board.
Signed-off-by: Sugaya Taichi
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/milbeaut-m10v-evb.dts | 32 +++
arch/arm/boot/dts/milbeaut-m10v.dtsi| 95 +
3 files
This patch adds the minimal defconfig for the Milbeaut M10V.
Signed-off-by: Sugaya Taichi
---
arch/arm/configs/milbeaut_m10v_defconfig | 175 +++
arch/arm/configs/multi_v7_defconfig | 2 +
2 files changed, 177 insertions(+)
create mode 100644
Add DT bindings document for Milbeaut serial driver.
Signed-off-by: Sugaya Taichi
---
.../devicetree/bindings/serial/milbeaut-uart.txt| 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/serial/milbeaut-uart.txt
diff --git
Add timer driver for Milbeaut SoCs series.
The timer has two 32-bit width down counters, one of which is configured
as a clockevent device and the other is configured as a clock source.
Signed-off-by: Sugaya Taichi
Acked-by: Daniel Lezcano
---
drivers/clocksource/Kconfig | 9 ++
Hi all,
Changes since 20190219:
The asm-generic tree lost its build failure.
The v4l-dvb tree lost its build failure.
The net-next tree gained a conflict against the bpf tree.
The kvm tree still had its build failure so I used a supplied patch.
The akpm-current tree gained a build failure
Add DT bindings document for Milbeaut M10V timer.
Signed-off-by: Sugaya Taichi
Reviewed-by: Rob Herring
---
.../bindings/timer/socionext,milbeaut-timer.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
This adds the basic M10V SoC support under arch/arm.
Since all cores are activated in the custom bootloader before booting
linux, it is necessary to wait for the secondary-cores using cpu-enable-
method and special sram.
Signed-off-by: Sugaya Taichi
---
arch/arm/Kconfig | 2 +
The Milbeaut M10V SoC needs a part of sram for smp, so this adds the
M10V sram compatible and binding.
Signed-off-by: Sugaya Taichi
Reviewed-by: Rob Herring
---
.../devicetree/bindings/sram/milbeaut-smp-sram.txt | 24 ++
1 file changed, 24 insertions(+)
create mode 100644
This adds a compatible string "socionext,milbeaut-m10v-smp"
for Milbeaut M10V to the 32 bit ARM CPU device tree binding.
Signed-off-by: Sugaya Taichi
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
This adds a DT binding documentation for the M10V and its evaluation
board.
Signed-off-by: Sugaya Taichi
---
.../bindings/arm/socionext/milbeaut.yaml | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
Hi,
Here is the series of patches the initial support for SC2000(M10V) of
Milbeaut SoCs. "M10V" is the internal name of SC2000, so commonly used in
source code.
SC2000 is a SoC of the Milbeaut series. equipped with a DSP optimized for
computer vision. It also features advanced functionalities
On Tue, Feb 19, 2019 at 03:19:18PM +, Colin King wrote:
> From: Colin Ian King
>
> The checks of a negative nval indicating an error an never be true
> as nval is currently a size_t which is of course unsigned and hence
> never less than zero. Fix this by making nval an int.
>
> Detected by
On Mon, Feb 18, 2019 at 9:48 AM Dave Young wrote:
>
> On 02/15/19 at 11:24am, Borislav Petkov wrote:
> > On Tue, Feb 12, 2019 at 04:48:16AM +0800, Dave Young wrote:
> > > Even we make it automatic in kernel, but we have to have some default
> > > value for swiotlb in case crashkernel can not find
On 2019/2/20 15:25, Chao Yu wrote:
> On 2019/2/20 15:08, Jaegeuk Kim wrote:
>> On 02/18, Chao Yu wrote:
>>> On 2019/2/16 12:55, Jaegeuk Kim wrote:
On 02/13, Chao Yu wrote:
> On 2019/2/12 10:33, Jaegeuk Kim wrote:
>> If we met this once, let fsck.f2fs clear this only.
>> Note that,
On 2019/2/20 15:08, Jaegeuk Kim wrote:
> On 02/18, Chao Yu wrote:
>> On 2019/2/16 12:55, Jaegeuk Kim wrote:
>>> On 02/13, Chao Yu wrote:
On 2019/2/12 10:33, Jaegeuk Kim wrote:
> If we met this once, let fsck.f2fs clear this only.
> Note that, this addresses all the subtle fault
Hello Friend,
I'm "Mrs.TAN ROBE" married to Mr. ROBE ( an International Contractor
and Oil Merchant/ jointly in Exposition of Agro Equipment ) who died
in the Burkina Faso attack, i am 64 years old and diagnosed of cancer
for about 2 years ago and my husband informed me that he deposited the
sum
Add this functionality, placing the descriptor being read in the actual
data buffer in the bio.
That is, for both read and write descriptors query upiu, we are using
the job's request_payload. This in turn, is mapped back in user land to
the applicable sg_io_v4 xferp: dout_xferp for write
Allow to read descriptors via raw upiu. This in fact was forbidden just
as a precaution, as ufs-bsg actually enforces which functionality is
supported.
Signed-off-by: Avri Altman
Reviewed-by: Evan Green
Reviewed-by: Bean Huo
---
drivers/scsi/ufs/ufshcd.c | 20 ++--
1 file
When we had a write descriptor query upiu, we appended the descriptor
right after the bsg request. This was fine as the bsg driver allows to
allocate whatever buffer we needed in its job request.
Still, the proper way to deliver payload, however small (we only write
config descriptors of 144
Hi Paolo, any comments on this patch? And the other one(kvm: x86: Return
LA57 feature based on hardware capability )? :-)
On Fri, Feb 01, 2019 at 12:09:23AM +0800, Yu Zhang wrote:
> Previously, commit 7dcd57552008 ("x86/kvm/mmu: check if tdp/shadow
> MMU reconfiguration is needed") offered some
UFS Protocol Information Units (UPIU) are UFS packets that travel
between the host and the device on the UniPro bus. Our previous series
added the capability to send UPIUs to the ufs driver. It does not cover
all the possible UPIU types - we are mainly focused on device management,
provisioning,
On 19. 02. 19 17:49, Guenter Roeck wrote:
> If xace hardware reports a bad version number, the error handling code
> in ace_setup() calls put_disk(), followed by queue cleanup. However, since
> the disk data structure has the queue pointer set, put_disk() also
> cleans and releases the queue. This
On 02/18, Chao Yu wrote:
> On 2019/2/16 12:55, Jaegeuk Kim wrote:
> > On 02/13, Chao Yu wrote:
> >> On 2019/2/12 10:33, Jaegeuk Kim wrote:
> >>> If we met this once, let fsck.f2fs clear this only.
> >>> Note that, this addresses all the subtle fault injection test.
> >>>
> >>> Signed-off-by:
Thanks for the notification, Stephen.
@Paolo, should I resubmit the patch to correct?
On Sat, Feb 16, 2019 at 06:34:33PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> aa8359972cfc ("KVM: x86/mmu: Differentiate between nr zapped and list
> unstable")
>
> Fixes tag
>
> Fixes:
On Tue, Feb 19, 2019 at 08:58:46PM -0700, Jerry Snitselaar wrote:
> I've seen requests to add linux-security-module to tpm patch
> submissions a couple of times recently, so just add the list
> to MAINTAINERS so get_maintainers.pl will mention it.
>
> Cc: Peter Huewe
> Cc: Jarkko Sakkinen
> Cc:
On Tue, Feb 19, 2019 at 6:42 PM David Howells wrote:
> Eric W. Biederman wrote:
...
> > Looking at your description you are introducing a container id.
>
> Yes. For audit logging, which was why I cc'd Richard.
Not to pile on, but it is more important to CC the audit mailing list.
You can
Hi,
On 19. 02. 19 18:25, Andrew Lunn wrote:
>> Thanks for the suggestion! So I had a closer look at that driver to try
>> and see what could go wrong and it looks like I found a few things
>> there.
>
> Hi Paul
>
> Yes, this driver has issues. If i remember correctly, it got merged
> while i
On Tue, Feb 19, 2019 at 10:46 PM James Bottomley
wrote:
> On Wed, 2019-02-20 at 11:04 +0800, Ian Kent wrote:
> > On Tue, 2019-02-19 at 18:20 -0800, James Bottomley wrote:
> > > On Tue, 2019-02-19 at 23:06 +, David Howells wrote:
> > > > James Bottomley wrote:
> > > >
> > > > > I thought we
On Wed, Feb 20, 2019 at 10:29:46AM +0530, Vaishali Thakkar wrote:
> From: Vinod Koul
>
> Qcom Socinfo driver can be built as a module, so
> export these two APIs.
>
> Signed-off-by: Vinod Koul
> Signed-off-by: Vaishali Thakkar
> ---
> Changes since v1:
> - None
This is fixing a build
Add i.MX8QXP CPU thermal zone support.
Signed-off-by: Anson Huang
---
Changes since V6:
- add fallback compatible string "fsl,imx-sc-thermal" according to i.MX
SC thermal driver
update.
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 28
1 file
Le 20/02/2019 à 06:53, Masahiro Yamada a écrit :
It is fragile to rely on the compiler's optimization to avoid the
section mismatch. Some functions may not be necessarily inlined
when the compiler's inlining heuristic changes.
Add __init markers consistently.
As for prom_getprop() and
This patch enables CONFIG_IMX_SC_THERMAL as module.
Signed-off-by: Anson Huang
---
No changes since V6.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 2d9c390..52d503e 100644
---
i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
inside, the system controller is in charge of controlling power,
clock and thermal sensors etc..
This patch adds i.MX system controller thermal driver support,
Linux kernel has to communicate with system controller via MU
(message
NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as
system controller, the system controller is in charge of system
power, clock and thermal sensors etc. management, Linux kernel
has to communicate with system controller via MU (message unit)
IPC to get temperature from thermal sensors,
Zdravstvujte vas interesuyut klientskie bazy dannyh?
On 2019/2/20 12:10, Herbert Xu wrote:
> On Sat, Feb 02, 2019 at 10:25:43AM +0800, Zhou Wang wrote:
>>
>> In fact, I planned to register to acomp later.
>>
>> It also makes sense to use scomp if hardware engine is faster than CPU.
>> So how about registering to scomp firstly, then we register this
From: Vinod Koul
Date: Wed, 20 Feb 2019 10:10:55 +0530
> On 20-02-19, 09:31, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>> a968b5e9d587 ("net: dsa: qca8k: Enable delay for RGMII_ID mode")
>>
>> Fixes tag
>>
>> Fixes: 40269aa9f40a ("net: dsa: qca8k: disable delay for RGMII
On 2/19/19 10:34 PM, Brendan Higgins wrote:
> On Mon, Feb 18, 2019 at 12:02 PM Frank Rowand wrote:
>
>> I have not read through the patches in any detail. I have read some of
>> the code to try to understand the patches to the devicetree unit tests.
>> So that may limit how valid my comments
On Wed, Feb 20, 2019 at 1:34 AM Kostya Serebryany wrote:
>
> On Tue, Feb 19, 2019 at 2:43 PM Nick Desaulniers
> wrote:
> >
> > + Evgenii, Kostya for KASAN
> >
> > On Tue, Feb 19, 2019 at 2:17 PM Qian Cai wrote:
> > >
> > > On Tue, 2019-02-19 at 22:49 +0100, Arnd Bergmann wrote:
> > > > Building
Hi all,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/nouveau/nouveau_dmem.c:299:11: error: initialization of
'vm_fault_t (*)(struct hmm_devmem *, struct vm_area_struct *, long unsigned
int, const struct page *, unsigned
Hello,
syzbot found the following crash on:
HEAD commit:7a92eb7cc1dc Add linux-next specific files for 20190215
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10b2f400c0
kernel config: https://syzkaller.appspot.com/x/.config?x=b16fd68f18a50133
On 2/19/19 7:39 PM, Brendan Higgins wrote:
> On Mon, Feb 18, 2019 at 11:52 AM Frank Rowand wrote:
>>
>> On 2/14/19 1:37 PM, Brendan Higgins wrote:
>>> Add support for aborting/bailing out of test cases. Needed for
>>> implementing assertions.
>>>
>>> Signed-off-by: Brendan Higgins
>>> ---
>>>
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Thursday, February 14, 2019 6:30 AM
> On Mon, Feb 11, 2019 at 03:34:23PM +, Marc Zyngier wrote:
> > On 31/01/2019 08:03, Aisheng Dong wrote:
> > > One irqsteer channel can support up to 8 output interrupts.
> > >
> > > Cc: Marc Zyngier
> >
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Thursday, February 14, 2019 6:27 AM>
> On Mon, Feb 11, 2019 at 03:35:40PM +, Marc Zyngier wrote:
> > On 31/01/2019 08:03, Aisheng Dong wrote:
> > > Not all 64 interrupts may be used in one group. e.g. most irqsteer
> > > in imx8qxp and
On Mon, Feb 18, 2019 at 12:02 PM Frank Rowand wrote:
> I have not read through the patches in any detail. I have read some of
> the code to try to understand the patches to the devicetree unit tests.
> So that may limit how valid my comments below are.
No problem.
>
> I found the code
On Wed, Feb 20, 2019 at 10:23:00AM +0800, YueHaibing wrote:
> calc_tpm2_event_size() has an invalid signature because
> it returns a 'size_t' where as its signature says that
> it returns 'int'.
>
> Fixes: 4d23cc323cdb ("tpm: add securityfs support for TPM 2.0 firmware event
> log")
>
Hi, Jitao:
On Tue, 2019-02-19 at 17:14 +0800, Jitao Shi wrote:
> Different IC has different mipi_tx setting of dsi.
> This patch separates the mipi_tx hardware relate part for mt8173.
>
> Signed-off-by: Jitao Shi
> ---
> drivers/gpu/drm/mediatek/Makefile | 1 +
>
Hi,
On Fri, Feb 15, 2019 at 10:18:47AM +0100, Wolfram Sang wrote:
> On Tue, Jan 15, 2019 at 11:43:51PM +0100, Wolfram Sang wrote:
> >
> > > All errors (new ones prefixed by >>):
> > >
> > > >> ERROR: "at91_init_twi_bus_slave" [drivers/i2c/busses/i2c-at91.ko]
> > > >> undefined!
> > > >> ERROR:
Could
https://lore.kernel.org/linux-mm/20190219123212.29838-1-lar...@axis.com/T/#u
be relevant?
Tried it, still broken.
I wrote:
But my kernel config had memory compaction (that turned on page migration) and
bounce buffers. I do not remember why I found them necessary but I will try
without
Hi,
>On Thu, Feb 14, 2019 at 07:45:10PM +, Pawel Laszczak wrote:
>> Patch moves some decoding functions from driver/usb/dwc3/debug.h driver
>> to driver/usb/common/debug.c file. These moved functions include:
>> dwc3_decode_get_status
>> dwc3_decode_set_clear_feature
>>
--
Dear Friend,
Greetings and how are you today?
I'm sorry if this message is found in the spam of your email box as
that will certainly be a network misharp and I want us to discuss
about the sum of Fourty Million Dollars discovered in my office and
I'll
give you more details when I hear
Hi Jordan,
On Thu, Feb 7, 2019 at 9:56 AM Jordan Rupprecht wrote:
>
> I have a patch up for review that fixes the second case of chopping
> off the directory when nesting thin archives:
> https://reviews.llvm.org/D57842. I'll commit it tomorrow if there are
> no more comments.
Sorry for late
On Wed, Feb 20, 2019 at 08:58:43AM +0300, Dan Carpenter wrote:
> On Wed, Feb 20, 2019 at 03:08:40AM +, YueHaibing wrote:
> > btrfs_item_size_nr return value is u32, convert it to int may result
> > in truncation.Also read_extent_buffer expect a unsigned param, so
> > min_t should use type u32
On Tue, Feb 19, 2019 at 9:59 PM Like Xu wrote:
> > -/* leaf 0xb sub-leaf types */
> > +/* extended topology sub-leaf types */
> > #define INVALID_TYPE0
> > #define SMT_TYPE1
> > #define CORE_TYPE 2
> > +#define DIE_TYPE 5
>
> This patch set is going to export die topology
Add check for valid ctx pointer and then only dereference ctx to
configure supp_nowait flag.
Fixes: 42bf4152d8a7 ("tee: add supp_nowait flag in tee_context struct")
Reported-by: Dan Carpenter
Signed-off-by: Sumit Garg
---
drivers/tee/tee_core.c | 4 +++-
1 file changed, 3 insertions(+), 1
On Wed, Feb 20, 2019 at 03:08:40AM +, YueHaibing wrote:
> btrfs_item_size_nr return value is u32, convert it to int may result
> in truncation.Also read_extent_buffer expect a unsigned param, so
> min_t should use type u32 to compare.
>
> Fixes: 8ea05e3a4262 ("Btrfs: introduce subvol uuids
It is fragile to rely on the compiler's optimization to avoid the
section mismatch. Some functions may not be necessarily inlined
when the compiler's inlining heuristic changes.
Add __init markers consistently.
As for prom_getprop() and prom_getproplen(), they are marked as
'inline', so inlining
Hi Tony,
On 19/02/19 11:26 PM, Tony Lindgren wrote:
> * Tony Lindgren [190219 17:11]:
>> * Lokesh Vutla [190219 16:19]:
>>> yes. How different is this from any of the above mentioned drivers using
>>> firmware specific ids. Like sci pm domain[1] driver utilizes the same
>>> device id for
> From: Anson Huang
> Sent: Tuesday, February 19, 2019 11:11 AM
>
> The System Controller Firmware (SCFW) controls RTC, thermal and WDOG etc.,
> these resources' interrupt function are managed by SCU. When any IRQ
> pending, SCU will notify Linux via MU general interrupt channel #3, and Linux
>
From: David Chen
RTL8153-BD is used in Dell DA300 type-C dongle.
Added RTL8153-BD support to activate MAC address pass through on DA300.
Apply correction on previously submitted patch in net.git tree.
Signed-off-by: David Chen
---
drivers/net/usb/r8152.c | 2 +-
1 file changed, 1
Good day,
I did send you an email on charity works and I
dont know if you got it.Please reach me for updates or let me know if to
resend
Pablo Mancilla
Hi Vinod,
On Wed, 20 Feb 2019 10:10:55 +0530 Vinod Koul wrote:
>
> Dave would you like to drop this and me sending updated patch or
> something else..
Dave doesn't rebase/reset net-next, so we will just have to use this as
a learning experience :-)
--
Cheers,
Stephen Rothwell
> From: Anson Huang
> Sent: Tuesday, February 19, 2019 11:11 AM
> Subject: [PATCH V3 1/4] dt-bindings: fsl: scu: add general interrupt support
>
> Add scu general interrupt function support.
>
> Signed-off-by: Anson Huang
> Reviewed-by: Rob Herring
> ---
> No change since V2.
> ---
>
From: Ira Weiny
Resending these as I had only 1 minor comment which I believe we have covered
in this series. I was anticipating these going through the mm tree as they
depend on a cleanup patch there and the IB changes are very minor. But they
could just as well go through the IB tree.
NOTE:
From: Ira Weiny
Rather than have a separate get_user_pages_longterm() call,
introduce FOLL_LONGTERM and change the longterm callers to use
it.
This patch does not change any functionality.
FOLL_LONGTERM can only be supported with get_user_pages() as it
requires vmas to determine if DAX is in
From: Ira Weiny
Use the new FOLL_LONGTERM to get_user_pages_fast() to protect against
FS DAX pages being mapped.
Signed-off-by: Ira Weiny
---
drivers/infiniband/hw/qib/qib_user_sdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/qib/qib_user_sdma.c
From: Ira Weiny
In order to support more options in the GUP fast walk, change
the write parameter to flags throughout the call stack.
This patch does not change functionality and passes FOLL_WRITE
where write was previously used.
Signed-off-by: Ira Weiny
---
mm/gup.c | 52
From: Ira Weiny
Use the new FOLL_LONGTERM to get_user_pages_fast() to protect against
FS DAX pages being mapped.
Signed-off-by: Ira Weiny
---
drivers/infiniband/hw/mthca/mthca_memfree.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Hi,
On 2019/02/19 19:11, Arnd Bergmann wrote:
On Tue, Feb 19, 2019 at 6:11 AM Sugaya, Taichi
wrote:
Hi,
Thank you for you comments.
On 2019/02/18 21:09, Arnd Bergmann wrote:
On Fri, Feb 8, 2019 at 1:28 PM Sugaya Taichi
wrote:
+
+ aliases {
+ serial1 =
+ };
From: Ira Weiny
Use the new FOLL_LONGTERM to get_user_pages_fast() to protect against
FS DAX pages being mapped.
Signed-off-by: Ira Weiny
---
drivers/infiniband/hw/hfi1/user_pages.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
From: Ira Weiny
To facilitate additional options to get_user_pages_fast() change the
singular write parameter to be gup_flags.
This patch does not change any functionality. New functionality will
follow in subsequent patches.
Some of the get_user_pages_fast() call sites were unchanged because
From: Ira Weiny
DAX pages were previously unprotected from longterm pins when users
called get_user_pages_fast().
Use the new FOLL_LONGTERM flag to check for DEVMAP pages and fall
back to regular GUP processing if a DEVMAP page is encountered.
Signed-off-by: Ira Weiny
---
mm/gup.c | 24
On 2/19/19 9:19 PM, Zi Yan wrote:
> On 19 Feb 2019, at 19:18, Mike Kravetz wrote:
>> Another high level question. One of the benefits of this approach is
>> that exchanging pages does not require N free pages as you describe
>> above. This assumes that the vma which we are trying to make
Basic audio dmac register only supports busif from 0 to 3,
in order to use busif4 ~ busif7, extended audio dmac register
need to be used
Signed-off-by: Jiada Wang
---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
According to user reference manual for R-CAR H3 and M3-W SoCs,
in order to access busif4 ~ busif7, extended audio dmac registers
(PDMASAREn, PDMADAREn, PDMACHCREn)
need to be used, rather than basic audio dmac registers
(PDMASARn, PDMADARn, PDMACHCRn)
This patch set updates H3 (= r8a7795) and
Basic audio dmac register only supports busif from 0 to 3,
in order to use busif4 ~ busif7, extended audio dmac register
need to be used.
Signed-off-by: Jiada Wang
---
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 19 Feb 2019, at 19:18, Mike Kravetz wrote:
On 2/19/19 6:33 PM, Zi Yan wrote:
On 19 Feb 2019, at 17:42, Mike Kravetz wrote:
On 2/15/19 2:08 PM, Zi Yan wrote:
Thanks for working on this issue!
I have not yet had a chance to take a look at the code. However, I
do have
some general
When waiting on completions, use the _io variant so the caller is
charged as using I/O.
This should have no effect on the module's functionality, only improve
CPU accounting.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-mmc/sd.c | 4 ++--
1 file changed, 2 insertions(+), 2
These comments don't contain useful code or alternate implementation
ideas. Remove them.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-mmc/sd.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/mt7621-mmc/sd.c b/drivers/staging/mt7621-mmc/sd.c
index
This struct does not exist, and when it is looked up in the
compatibility tree, it returns null. Remove these nonfunctional lines.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-spi/spi-mt7621.c | 5 -
1 file changed, 5 deletions(-)
diff --git
There is no need to delay notifying the mmc layer. Schedule the delayed
work to run immediately.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-mmc/sd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/mt7621-mmc/sd.c
The buffer descriptor setup loop is correct only if it is setting up at
least one bd struct. Besides, there is an error somewhere if
dma_map_sg() returns 0. So add a paranoid check for this condition.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-mmc/sd.c | 7 ++-
1 file
This is a series of patches to provide a little TLC for the mt7621-mmc driver.
My original goal was to get it working on the MT7688, and I have succeeded. I
suspect it will now work on any of the MT762x line. The main change was
getting the driver to use the pinctrl subsystem instead of
The module was initializing completions whenever it was going to wait on
them, and not when the completion was allocated. This is incorrect
according to the completion docs:
Calling init_completion() on the same completion object twice is
most likely a bug [...]
Re-initialization is
This is set once during initialization and never changed. Don't bother
setting it again in the interrupt handler.
Signed-off-by: George Hilliard
---
drivers/staging/mt7621-mmc/sd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/mt7621-mmc/sd.c
The driver previously grabbed the SD pins for itself, ignoring the pin
controller. Replace this direct register access with appropriate calls
to the pinctrl subsystem.
This also allows this driver to work on related devices that have a
different pin controller mapping, such as the MT7688. The
The kernel complained:
[ 510.277151] WARNING: CPU: 0 PID: 395 at fs/proc/generic.c:360
proc_register+0xf0/0x108
[ 510.292891] proc_dir_entry '/proc/msdc_debug' already registered
when doing a modprobe/rmmod/modprobe of this module if debug messages
are compiled in. Fix this by
The compiler complains:
drivers/staging/mt7621-mmc/dbg.c: In function ‘msdc_debug_proc_write’:
drivers/staging/mt7621-mmc/dbg.c:237:12: warning: unused variable ‘size’
[-Wunused-variable]
int mode, size;
^~~~
drivers/staging/mt7621-mmc/dbg.c:237:6: warning:
Hi,
On 2019/02/19 18:21, Arnd Bergmann wrote:
On Tue, Feb 19, 2019 at 8:12 AM Sugaya, Taichi
wrote:
On 2019/02/18 21:15, Arnd Bergmann wrote:
On Fri, Feb 8, 2019 at 1:26 PM Sugaya Taichi
wrote:
+static int __init m10v_pm_init(void)
+{
+ suspend_set_ops(_pm_ops);
+
+ return 0;
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, February 15, 2019 4:15 AM
> To: Lu Baolu
> Subject: Re: [PATCH v6 0/9] vfio/mdev: IOMMU aware mediated device
>
> On Wed, 13 Feb 2019 12:02:52 +0800
> Lu Baolu wrote:
>
> > Hi,
> >
> > The Mediate Device is a framework
On 20-02-19, 00:21, Rafael J. Wysocki wrote:
> Hi,
>
> There are a few things related to cpufreq_set_policy() and
> cpufreq_update_policy()
> that increase the level of confusion thereof quite unnecessarily, so this
> series
> attempts to clean them up. Please refer to the patch changelogs for
From: Vinod Koul
Qcom Socinfo driver can be built as a module, so
export these two APIs.
Signed-off-by: Vinod Koul
Signed-off-by: Vaishali Thakkar
---
Changes since v1:
- None
---
drivers/base/soc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/base/soc.c
From: Imran Khan
The Qualcomm socinfo driver exposes information about the SoC, its
version and its serial number to user space.
Signed-off-by: Imran Khan
[Bjorn: Extract code to platform_driver, split patch in multiple]
Signed-off-by: Bjorn Andersson
[Vaishali: Simplify declarations,
The Qualcomm socinfo provides a number of additional attributes,
add these to the socinfo driver and expose them via debugfs
functionality.
Signed-off-by: Vaishali Thakkar
---
Changes since v1:
- Remove unnecessary debugfs dir creation check
- Align ifdefs to left
- Fix
The socinfo driver provides information about version of the various
images loaded in the system. Expose this to user space for debugging
purpose.
Signed-off-by: Vaishali Thakkar
---
Changes since v1:
- None
---
drivers/soc/qcom/socinfo.c | 210 +
1
This patchset adds SoC info driver which can provide information
such as Chip ID, Chip family and serial number about Qualcomm SoCs
to user space via sysfs. Furthermore, it allows userspace to get
information about custom attributes and various image version
information via debugfs.
The patchset
1 - 100 of 1032 matches
Mail list logo
