Hello,
syzbot found the following crash on:
HEAD commit:d2ff0ff2c23f Merge tag 'armsoc-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=124fc13340
kernel config: https://syzkaller.appspot.com/x/.config?x=9384ecb1c973baed
da
Hello,
syzbot found the following crash on:
HEAD commit:aa0c38cf39de Merge branch 'fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105302a740
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Linus,
Please pull one more powerpc fix for 5.0:
The following changes since commit 5a3840a470c41ec0b85cd36ca80370330656b163:
powerpc/papr_scm: Use the correct bind address (2019-02-01 10:13:51 +1100)
are available in the git repository at:
On Thu, 2019-02-14 at 06:23:39 UTC, Michael Ellerman wrote:
> In v4.20 we changed our pgd/pud_present() to check for _PAGE_PRESENT
> rather than just checking that the value is non-zero, e.g.:
>
> static inline int pgd_present(pgd_t pgd)
> {
> - return !pgd_none(pgd);
> + return
On 2019-02-05 07:30 AM, Luis Chamberlain wrote:
On Mon, Jan 14, 2019 at 05:58:30PM +0800, yuank...@codeaurora.org
wrote:
Hi,
Refined at below.
From bbd0d9c8f28eb78ca34353347c3d4092e88f000c Mon Sep 17 00:00:00 2001
This is all garbled, not sure why your patch looks all messed up.
Are you
Andreas Schwab writes:
> On Feb 14 2019, Michael Ellerman wrote:
>
>> The fix is simple, we need to convert the result of the bitwise && to
>> an int before returning it.
>
> Alternatively, the return type could be changed to bool, so that the
> compiler does the right thing by itself.
Yes that
Any comments on this?
On Tue, Feb 12, 2019 at 11:32:36AM +0200, Mike Rapoport wrote:
> The reduce_memory() function clampls the available memory to a limit
> defined by the "mem=" command line parameter. It takes into account the
> amount of already reserved memory and excludes it from the limit
>
Segher Boessenkool writes:
> Hi all,
>
> On Sat, Feb 16, 2019 at 09:55:11PM +1100, Balbir Singh wrote:
>> On Thu, Feb 14, 2019 at 05:23:39PM +1100, Michael Ellerman wrote:
>> > In v4.20 we changed our pgd/pud_present() to check for _PAGE_PRESENT
>> > rather than just checking that the value is no
Balbir Singh writes:
> On Sat, Feb 16, 2019 at 08:22:12AM -0600, Segher Boessenkool wrote:
>> Hi all,
>>
>> On Sat, Feb 16, 2019 at 09:55:11PM +1100, Balbir Singh wrote:
>> > On Thu, Feb 14, 2019 at 05:23:39PM +1100, Michael Ellerman wrote:
>> > > In v4.20 we changed our pgd/pud_present() to chec
Reading from /dev/random may return data while the getrandom
syscall is still blocking.
Those bytes are not yet cryptographically secure.
The first byte from /dev/random can have as little
as 8 bits entropy estimation. Once a read blocks, it will
block until /proc/sys/kernel/random/read_wakeup_t
So not to dispute that this could be a bug, but I couldn't cause a
deadlock. I wonder if you can see something wrong with my method?
*** Set up ***
- kernel 5.0.0-0.rc3.git0.1.fc30.x86_64
- nbd-client 3.19-1.fc30
- nbdkit 1.11.5 (git commit ef9d1978ce28)
Baremetal machine was booted with mem=2G
Use a struct as the platform special data instead of the enumeration.
This is a prepare patch for adding mt8183 iommu support.
Signed-off-by: Yong Wu
Reviewed-by: Matthias Brugger
Reviewed-by: Evan Green
---
drivers/iommu/mtk_iommu.c | 24
drivers/iommu/mtk_iommu.h |
Add two helper functions: paddr_to_iopte and iopte_to_paddr.
Signed-off-by: Yong Wu
Reviewed-by: Robin Murphy
Reviewed-by: Evan Green
---
drivers/iommu/io-pgtable-arm-v7s.c | 45 --
1 file changed, 33 insertions(+), 12 deletions(-)
diff --git a/drivers/iomm
Use a struct as the platform special data instead of the enumeration.
Also there is a minor change that moving the position of
"enum mtk_smi_gen" definition, this is because we expect define
"struct mtk_smi_common_plat" before it is referred.
This is a preparing patch for mt8183.
Signed-off-by:
The larb-id may be remapped in the smi-common, this means the
larb-id reported in the mtk_iommu_isr isn't the real larb-id,
Take mt8183 as a example:
M4U
|
-
| SMI common |
-0-
MediaTek extend the arm v7s descriptor to support the dram over 4GB.
In the mt2712 and mt8173, it's called "4GB mode", the physical address
is from 0x4000_ to 0x1_3fff_, but from EMI point of view, it
is remapped to high address from 0x1__ to 0x1__, the
bit32 is always enab
The config_port of mt2712 and mt8183 are the same. Use a general
config_port interface instead.
In addition, in mt2712, larb8 and larb9 are the bdpsys larbs which
are not the normal larb, their register space are different from the
normal one. thus, we can not call the general config_port. In mt81
In some SoCs, M4U doesn't have its "bclk", it will use the EMI
clock instead which has always been enabled when entering kernel.
Currently mt2712 and mt8173 have this bclk while mt8183 doesn't.
This also is a preparing patch for mt8183.
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drive
This patchset mainly adds support for mt8183 IOMMU and SMI.
mt8183 has only one M4U like mt8173 and is also MTK IOMMU gen2 which
uses ARM Short-Descriptor translation table format.
The mt8183 M4U-SMI HW diagram is as below:
EMI
|
This patch adds decriptions for mt8183 IOMMU and SMI.
mt8183 has only one M4U like mt8173 and is also MTK IOMMU gen2 which
uses ARM Short-Descriptor translation table format.
The mt8183 M4U-SMI HW diagram is as below:
EMI
|
The protect memory setting is a little different in the different SoCs.
In the register REG_MMU_CTRL_REG(0x110), the TF_PROT(translation fault
protect) shift bit is normally 4 while it shift 5 bits only in the
mt8173. This patch delete the complex MACRO and use a common if-else
instead.
Signed-off
In mt8173 and mt8183, 0x48 is REG_MMU_STANDARD_AXI_MODE while it is
REG_MMU_CTRL in the other SoCs, and the bits meaning is completely
different with the REG_MMU_STANDARD_AXI_MODE.
This patch moves this property to plat_data, it's also a preparing
patch for mt8183.
Signed-off-by: Yong Wu
Reviewe
Commit 8099b047ecc4 ("exec: load_script: don't blindly truncate
shebang string") was trying to protect against a confused exec of a
truncated interpreter path. However, it was overeager and also refused
to truncate arguments as well, which broke userspace, and it was
reverted. This attempts the pro
This patch only move the clk_prepare_enable and config_port into the
runtime suspend/resume callback. It doesn't change the code content
and sequence.
This is a preparing patch for adjusting SMI_BUS_SEL for mt8183.
(SMI_BUS_SEL need to be restored after smi-common resume every time.)
Also it gives
There are 2 mmu cells in a M4U HW. we could adjust some larbs entering
mmu0 or mmu1 to balance the bandwidth via the smi-common register
SMI_BUS_SEL(0x220)(Each larb occupy 2 bits).
In mt8183, For better performance, we switch larb1/2/5/7 to enter
mmu1 while the others still keep enter mmu0.
In m
In some SoCs like mt8183, SMI add GALS(Global Async Local Sync) module
which can help synchronize for the modules in different clock frequency.
It can be seen as a "asynchronous fifo". This is a example diagram:
M4U
|
--
||
gals0-rx
The M4U IP blocks in mt8183 is MediaTek's generation2 M4U which use
the ARM Short-descriptor like mt8173, and most of the HW registers
are the same.
Here list main differences between mt8183 and mt8173/mt2712:
1) mt8183 has only one M4U HW like mt8173 while mt2712 has two.
2) mt8183 don't have the
This patch only rename the variable name from enable_4GB to
dram_is_4gb for readable.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 10 +-
drivers/iommu/mtk_iommu.h | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/
This patch only improve the shutdown flow. The shutdown callback will
mute the M4U HW when the system shutdown.
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drivers/iommu/mtk_iommu.c| 6 ++
drivers/iommu/mtk_iommu_v1.c | 6 ++
2 files changed, 12 insertions(+)
diff --git a/dr
Normally the M4U HW connect EMI with smi. the diagram is like below:
EMI
|
M4U
|
smi-common
|
-
||| |...
larb0 larb1 larb2 larb3
Actually there are 2 mmu cells in
The register VLD_PA_RNG(0x118) was forgot to backup while adding 4GB
mode support for mt2712. this patch add it.
Fixes: 30e2fccf9512 ("iommu/mediatek: Enlarge the validate PA range
for 4GB mode")
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drivers/iommu/mtk_iommu.c | 2 ++
drivers/iommu/
The "mediatek,larb-id" has already been parsed in MTK IOMMU driver.
It's no need to parse it again in SMI driver. Only clean some codes.
This patch is fit for all the current mt2701, mt2712, mt7623, mt8173
and mt8183.
After this patch, the "mediatek,larb-id" only be needed for mt2712
which have 2
Both mt8173 and mt8183 don't have this vld_pa_rng(valid physical address
range) register while mt2712 have. Move it into the plat_data.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 3 ++-
drivers/iommu/mtk_iommu.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/dri
In the 4GB mode, the physical address is remapped,
Here is the detailed remap relationship.
CPU PA ->HW PA
0x4000_ 0x1_4000_ (Add bit32)
0x8000_ 0x1_8000_ ...
0xc000_ 0x1_c000_ ...
0x1__0x1__ (No change)
Thus,
Switch to SPDX license identifier for MediaTek iommu/smi and their
header files.
Signed-off-by: Yong Wu
Reviewed-by: Rob Herring
Reviewed-by: Evan Green
---
drivers/iommu/mtk_iommu.c | 10 +-
drivers/iommu/mtk_iommu.h | 10 +-
drivers/iom
This is v5 patchset for supporting goodix GT5553 CTP. Here is the
previous version[1]
Changes for v4:
- document AVDD22, DVDD12, VDDIO as optional properties
- use regulator bulk calls, for get, enable and disable functionalities
Changes for v4:
- devm_add_action_or_reset for disabling regulator
C
On Sun, Feb 17, 2019 at 1:21 PM Jagan Teki wrote:
>
> Hi Dmitry and Rob,
>
> On Thu, Feb 14, 2019 at 3:21 AM Rob Herring wrote:
> >
> > On Tue, Jan 22, 2019 at 7:39 AM Jagan Teki
> > wrote:
> > >
> > > On Mon, Jan 21, 2019 at 9:46 PM Rob Herring wrote:
> > > >
> > > > On Fri, Jan 18, 2019 at 1
Goodix CTP controllers support analog, digital and gpio regulator
supplies on relevant controller pin configurations.
Out of which AVDD28 regulator is mandatory supplied regulator in most
of the board designs, so document AVDD28 as required property and
rest marked as optional regulators.
Signed-
GT5663 is capacitive touch controller with customized smart
wakeup gestures.
Add support for it by adding compatible and supported chip data.
The chip data on GT5663 is similar to GT1151, like
- config data register has 0x8050 address
- config data register max len is 240
- config data checksum h
Goodix CTP controllers support analog, digital and gpio regulator
supplies on relevant controller pin configurations.
Support them via regulator bulk calls.
Signed-off-by: Jagan Teki
---
drivers/input/touchscreen/goodix.c | 58 ++
1 file changed, 52 insertions(+), 6
GT5663 is capacitive touch controller with customized smart
wakeup gestures, it support chipdata which is similar to
existing GT1151 and require AVDD28 supply for some boards.
Document the compatible for the same.
Signed-off-by: Jagan Teki
---
Documentation/devicetree/bindings/input/touchscreen
On 2/14/19 8:51 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
We need to create an irq domain if we want to select SPARSE_IRQ. The
cp-intc driver already supports it, but aintc doesn't. Use the helpers
provided by the generic irq chip abstraction.
Signed-off-by: Bartosz Golaszews
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Once we select SPARSE_IRQ, the interrupt numbers defined in mach/irqs.h
will only signify the hardware interrupt offsets, not the interrupt
numbers seen by linux. Introduce a wrapper macro that translates the
hwirq number
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
The existence of irqs.h in mach-davinci/include/mach only makes sense
without SPARSE_IRQ as it's then expected to define NR_IRQS and is
included from asm/irq.h. As we now support SPARSE_IRQ, this header can
be moved to mac
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Raplace all calls to __raw_readl() & __raw_writel() with readl_relaxed()
and writel_relaxed() respectively. It's safe to do as there's no
endianness conversion being done in the code.
This patch only changes writel. Ther
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add a config structure that will be used by aintc-based platforms.
It contains the register range resource, number of interrupts and
a list of priorities.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechn
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add the new-style config structures for dm* SoCs. They will be used
once we make the aintc driver stop using davinci_soc_info.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechner
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add a missing call to request_mem_region() before calling ioremap() to
make sure the region is not being used by anyone else.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by:
> +@search exists@
> +local idexpression id;
> +expression x,e,e1;
> +position p1,p2;
> +type T,T1,T2;
> +@@
> +
> +id = of_find_device_by_node@p1(x)
> +... when != e = id
I suggest to increase your software development attention also for
another implementation detail.
Source code analysis trigger
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
The aintc driver has now been cleaned up. Move it to drivers/irqchip
where it belongs. There's no device-tree support for any dm* board so
there's no IRQCHIP_OF_DECLARE() - there's only the exported init
function called fr
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add a config structure that will be used by cp-intc-based platforms.
It contains the register range resource and the number of interrupts.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechner
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add the new-style config structures for da8xx SoCs. They will be used
once we make the cp-intc driver stop using davinci_soc_info.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechner
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Modify the cp-intc driver to take all its configuration from the new
config structure. Stop referencing davinci_soc_info in any way.
Move the declaration for davinci_cp_intc_init() to
irq-davinci-cp-intc.h and make it take
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Add a missing call to request_mem_region() before calling ioremap() to
make sure it's not been requested by another user.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechner
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Raplace all calls to __raw_readl() & __raw_writel() with readl_relaxed()
s/Raplace/Replace/
and writel_relaxed() respectively. It's safe to do as there's no
endianness conversion being done in the code.
Should this b
On Tue, 2019-02-05 at 15:11 -0800, Evan Green wrote:
> On Fri, Feb 1, 2019 at 1:42 AM Yong Wu wrote:
> >
> > On Thu, 2019-01-31 at 11:23 -0800, Evan Green wrote:
> > > On Wed, Jan 30, 2019 at 10:59 PM Yong Wu wrote:
> > > >
> > > > On Wed, 2019-01-30 at 10:28 -0800, Evan Green wrote:
> > > > > On
On 2/14/19 8:52 AM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
The fields related to the two davinci interrupt controllers are no
longer used. Remove them.
Signed-off-by: Bartosz Golaszewski
---
Reviewed-by: David Lechner
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 528871b456026e6127d95b1b2bd8e3a003dc1614 perf/core: Fix impossible
ring-buffer sizes warning
Two fixes on the kernel side: fix an ov
Linus,
I2C has two more driver bugfixes for you.
Please pull.
Thanks,
Wolfram
The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: f331e766c4be33f4338574f3c9f7f77e98ab4571 x86/platform/UV: Use
efi_runtime_lock to serialise BIOS calls
Three changes:
- An UV fix/qu
On 14/02/2019 15:23, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Check if there are any imported dma-bufs left not released by
> user-space when grant device's release callback is called and
> free those if this is the case. This can happen if user-space
> leaks the buffers
On 14/02/2019 15:23, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> If there are exported DMA buffers which are still in use and
> grant device is closed by either normal user-space close or by
> a signal this leads to the grant device context to be destroyed,
> thus making it
Hello Heiko,
On 2019/02/12 20:12, Heiko Stübner wrote:
Hi,
Am Montag, 4. Februar 2019, 13:59:37 CET schrieb Katsuhiro Suzuki:
On 2019/02/03 18:06, Heiko Stuebner wrote:
Am Samstag, 2. Februar 2019, 05:34:44 CET schrieb Katsuhiro Suzuki:
This patch adds HDMI sound (I2S0) node and remove dma p
Linus,
Please pull the latest efi-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
efi-urgent-for-linus
# HEAD: 582a32e708823e5957fd73ccd78dc4a9e49d21ea efi/arm: Revert "Defer
persistent reservations until after paging_init()"
This tree reverts a
Am Samstag, 16. Februar 2019, 11:25:45 CET schrieb Johan Jonker:
> The mmc1 pins are used for SDIO with a wifi chip.
> The function mmc_sdio_switch_hs() only checks for MMC_CAP_SD_HIGHSPEED and
> not for MMC_CAP_MMC_HIGHSPEED, so cap-mmc-highspeed can be removed.
>
> Signed-off-by: Johan Jonker
On Fri, Feb 15, 2019 at 02:08:26PM -0800, Zi Yan wrote:
> +struct page_flags {
> + unsigned int page_error :1;
> + unsigned int page_referenced:1;
> + unsigned int page_uptodate:1;
> + unsigned int page_active:1;
> + unsigned int page_unevictable:1;
> + unsigned int page_che
On Sun, 17 Feb 2019, Markus Elfring wrote:
> > +@search exists@
> > +local idexpression id;
> > +expression x,e,e1;
> > +position p1,p2;
> > +type T,T1,T2;
> > +@@
> > +
> > +id = of_find_device_by_node@p1(x)
> > +... when != e = id
>
> I suggest to increase your software development attention
>>> +@search exists@
>>> +local idexpression id;
>>> +expression x,e,e1;
>>> +position p1,p2;
>>> +type T,T1,T2;
>>> +@@
>>> +
>>> +id = of_find_device_by_node@p1(x)
>>> +... when != e = id
>>
>> I suggest to increase your software development attention also for
>> another implementation detail.
>>
On Sun, 17 Feb 2019, Markus Elfring wrote:
> >>> +@search exists@
> >>> +local idexpression id;
> >>> +expression x,e,e1;
> >>> +position p1,p2;
> >>> +type T,T1,T2;
> >>> +@@
> >>> +
> >>> +id = of_find_device_by_node@p1(x)
> >>> +... when != e = id
> >>
> >> I suggest to increase your softwar
>> Would you dare to interpret my update suggestion (reordering of two
>> identifiers)
>> as a required SmPL script correction?
>
> I didn't suggest to reorder anything.
This is obvious according to your acknowledgement for the sixth version
of this evolving SmPL script.
> Both are needed.
If
On Sun, 17 Feb 2019, Markus Elfring wrote:
> >> Would you dare to interpret my update suggestion (reordering of two
> >> identifiers)
> >> as a required SmPL script correction?
> >
> > I didn't suggest to reorder anything.
>
> This is obvious according to your acknowledgement for the sixth ver
>> If you would insist on the specification of such an assignment exclusion
>> for a SmPL ellipsis:
>> Can we agree on a correct order?
>
> I don't get your point.
I propose to take another closer look at a bit of SmPL code.
> There is no correct order.
I have got an other software development
Hi,
On 2/16/19 11:03 PM, Hans de Goede wrote:
Hi,
On 2/16/19 10:54 PM, Jacek Anaszewski wrote:
On 2/16/19 8:37 PM, Pavel Machek wrote:
Hi!
I think that should work fine, which means that we can use the
timer and
pattern trigger support for the blinking and breathing modes.
That still leav
On Sat, Feb 16, 2019 at 11:33:58PM +0100, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Move the local variable 'ret' into the IP_VS_IPV6 ifdef so that the
> unused variable warning doesn't fire for randconfig builds with
> CONFIG_IP_VS_IPV6 disabled.
Thanks! We already have a patch for thi
On Sun, 17 Feb 2019, Markus Elfring wrote:
> >> If you would insist on the specification of such an assignment exclusion
> >> for a SmPL ellipsis:
> >> Can we agree on a correct order?
> >
> > I don't get your point.
>
> I propose to take another closer look at a bit of SmPL code.
>
>
> > There
On Fri, Feb 15, 2019 at 03:51:26PM +0100, Christoph Hellwig wrote:
> I still don't understand why mp_bvec_last_segment isn't simply
> called bvec_last_segment as there is no conflict. But I don't
> want to hold this series up on that as there only are two users
> left and we can always just fix it
On Fri, Feb 15, 2019 at 09:14:15AM -0800, Bart Van Assche wrote:
> On Fri, 2019-02-15 at 08:49 -0700, Jens Axboe wrote:
> > On 2/15/19 4:13 AM, Ming Lei wrote:
> > > This patchset brings multi-page bvec into block layer:
> >
> > Applied, thanks Ming. Let's hope it sticks!
>
> Hi Jens and Ming,
>
On Fri, Feb 15, 2019 at 10:59:47AM -0700, Jens Axboe wrote:
> On 2/15/19 10:14 AM, Bart Van Assche wrote:
> > On Fri, 2019-02-15 at 08:49 -0700, Jens Axboe wrote:
> >> On 2/15/19 4:13 AM, Ming Lei wrote:
> >>> This patchset brings multi-page bvec into block layer:
> >>
> >> Applied, thanks Ming. Le
>> …
>> +@search exists@
>> +local idexpression id;
>> +expression x,e,e1;
>> +position p1,p2;
>> …
>> +@@
>> +
>> +id = of_find_device_by_node@p1(x)
>> +... when != e = id
>> …
>>
>> Or:
>>
>> …
>> + ... when != id = e
>> …
>>
>>
>> Which SmPL specification will achieve the desired software behavi
Am Sonntag, 17. Februar 2019, 11:58:36 CET schrieb Katsuhiro Suzuki:
> Hello Heiko,
>
> On 2019/02/12 20:12, Heiko Stübner wrote:
> > Hi,
> >
> > Am Montag, 4. Februar 2019, 13:59:37 CET schrieb Katsuhiro Suzuki:
> >> On 2019/02/03 18:06, Heiko Stuebner wrote:
> >>> Am Samstag, 2. Februar 2019, 0
On Fri, Feb 15, 2019 at 08:08:08AM -0800, Bart Van Assche wrote:
> On Fri, 2019-02-15 at 10:26 +0800, Ming Lei wrote:
> > There might be lots of blk_flush_queue instance which is allocated
> > for each hctx, then lots of class key slot may be wasted.
> >
> > So I suggest to use one nvmet_loop_flus
On Tue, 2019-02-12 at 10:28 +0100, Matthias Brugger wrote:
>
> On 12/02/2019 07:19, Jitao Shi wrote:
> > This patch adds mipi tx driver support for mt8183.
> >
> > Mipi_tx of mt8183 is very different to mt8173.
> > 1.Separate mipi tx setting to mtk_mt8173_mipi_tx.c for mt8173
> > 2.Separate mipi
On Sat, Feb 16, 2019 at 06:13:07PM +0100, Thomas Gleixner wrote:
> All information and calculations in the interrupt affinity spreading code
> is strictly unsigned int. Though the code uses int all over the place.
>
> Convert it over to unsigned int.
>
> Signed-off-by: Thomas Gleixner
> ---
> i
On Sat, Feb 16, 2019 at 06:13:11PM +0100, Thomas Gleixner wrote:
> Now that the NVME driver is converted over to the calc_set() callback, the
> workarounds of the original set support can be removed.
>
> Signed-off-by: Thomas Gleixner
> ---
> kernel/irq/affinity.c | 20
>
On Sat, Feb 16, 2019 at 06:13:12PM +0100, Thomas Gleixner wrote:
> Multiple interrupt sets for affinity spreading are now handled in the core
> code and the number of sets and their size is recalculated via a driver
> supplied callback.
>
> That avoids the requirement to invoke pci_alloc_irq_vecto
Hi Thomas,
On Sat, Feb 16, 2019 at 06:13:13PM +0100, Thomas Gleixner wrote:
> Some drivers need an extra set of interrupts which should not be marked
> managed, but should get initial interrupt spreading.
Could you share the drivers and their use case?
>
> Add a bitmap to struct irq_affinity wh
Use linear range to replace the twl6030ldo_list_voltage implementation.
With this change, the min_mV is not used and can be removed from
struct twlreg_info.
Signed-off-by: Axel Lin
---
drivers/regulator/twl6030-regulator.c | 73 ++-
1 file changed, 27 insertions(+), 46 de
Signed-off-by: Axel Lin
---
drivers/regulator/twl6030-regulator.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/regulator/twl6030-regulator.c
b/drivers/regulator/twl6030-regulator.c
index dcaa6512d760..15f19df6bc5d 100644
--- a/drivers/regulator/twl6030-regu
On 2/17/19 9:44 AM, Bernd Edlinger wrote:
>
> + if (crng_ready() && !blocking_pool.initialized &&
After some more debugging I realize that blocking_pool.initialized
is true after 128 bits of input entropy, but that is only 80 bits
credited, due to the asymptotic 3/4 crediting formula
From: Ryder Lee
Update the binding for MT7629 SoC, which uses fallback compatible to
MT6765 SYST, so add more descriptions to distinguish it from the other
SoCs that use GPT.
Signed-off-by: Ryder Lee
Cc: Daniel Lezcano
---
.../devicetree/bindings/timer/mediatek,mtk-timer.txt | 11 +++
From: Ryder Lee
This fixes a typo for MT7623A
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/soc/mediatek/scpsys.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/scpsys.txt
b/Documentation/devicetree/binding
From: Ryder Lee
This updates bindings for MT7629 SoC, which includes very basic items
such as system timer, UART, sysirq and scpsys unit.
Signed-off-by: Ryder Lee
Cc: Marc Zyngier
Cc: Greg Kroah-Hartman
---
.../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 5 +++--
Docum
Hi all,
In commit
a40061ea2e39 ("net: systemport: Fix reception of BPDUs")
Fixes tag
Fixes: 4e8aedfe78c7 ("net: systemport: Turn on offloads by default")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: b5061778f822 ("net: systemport: Turn on offloads by def
Hi all,
Commits
28df69acbd27 ("xen-scsiback: mark expected switch fall-through")
7bb17e0ca4a5 ("xen: mark expected switch fall-through")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
pgpkPsg58d30U.pgp
Description: OpenPGP digital signature
Hi Alexandre,
On Mon, Feb 11, 2019 at 11:33 AM Alexandre Belloni
wrote:
>
> rtc_nvmem_unregister() is called on rtc_device release so it is not
> necessary to call it from the driver.
thank you for taking care of the linker-error!
> Signed-off-by: Alexandre Belloni
Reviewed-by: Martin Blumensti
Hi,
On 2/17/19 1:08 AM, Pavel Machek wrote:
I don't pretend to fully understand it, _but_ hw_pattern should really
describe the pattern LED should do, not whether it reacts to charging
or not.
Then we are back to step 1 of the discussion, that we need another
mechanism outside of the trigger
Extend the inkern API with a function for reading available
attribute values of iio channels.
Signed-off-by: Artur Rojek
---
drivers/iio/inkern.c | 20
include/linux/iio/consumer.h | 14 ++
2 files changed, 34 insertions(+)
diff --git a/drivers/iio/inker
Add documentation for the ingenic-battery driver, used on JZ47xx SoCs.
Signed-off-by: Artur Rojek
---
.../bindings/power/supply/ingenic,battery.txt | 31 +++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetree/bindings/power/supply/ingenic,battery.txt
Add documentation for the "voltage-max-design-microvolt" property.
Signed-off-by: Artur Rojek
---
Documentation/devicetree/bindings/power/supply/battery.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/supply/battery.txt
b/Documentation/devicetre
Add a field for "voltage_max_design_uv" to present fully charged
battery voltage.
Signed-off-by: Artur Rojek
---
drivers/power/supply/power_supply_core.c | 3 +++
include/linux/power_supply.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/power/supply/power_supply_core
1 - 100 of 391 matches
Mail list logo
