This patch is first version of Mediatek Command Queue(CMDQ) driver. The
CMDQ is used to help write registers with critical time limitation,
such as updating display configuration during the vblank. It controls
Global Command Engine (GCE) hardware to achieve this requirement.
Currently, CMDQ only
Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
Signed-off-by: Houlong Wei
Signed-off-by: HS Liao
---
drivers/soc/mediatek/Kconfig | 12 ++
drivers/soc/mediatek/Makefile |1 +
drivers/soc/mediatek/mtk-cmdq-helper.c | 258
This patch adds the device node of the GCE hardware for CMDQ module.
Signed-off-by: Houlong Wei
Signed-off-by: HS Liao
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
This adds documentation for the MediaTek Global Command Engine (GCE) unit
found in MT8173 SoCs.
Signed-off-by: Houlong Wei
Signed-off-by: HS Liao
---
Hi Rob,
I don't add your ACK in this version since the dt-binding description
has been changed. Thanks.
---
Hi,
This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used
to help write registers with critical time limitation, such as
updating display configuration during the vblank. It controls Global
Command Engine (GCE) hardware to achieve this requirement.
Changes since v21:
-rebase on
Mein Liebster
Wie geht es Ihnen heute? Ich hoffe, dass es dir und deiner Familie gut
geht zum Ruhm des allmächtigen Gottes. Mein Name ist Beatrice Morgan
Ich bin 52 Jahre alt. Ich war mit dem verstorbenen Mr. James Morgan
verheiratet, der 11 Jahre lang in der Botschaft der Vereinigten
Staaten in
On Friday 01 June 2018 01:55 AM, David Lechner wrote:
> This enables Bluetooth modules in davinic_all_defconfig needed for LEGO
davinci_all_defconfig
> MINDSTORMS EV3.
>
> Signed-off-by: David Lechner
> ---
> arch/arm/configs/davinci_all_defconfig | 9 +
> 1 file changed, 9
Hi Suzuki, Jun,
On 27/06/18 12:07, Suzuki K Poulose wrote:
> On 25/06/18 12:39, Jun Yao wrote:
>> When CONFIG_ARM64_VA_BITS_36/CONFIG_ARM64_VA_BITS_39/
>> CONFIG_ARM64_VA_BITS_42 are selected, a block-mapping can be
>> written to swapper_pg_dir. To defend 'KSMA', we move swapper_pg_dir
>> to
Hi,
On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> >
> > Hi,
> > I am wondering why do we still keep mm/bootmem.c when most architectures
> > already moved to nobootmem. Is there any fundamental reason why others
> > cannot or
On Tuesday 26 June 2018 04:32 AM, David Lechner wrote:
> On 06/25/2018 11:04 AM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> The way this function is implemented caused some confusion when
>> converting the TI DaVinci platform to using the common clock framework.
>>
>> Current
On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
wrote:
> Is there a way for a user process to mark memory as 'sensitive' or
> 'non-sensitive' when it is allocated? That could allow it not to have to be
> zeroed before being allocated to another process.
Isn't this what we have Meltdown
The patch
ASoC: simple-amplifer: add simple-amplifier compatible
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: simple-amplifier: remame dio2125 documentation
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
ASoC: tas517x: add tas5707 support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: tas571x: add tas5707 compatible
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
On Tue, Jun 26, 2018 at 06:16:04PM +0200, Anna-Maria Gleixner wrote:
> Hi,
>
> during rcu torture tests (TREE04 and TREE07) I noticed, that a
> WARN_ON_ONCE() in sched core triggers on a recent 4.18-rc2 based
> kernel (6f0d349d922b ("Merge
>
On Tue 26-06-18 18:48:25, Jan Kara wrote:
> On Tue 26-06-18 15:47:57, Michal Hocko wrote:
> > On Mon 18-06-18 12:21:46, Dan Williams wrote:
> > [...]
> > > I do think we should explore a page flag for pages that are "long
> > > term" pinned. Michal asked for something along these lines at LSF / MM
On Tue, 2018-02-06 at 10:52 +0800, CK Hu wrote:
> Hi, Houlong:
>
> I've some inline comment.
>
> On Wed, 2018-01-31 at 15:28 +0800, houlong@mediatek.com wrote:
> > From: "hs.l...@mediatek.com"
> >
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >
> >
Some users of static UBI volumes implement their own integrity check, thus
making the volume CRC check done at open time useless. For instance, this
is the case when one use the ubiblock + dm-verity + squashfs combination,
where dm-verity already checks integrity of the block device but this time
Some users of static UBI volumes implement their own integrity check,
thus making the volume CRC check done at open time useless. For
instance, this is the case when one use the ubiblock + dm-verity +
squashfs combination, where dm-verity already checks integrity of the
block device but this time
Now that we have the logic for skipping CRC check for static UBI volumes
in the core, let's expose it to users.
This makes use of a padding byte in the volume description data
structure as a flag. This flag only tell for now whether we should skip
the CRC check of a volume.
This checks the UBI
On Wed, 2018-06-27 at 12:40 +0300, Sakari Ailus wrote:
> On Wed, Jun 27, 2018 at 10:19:38AM +0200, Bartosz Golaszewski wrote:
> > 2018-06-27 7:46 GMT+02:00 :
> > > From: Alan Chiang
> > >
> > > The AT24 series chips use 8-bit address by default. If some
> > > chips would like to support more
On Wed, 2018-02-21 at 16:05 +0800, CK Hu wrote:
> Hi, Houlong:
>
> I've one more inline comment.
>
> On Wed, 2018-01-31 at 15:28 +0800, houlong@mediatek.com wrote:
> > From: "hs.l...@mediatek.com"
> >
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >
> >
On Wed, 27 Jun 2018 13:33:19 +0200
Quentin Schulz wrote:
> Some users of static UBI volumes implement their own integrity check,
> thus making the volume CRC check done at open time useless. For
> instance, this is the case when one use the ubiblock + dm-verity +
> squashfs combination, where
On Wed, 27 Jun 2018 13:33:20 +0200
Quentin Schulz wrote:
> Now that we have the logic for skipping CRC check for static UBI volumes
> in the core, let's expose it to users.
>
> This makes use of a padding byte in the volume description data
> structure as a flag. This flag only tell for now
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.com wrote:
> > From: "hs.l...@mediatek.com"
> >
> > This patch is first version of Mediatek Command Queue(CMDQ) driver. The
> > CMDQ is used
On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> On Tue 26-06-18 18:48:25, Jan Kara wrote:
> > On Tue 26-06-18 15:47:57, Michal Hocko wrote:
> > > On Mon 18-06-18 12:21:46, Dan Williams wrote:
> > > [...]
> > > > I do think we should explore a page flag for pages that are "long
> > > > term"
The .gpio_set_direction() callback was setting inverted direction
for SoCs older than the JZ4770, this restores the correct behaviour.
Signed-off-by: Paul Cercueil
---
drivers/pinctrl/pinctrl-ingenic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Linus,
Here's a set of (rather RFC) patches, to implement
pinctrl_gpio_get_direction(). I did that, because my gpio-ingenic driver
calls pinctrl_gpio_set_direction() within its gpio_chip's .set_direction
callback, but there was no corresponding function to implement the
.get_direction
Right now there is a core function to set the direction (input or output)
of a GPIO, pinmux_gpio_set_direction(). This function is provided to the
consumers with two wrappers, pinctrl_gpio_direction_input() /
pinctrl_gpio_direction_output(). Typically, these functions are used
within GPIO drivers,
This function can be used to retrieve the direction (input/output) of a
given GPIO.
It should *ONLY* be used from gpiolib-based GPIO drivers, as part of their
gpio_get_direction() semantics, platforms and individual drivers shall
*NOT* touch pin control GPIO calls.
Signed-off-by: Paul Cercueil
This will allow the GPIO driver to use the previously introduced
pinctrl_gpio_get_direction function to implement its .get_direction
callback.
Signed-off-by: Paul Cercueil
---
drivers/pinctrl/pinctrl-ingenic.c | 13 +
1 file changed, 13 insertions(+)
diff --git
Use the newly introduced pinctrl_gpio_get_direction to implement the
.get_direction callback.
Signed-off-by: Paul Cercueil
---
drivers/gpio/gpio-ingenic.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpio/gpio-ingenic.c b/drivers/gpio/gpio-ingenic.c
index
On Wed 27-06-18 13:53:49, Jan Kara wrote:
> On Wed 27-06-18 13:32:21, Michal Hocko wrote:
[...]
> > Appart from that, do we really care about 32b here? Big DIO, IB users
> > seem to be 64b only AFAIU.
>
> IMO it is a bad habit to leave unpriviledged-user-triggerable oops in the
> kernel even for
On Tue, Jun 19, 2018 at 10:09:05AM +0200, Michal Simek wrote:
> On 6.6.2018 14:41, Michal Simek wrote:
> > Writing zero and NULLs to already initialized fields is not needed.
> > Remove this additional writes.
> >
> > Signed-off-by: Michal Simek
> > ---
> >
> > Changes in v2:
> > - new patch -
Enabling HARDENED_USER_COPY causes measurable regressions in
networking performance, up to 8% under UDP flood.
I'm running an a small packet UDP flood using pktgen vs. a host b2b
connected. On the receiver side the UDP packets are processed by a
simple user space process that just reads and
The c6x is already using memblock and does most of early memory
reservations with it, so it was only a matter of removing the bootmem
initialization and handover of the memory from memblock to bootmem.
Signed-off-by: Mike Rapoport
---
arch/c6x/Kconfig| 1 +
arch/c6x/kernel/setup.c | 26
On Tuesday 05 June 2018 03:37 PM, Keerthy wrote:
> The intc #interrupt-cells is equal to 1. Currently gpio
> node has 2 cells per IRQ which is wrong. Remove the additional
> cell for each of the interrupts.
>
> Signed-off-by: Keerthy
> Fixes: 2e38b946dc54 ("ARM: davinci: da850: add GPIO DT
The UDC clock of the JZ4740 SoC can be gated, but the data structure
representing it was missing the CGU_CLK_GATE flag to make it work.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/jz4740-cgu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The register field for configuring the divider for the i2s clock
occupies the bits [8-0], which means 9 bits and not 8.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/jz4740-cgu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/ingenic/jz4740-cgu.c
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:
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:
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
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:
>
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
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:
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:
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:
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
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
---
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
> >
On Tue, Jun 26, 2018 at 09:57:07AM +0100, David Howells wrote:
> Andrei Vagin wrote:
>
> > > > > - mnt = kern_mount_data(_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?
> > ...
> > -
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
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
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
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
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
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.
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:
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
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
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
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
---
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
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
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
>
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
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
>
> -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
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 ---
>
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: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
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
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
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):
>>
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;
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
> >>
. 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 supports more recent partition formats, all the better.
T
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
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
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
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
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 +-
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,
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
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
> > >
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:
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,
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()
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/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
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
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
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:
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
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
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
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
401 - 500 of 1028 matches
Mail list logo
