On 06/27/18 at 11:14pm, Pavel Tatashin wrote:
> Honestly, I do not like this new agrument, but it will do for now. I
> could not think of a better way without rewriting everything.
>
> Reviewed-by: Pavel Tatashin
>
> However, I will submit a series of patches to cleanup sparse.c and
> completely
On Thu, 2018-06-28 at 09:57 +0800, CK Hu wrote:
> Hi, Houlong:
>
> On Wed, 2018-06-27 at 19:53 +0800, houlong wei wrote:
> > On Wed, 2018-02-21 at 11:53 +0800, CK Hu wrote:
> > > Hi, Houlong:
> > >
> > > I've one inline comment.
> > >
> > > On Wed, 2018-01-31 at 15:28 +0800, houlong@mediatek
On Thu, Jun 21, 2018 at 8:43 AM Naga Sureshkumar Relli
wrote:
Thanks for your patch!
> Add pl353 static memory controller devicetree binding information.
>
> Signed-off-by: Naga Sureshkumar Relli
> +Device tree bindings for ARM PL353 static memory controller
> +
> +PL353 static memory controlle
On Thu, Jun 21, 2018 at 8:43 AM Naga Sureshkumar Relli
wrote:
> Add driver for arm pl353 static memory controller. This controller is used in
> Xilinx Zynq SoC for interfacing the NAND and NOR/SRAM memory devices.
>
> Signed-off-by: Naga Sureshkumar Relli
(...)
> +config PL353_SMC
> + tr
On 28.6.2018 07:42, Luis Araneda wrote:
> The bindings were missing when adding the device-tree files
> Also, improve description of existing boards
>
> Signed-off-by: Luis Araneda
> ---
> .../devicetree/bindings/arm/xilinx.txt| 22 +--
> 1 file changed, 20 insertions(+),
On 28.6.2018 07:42, Luis Araneda wrote:
> The value "zynq" isn't officially part of the model on any board.
> Additionally, the value is redundant as it's included in a
> subsequent value of the property.
>
> Signed-off-by: Luis Araneda
> ---
> .../devicetree/bindings/arm/xilinx.txt| 22
On 28.6.2018 07:42, Luis Araneda wrote:
> The real name of the board is ZedBoard, from Avnet
>
> Signed-off-by: Luis Araneda
> ---
> Documentation/devicetree/bindings/arm/xilinx.txt | 2 +-
> arch/arm/boot/dts/Makefile| 2 +-
> arch/arm/boot/dts/{zynq-zed.dts =>
mostly ignoring m68k Linux. People
using that are hard core. People using x86/x64 Linux aren't such hard core
folks. And I bet most of them want to read the disks so they can copy stuff to
Amiga Forever or WinUAE running on other architectures. So TB is not likely to
be an issue for them, e
On 28.6.2018 07:42, Luis Araneda wrote:
> Replace the current value of the model property by a more accurate
> description of each board (which includes the manufacturer), as some
> of the boards had the same value ("Xilinx Zynq")
>
> Signed-off-by: Luis Araneda
> ---
> arch/arm/boot/dts/zynq-cc
On 06/27/18 at 11:19pm, Pavel Tatashin wrote:
> > Signed-off-by: Baoquan He
> >
> > Signed-off-by: Baoquan He
>
> Please remove duplicated signed-off
Done.
>
> > if (!usemap) {
> > ms->section_mem_map = 0;
> > + nr_consumed_maps++;
On 28.6.2018 07:42, Luis Araneda wrote:
> Both boards are made by Avnet, Inc.
>
> Signed-off-by: Luis Araneda
> ---
> arch/arm/boot/dts/zynq-microzed.dts | 2 +-
> arch/arm/boot/dts/zynq-zed.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/z
In sparse_init(), two temporary pointer arrays, usemap_map and map_map
are allocated with the size of NR_MEM_SECTIONS. They are used to store
each memory section's usemap and mem map if marked as present. With
the help of these two arrays, continuous memory chunk is allocated for
usemap and memmap
alloc_usemap_and_memmap() is passing in a "void *" that points to
usemap_map or memmap_map. In next patch we will change both of the
map allocation from taking 'NR_MEM_SECTIONS' as the length to taking
'nr_present_sections' as the length. After that, the passed in 'void*'
needs to update as things
In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y, system
will allocate one continuous memory chunk for mem maps on one node and
populate the relevant page tables to map memory section one by one. If
fail to populate for a certain mem section, print warning and its
->section_mem_map wi
This is v6 post.
In sparse_init(), two temporary pointer arrays, usemap_map and map_map
are allocated with the size of NR_MEM_SECTIONS. They are used to store
each memory section's usemap and mem map if marked as present. In
5-level paging mode, this will cost 512M memory though they will be
relea
It's used to record how many memory sections are marked as present
during system boot up, and will be used in the later patch.
Signed-off-by: Baoquan He
Reviewed-by: Pavel Tatashin
---
mm/sparse.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/mm/sparse.c b/mm/sparse.c
index f13f272
Pavel pointed out that the behaviour of allocating memmap together
for one node should be defaulted for all ARCH-es. It won't break
anything because it will drop to the fallback action to allocate
imemmap for each section at one time if failed on large chunk of
memory.
So remove CONFIG_SPARSEMEM_A
The mm-of-the-moment snapshot 2018-06-27-23-21 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
Thanks Rob for reviewing.
On 6/26/2018 12:47 AM, Rob Herring wrote:
On Thu, Jun 21, 2018 at 04:23:18PM +0530, Rohit kumar wrote:
Add devicetree bindings documentation file for SDM845 sound card.
Signed-off-by: Rohit kumar
---
.../devicetree/bindings/sound/qcom,sdm845.txt | 82
Hi all,
Changes since 20180627:
The sunxi tree gained a build failure so I used the version from
next-20180627.
The btrfs-kdave tree gained a build failure so I used the version from
next-20180626.
The drm tree lost its build failure.
The xarray tree gained a conflict against the wireless
On Thu, 28 Jun 2018 13:35:15 +0800 "Huang\, Ying" wrote:
> Andrew Morton writes:
>
> > On Thu, 28 Jun 2018 13:29:09 +0800 "Huang\, Ying"
> > wrote:
> >
> >> Andrew Morton writes:
> >>
> >> > On Fri, 22 Jun 2018 11:51:30 +0800 "Huang, Ying"
> >> > wrote:
> >> >
> >> >> This is the final st
On 22-06-18, 11:24, Guodong Xu wrote:
> From: Li Yu
>
> On k3 series of SoC, DMA controller reserves some channels for
> other on-chip coprocessors. By adding support to dma_min_chan, kernel
> will not be able to use these reserved channels.
>
> One example is on Hi3660 platform, channel 0 is re
On Thu, Jun 28, 2018 at 11:45:37AM +0800, Stu Hsieh wrote:
> Hi, Daniel Vetter:
>
> On Mon, 2018-06-25 at 10:47 +0200, Daniel Vetter wrote:
> > On Wed, Jun 20, 2018 at 04:19:02PM +0800, Stu Hsieh wrote:
> > > This patch add support for the Mediatek MT2712 DISP subsystem.
> > > MT2712 is base on MT
On 22-06-18, 11:24, Guodong Xu wrote:
> From: Li Yu
>
> Add optional property dma_min_chan for k3dma.
>
> Signed-off-by: Li Yu
> ---
> Documentation/devicetree/bindings/dma/k3dma.txt | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/dma/k3dma.txt
On 19-06-18, 15:20, Marek Szyprowski wrote:
> The reported residue is already calculated in BURST unit granularity, so
> advertise this capability properly to other devices in the system.
Applied, thanks
--
~Vinod
On Tue, Jun 26, 2018 at 09:57:07AM +0100, David Howells wrote:
> Andrei Vagin wrote:
>
> > > > > - mnt = kern_mount_data(&proc_fs_type, ns, 0);
> > >
> > > Here ns->user_ns and get_current_cred()->user_ns are not always equal
> >
> > What do you think about the attached patch?
> > ...
> > -
lost a delightful drawing. Jerry reported it. Amigoids screamed. I tried
to tell them I was there, it was my machine, and 1.1 was, indeed, crap.
{o.o}
On 20180627 02:00, Michael Schmitz wrote:
Joanne,
I'm not at all allergic to avoiding RDB at all cost for new disks. If
AmigaOS 4.1 support
The real name of the board is ZedBoard, from Avnet
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/xilinx.txt | 2 +-
arch/arm/boot/dts/Makefile| 2 +-
arch/arm/boot/dts/{zynq-zed.dts => zynq-zedboard.dts} | 2 +-
3 files changed, 3 insertio
This series attempts to standardize device naming and improve
its information for better identification
The values of the "compatible" and "model" device-tree properties
are corrected for some devices, adding complementary information
when necessary
Additionally, a device-tree file is renamed to
The bindings were missing when adding the device-tree files
Also, improve description of existing boards
Signed-off-by: Luis Araneda
---
.../devicetree/bindings/arm/xilinx.txt| 22 +--
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree
The value "zynq" isn't officially part of the model on any board.
Additionally, the value is redundant as it's included in a
subsequent value of the property.
Signed-off-by: Luis Araneda
---
.../devicetree/bindings/arm/xilinx.txt| 22 +--
arch/arm/boot/dts/zynq-cc108.dts
Replace the current value of the model property by a more accurate
description of each board (which includes the manufacturer), as some
of the boards had the same value ("Xilinx Zynq")
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-cc108.dts | 2 +-
arch/arm/boot/dts/zynq-microzed.
Both boards are made by Avnet, Inc.
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-microzed.dts | 2 +-
arch/arm/boot/dts/zynq-zed.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/zynq-microzed.dts
b/arch/arm/boot/dts/zynq-microzed.dts
in
On Wed, 27 Jun 2018 20:54:34 +0200,
Guy Chronister wrote:
>
> Signed-off-by: Guy Chronister
The code change itself is good, but the subject is wrong, and there is
no changelog texts. Please describe what it really fixes. It's not
about typo fix, but it fixes a real bug, and this has to be writ
Andrew Morton writes:
> On Thu, 28 Jun 2018 13:29:09 +0800 "Huang\, Ying"
> wrote:
>
>> Andrew Morton writes:
>>
>> > On Fri, 22 Jun 2018 11:51:30 +0800 "Huang, Ying"
>> > wrote:
>> >
>> >> This is the final step of THP (Transparent Huge Page) swap
>> >> optimization. After the first and s
On Thu, 28 Jun 2018 13:29:09 +0800 "Huang\, Ying" wrote:
> Andrew Morton writes:
>
> > On Fri, 22 Jun 2018 11:51:30 +0800 "Huang, Ying"
> > wrote:
> >
> >> This is the final step of THP (Transparent Huge Page) swap
> >> optimization. After the first and second step, the splitting huge
> >> p
Andrew Morton writes:
> On Fri, 22 Jun 2018 11:51:30 +0800 "Huang, Ying" wrote:
>
>> This is the final step of THP (Transparent Huge Page) swap
>> optimization. After the first and second step, the splitting huge
>> page is delayed from almost the first step of swapout to after swapout
>> has b
On Sat, Apr 14, 2018 at 3:07 AM, syzbot
wrote:
> syzbot has found reproducer for the following crash on upstream commit
> 1bad9ce155a7c010a9a5f3261ad12a6a8eccfb2c (Fri Apr 13 19:27:11 2018 +)
> Merge tag 'sh-for-4.17' of git://git.libc.org/linux-sh
> syzbot dashboard link:
> https://syzkaller.
On Thu, Jun 28, 2018 at 7:24 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:debd52a05061 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1058cc9f80
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:debd52a05061 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1058cc9f80
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
da
On Thu, Jun 28, 2018 at 11:06:13AM +0800, Sean Wang wrote:
> On Wed, 2018-06-27 at 20:04 +0300, Andy Shevchenko wrote:
> > On Wed, Jun 27, 2018 at 7:59 PM, Andy Shevchenko
> > wrote:
> > > On Wed, Jun 27, 2018 at 8:43 AM, wrote:
> > >> From: Sean Wang
> > >> +#include
> > >> +#include
> >
>
This patch implements the 'pattern_set', 'pattern_get' and 'pattern_clear'
interfaces to support SC27XX LED breathing mode.
Signed-off-by: Baolin Wang
---
Changes from v1:
- No updates.
---
drivers/leds/leds-sc27xx-bltc.c | 160 +++
1 file changed, 160 inser
From: Bjorn Andersson
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class drivers can implement
if they support such functionality as well as a new device attrib
On Wed, Jun 27, 2018 at 07:51:34PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 27, 2018 at 08:57:21AM -0700, Paul E. McKenney wrote:
> > > Another variant, which simply skips the wakeup whever ran on an offline
> > > CPU, relying on the wakeup from rcutree_migrate_callbacks() right after
> > > the C
On Wed, Jun 27, 2018 at 11:27:26AM -0700, Joel Fernandes wrote:
[..]
> > > > s = __ALIGN_MASK(s, RCU_SEQ_STATE_MASK);
> > > >
> > >
> > > I agree with Peter's suggestions for both the verbiage reduction in the
> > > comments in the header, as the new code he is proposing is more
> > > sel
Hi Ben,
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> The Aspeed AST2x00 can contain a ColdFire v1 coprocessor which
> is currently unused on OpenPower systems.
>
> This adds an alternative to the fsi-master-gpio driver that
> uses that coprocessor instead of bit banging from the ARM
Hi Miquel,
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Wednesday, June 27, 2018 8:53 PM
> To: Naga Sureshkumar Relli
> Cc: boris.brezil...@bootlin.com; rich...@nod.at; dw...@infradead.org;
> computersforpe...@gmail.com; marek.va...@gmail.com; f.fa
On Fri, 22 Jun 2018 11:51:30 +0800 "Huang, Ying" wrote:
> This is the final step of THP (Transparent Huge Page) swap
> optimization. After the first and second step, the splitting huge
> page is delayed from almost the first step of swapout to after swapout
> has been finished. In this step, we
On Wed, 27 Jun 2018 21:18:34 -0700 Joe Perches wrote:
> On Wed, 2018-06-27 at 18:13 -0700, Andrew Morton wrote:
> > On Wed, 27 Jun 2018 18:05:35 -0700 Joe Perches wrote:
> >
> > > On Wed, 2018-06-27 at 22:48 +0300, Alexey Dobriyan wrote:
> > > > I know I'll regret it.
> > >
> > > This wasn't a
On Wed, Jun 27, 2018 at 9:24 PM Andrey Smirnov wrote:
>
> ZII's RDU1s come with two EEPROMs attached to RAVE SP. Add
Ugh, the description should read RDU2, not RDU1. Will fix in v2,
tomorrow. Sorry about that.
Thanks,
Andrey Smirnov
> corresponding nodes to make them availible.
>
> Cc: Fabio Es
Pinctrl_usbh1reg defines pinmux setting for reset GPIO used by
usbh1phy, but is not referenced by that node. Fix that.
Cc: Fabio Estevam
Cc: Shawn Guo
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Andrey Smirnov
---
arch/arm/boot/dts/imx51-babbage.dts
There's already a USB PHY with reg of zero on that bus - usbphy0, used
by usbotg (included from imx51.dtsi). Move usbh1phy to @1 avoid
address collision.
Cc: Fabio Estevam
Cc: Shawn Guo
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Andrey Smirnov
---
Hi Thierry,
On 6/27/2018 3:01 PM, Thierry Escande wrote:
> Hi Sricharan,
>
> On 19/06/2018 15:45, Sricharan R wrote:
>> Sricharan R (2):
>> clk: qcom: Add safe switch hook for krait mux clocks
>> dt-bindings: cpufreq: Document operating-points-v2-krait-cpu
>>
>> Stephen Boyd (12):
>> ARM
ZII's RDU1s come with up to 3 EEPROMs attached to RAVE SP. Add
corresponding nodes to make them availible.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger
RAVE SP found on RDU2 implements backlight control compatible with the
rave-sp-backlight driver. Add a node to make it availible.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.
RAVE SP found on RDU2 implements power button control compatible with
the rave-sp-pwrbutton driver. Add a node to make it availible.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infrade
ZII's RDU1s come with two EEPROMs attached to RAVE SP. Add
corresponding nodes to make them availible.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.ker
Shawn:
These are patches adding the rest of RAVE SP child nodes covering all
the rest of currently supported MFD cells. There's more to be added,
once more drivers get accepted upstream.
The bindings three drivers mentioned are availible in:
Documentation/devicetree/bindings/nvmem/zii,rave-s
On Wed, 2018-06-27 at 18:13 -0700, Andrew Morton wrote:
> On Wed, 27 Jun 2018 18:05:35 -0700 Joe Perches wrote:
>
> > On Wed, 2018-06-27 at 22:48 +0300, Alexey Dobriyan wrote:
> > > I know I'll regret it.
> >
> > This wasn't applied back in February?
>
> Well I thought it was, but I can't find
Santosh,
On Friday 22 June 2018 03:46 PM, Kishon Vijay Abraham I wrote:
> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc
> binding.
>
> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP.
> Everyone who use a custom .config should also enable
> CONFIG_MMC_SDH
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> This switches away from userspace bitbanging to kernel FSI
> using the coprocessor.
>
> Signed-off-by: Benjamin Herrenschmidt
As with the other patch, I will take this through the ASPEED SoC tree
once we've got acks on the bindings.
Che
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> Signed-off-by: Benjamin Herrenschmidt
I will take this through the ASPEED SoC tree once we've got acks on
the bindings.
Cheers,
Joel
> ---
> arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 15 +--
> 1 file changed, 13 inser
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> The embedded struct device needs a release function to be
> able to successfully remove the driver.
>
> We remove the devm_gpiod_put() as they are unnecessary
> (the resources will be released automatically) and because
> fsi_master_unregis
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> This isn't per-se a real device, it's a pseudo-device that
> represents the use of the Aspeed built-in ColdFire to
> implement the FSI protocol by bitbanging the GPIOs instead
> of doing it from the ARM core.
>
> Thus it's a drop-in replace
On 27 June 2018 at 08:55, Benjamin Herrenschmidt
wrote:
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Joel Stanley
On 27 June 2018 at 08:55, Benjamin Herrenschmidt
wrote:
> Some definitions are generic to the FSI protocol or any
> give master implementation. Rename them to remove the
> "GPIO" prefix in preparation for moving them to a common
> header.
>
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Jo
On 27 June 2018 at 08:56, Benjamin Herrenschmidt
wrote:
> This moves the definitions for various protocol details
> (message & response codes, delays etc...) out of
> fsi-master-gpio.c to fsi-master.h in order to share them
> with other master implementations.
>
> Signed-off-by: Benjamin Herrensch
On 27 June 2018 at 08:55, Benjamin Herrenschmidt
wrote:
> This adds a few more tracepoints that have proven useful when
> debugging issues with the FSI bus.
>
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Joel Stanley
> ---
> drivers/fsi/fsi-master-gpio.c | 16 ---
> inclu
On 27 June 2018 at 08:53, Benjamin Herrenschmidt
wrote:
> Move fsi_slave_set_smode() and its helpers to before it's
> first user and remove the corresponding forward declaration.
>
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Joel Stanley
On 27 June 2018 at 08:55, Benjamin Herrenschmidt
wrote:
> To configure the send and echo delays
>
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Joel Stanley
On 27 June 2018 at 08:55, Benjamin Herrenschmidt
wrote:
> Those values control the amount of "dummy" clocks between commands and
> between a command and its response.
>
> This adds a way to configure them from sysfs (to be later extended to
> defaults in the device-tree). The default remains 16 (t
On 27 June 2018 at 08:53, Benjamin Herrenschmidt
wrote:
> What the driver called "FSI_GPIO_PRIME_SLAVE_CLOCKS" is what
> the FSI spec calls tSendDelay and should be 16 clocks by
> default.
>
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: Joel Stanley
> -Original Message-
> From: stable-ow...@vger.kernel.org On Behalf
> Of Ben Hutchings
[..]
> 3.18 and 4.4 are still missing this important fix to early parameter
> parsing:
>
> commit 02afeaae9843733a39cd9b11053748b2d1dc5ae7
> Author: Dave Hansen
> Date: Tue Dec 22 14:52:38 2015 -080
Hello Darrick,
Lockdep is reporting a deadlock with following trace. Saw this on my
powerpc vm with 4GB of ram, running Linus/master kernel. Though, I
don't have exact testcase to reproduce it. Is this something known?
[ 1797.620389] ==
[ 1797.
On 6/19/2018 2:06 PM, Can Guo wrote:
> All PHYs should be powered on before register configuration starts. And
> only PCIe PHYs need an extra power control before deasserts reset state.
>
> Signed-off-by: Can Guo
> ---
> drivers/phy/qualcomm/phy-qcom-qmp.c | 19 ---
> 1 file c
my machine, and 1.1 was, indeed, crap.
{o.o}
On 20180627 02:00, Michael Schmitz wrote:
Joanne,
I'm not at all allergic to avoiding RDB at all cost for new disks. If AmigaOS
4.1 supports more recent partition formats, all the better. This is all about
supporting use of legacy RDB disks o
On 6/19/2018 2:06 PM, Can Guo wrote:
> Move MSM8996 specific PHY vreg list struct name to a genernal one as it is
> used by all PHYs. Add a specific field to handle dual lane situation.
>
> Signed-off-by: Can Guo
> ---
> drivers/phy/qualcomm/phy-qcom-qmp.c | 25 ++---
> 1
Hi,
On 6/19/2018 2:06 PM, Can Guo wrote:
> +static int qcom_qmp_phy_poweron(struct phy *phy)
> +{
> + struct qmp_phy *qphy = phy_get_drvdata(phy);
> + struct qcom_qmp *qmp = qphy->qmp;
> + const struct qmp_phy_cfg *cfg = qmp->cfg;
> + void __iomem *pcs = qphy->pcs;
> + void __i
On Wed, Jun 20, 2018 at 04:38:37PM +0800, Anson Huang wrote:
> i.MX6SLL uses same SRC module as i.MX51, add "fsl,imx51-src"
> compatible string to enable SRC driver to support setting
> CPU resume address for cpu-idle and suspend/resume.
>
> Signed-off-by: Anson Huang
Applied, thanks.
> Signed-off-by: Baoquan He
>
> Signed-off-by: Baoquan He
Please remove duplicated signed-off
> if (!usemap) {
> ms->section_mem_map = 0;
> + nr_consumed_maps++;
Currently, we do not set ms->section_mem_map to 0 when fail to
allocat
Honestly, I do not like this new agrument, but it will do for now. I
could not think of a better way without rewriting everything.
Reviewed-by: Pavel Tatashin
However, I will submit a series of patches to cleanup sparse.c and
completely remove large and confusing temporary buffers: map_map, and
On Fri, Jun 22, 2018 at 04:49:49PM +0200, Sebastian Reichel wrote:
> Subject: Avoid firmware warning in imx-sdma
>
> Hi,
>
> I grabbed the first patch from patchwork from an 2017 patch series. As far as
> I
> could see, their usecase vanished due to switching to sync FW API (that
> already
> su
Once you remove the ms mentioned by Oscar:
Reviewed-by: Pavel Tatashin
On Wed, Jun 27, 2018 at 6:59 PM Baoquan He wrote:
>
> On 06/27/18 at 11:54am, Oscar Salvador wrote:
> > On Wed, Jun 27, 2018 at 09:31:14AM +0800, Baoquan He wrote:
> > > In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGE
Reviewed-by: Pavel Tatashin
On Tue, Jun 26, 2018 at 9:31 PM Baoquan He wrote:
>
> It's used to record how many memory sections are marked as present
> during system boot up, and will be used in the later patch.
>
> Signed-off-by: Baoquan He
> ---
> mm/sparse.c | 7 +++
> 1 file changed, 7 i
On Wed, 2018-06-27 at 20:04 +0300, Andy Shevchenko wrote:
> On Wed, Jun 27, 2018 at 7:59 PM, Andy Shevchenko
> wrote:
> > On Wed, Jun 27, 2018 at 8:43 AM, wrote:
> >> From: Sean Wang
> >>
> >
> >> +config BT_HCIBTUART_MTK
> >> + tristate "MediaTek HCI UART driver"
> >> + depends on
The issue is what happens when one of those disks appears on a 3.1 system.
{^_^}
On 20180627 01:03, Martin Steigerwald wrote:
Dear Joanne.
jdow - 27.06.18, 08:24:
You allergic to using a GPT solution? It will get away from some of
the evils that RDB has inherent in it because they are also
FFS is limited to 2 GHz file size if you don't want any corruption using
fseek(). Otherwise it can go to 4 GHz sort of safely.
{^_^}
On 20180627 00:57, Martin Steigerwald wrote:
Michael Schmitz - 27.06.18, 03:07:
Joanne,
As far as I have been able to test, the change is backwards compa
On Wed, 2018-06-27 at 19:59 +0300, Andy Shevchenko wrote:
> On Wed, Jun 27, 2018 at 8:43 AM, wrote:
> > From: Sean Wang
> >
>
> > +config BT_HCIBTUART_MTK
> > + tristate "MediaTek HCI UART driver"
> > + depends on BT_HCIBTUART
>
> > + default y
>
> Perhaps it's an overkill f
On (06/20/18 12:38), Linus Torvalds wrote:
> On Wed, Jun 20, 2018 at 11:50 AM Sergey Senozhatsky
> wrote:
> >
> > It's not UART on its own that immediately calls into printk(), that would
> > be trivial to fix, it's all those subsystems that serial console driver
> > can call into.
>
> We already
On 06/27/2018 10:02 AM, Jan Kara wrote:
> On Wed 27-06-18 08:57:18, Jason Gunthorpe wrote:
>> On Wed, Jun 27, 2018 at 02:42:55PM +0200, Jan Kara wrote:
>>> On Wed 27-06-18 13:59:27, Michal Hocko wrote:
On Wed 27-06-18 13:53:49, Jan Kara wrote:
> On Wed 27-06-18 13:32:21, Michal Hocko wrote
On (06/27/18 16:08), Petr Mladek wrote:
>
> kernel/printk/printk.c | 57 +++-
> kernel/printk/printk_safe.c | 58
> +
Shall we just merge these two?
-ss
The commit 4f1acd758b08 ("hwspinlock: Add devm_xxx() APIs to request/free
hwlock") introduces one bug, that will return one error pointer if failed
to request one hwlock, but we expect NULL pointer on error for consumers.
This patch will fix this issue.
Reported-by: Dan Carpenter
Signed-off-by: B
On Thu, Jun 28, 2018 at 01:40:30AM +, Gaoming (ming, consumer BG) wrote:
> Hi tytso,
>
> I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
> branch of /system/extras repository.
> e.g.
> https://android-review.googlesource.com/c/platform/system/extras/+/708003
Make_
On Mon, Jun 25, 2018 at 8:02 PM, Jernej Skrabec wrote:
> DW HDMI PHY driver and PHY clock driver share same registers. Make sure
> that DW HDMI PHY setup code doesn't change any clock related bits.
> During initialization, set PHY PLL parent bit to 0.
>
> Signed-off-by: Jernej Skrabec
Reviewed-b
On (06/27/18 16:20), Petr Mladek wrote:
> +/*
> + * Marks a code that might produce many messages in NMI context
> + * and the risk of losing them is more critical than eventual
> + * reordering.
> + *
> + * It has effect only when called in NMI context. Then printk()
> + * will try to store the me
On Mon, Jun 18, 2018 at 05:42:57PM +0200, Emmanuel Vadot wrote:
> The RIoTboard debug uart is connected to serial1.
> Add a chosen property in the DTS so OS knows what serial port to use for
> the console.
>
> Signed-off-by: Emmanuel Vadot
Applied, thanks.
On (06/28/18 11:16), Sergey Senozhatsky wrote:
>
> You can just call vprintk_emit(LOGLEVEL_SCHED) from vprintk_func(),
> then you don't need to factor out vprintk_deferred() and vprintk_emit().
> Any reason for that split?
My bad, no you can't. I forgot that for direct_nmi vprintk_func()
logbuf_l
On (06/27/18 16:08), Petr Mladek wrote:
> -int vprintk_deferred(const char *fmt, va_list args)
> +void defer_console(void)
> {
> - int r;
> -
> - r = vprintk_emit(0, LOGLEVEL_SCHED, NULL, 0, fmt, args);
> -
> preempt_disable();
> __this_cpu_or(printk_pending, PRINTK_PENDING_OUT
On Sat, 23 Jun 2018 22:12:51 +0800 ufo19890...@gmail.com wrote:
> From: yuzhoujian
>
> The current system wide oom report prints information about the victim
> and the allocation context and restrictions. It, however, doesn't
> provide any information about memory cgroup the victim belongs to. T
On (06/27/18 16:08), Petr Mladek wrote:
[..]
> if (dict)
> lflags |= LOG_PREFIX|LOG_NEWLINE;
>
> - printed_len = log_output(facility, level, lflags, dict, dictlen, text,
> text_len);
> + return log_output(facility, level, lflags,
> + dict, dictle
1 - 100 of 527 matches
Mail list logo
