From: Colin Ian King
Array iw_operation_mode is defined but is never used hence it is
redundant and can be removed. This array has been like this since
the driver was added back in 2010
Cleans up clang warning:
warning: 'iw_operation_mode' defined but not used [-Wunused-const-variable=]
Signed-
Stanislaw Gruszka writes:
> On Wed, Aug 08, 2018 at 08:41:28AM -0700, Kees Cook wrote:
>> >> I thought SPDX line is needed only if file has no license and eeprom.c
>> >> file and other mt76x0 files have specified the license. Is SPDX still
>> >> needed in that case ?
>>
>> I thought all source f
On Thu, Aug 09, 2018 at 01:47:27PM +0800, Leo Yan wrote:
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index 1a3e9bd..802286e 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -190,10 +190,18 @@ static void cpuidle_idle_call(void)
>*/
> n
From: Colin Ian King
Array cm_mappable_regions is defined but is never used hence it is
redundant and can be removed.
Cleans up clang warning:
warning: 'cm_mappable_regions' defined but not used [-Wunused-const-variable=]
Signed-off-by: Colin Ian King
---
drivers/staging/gasket/apex_driver.c
On 2018/08/09 18:21, Kirill Tkhai wrote:
> 2)SRCU. Pros are there are no the above problems; we will have completely
> unlocked and
> scalable shrink_slab(). We will also have a possibility to avoid
> unregistering delays,
> like I did for superblock shrinker. There will be full scalability.
Add driver for the Cadence SD0801 "Torrent" PHY used with the Cadence MHDP
DisplayPort Tx controller.
Integration with the MHDP driver will be the subject of another commit.
Signed-off-by: Scott Telford
---
drivers/phy/Kconfig | 1 +
drivers/phy/Makefile | 1
These patches add preliminary support for the Cadence "Torrent" SD0801
PHY used with the Cadence MHDP DisplayPort Tx controller.
Integration with the MHDP driver will be the subject of another commit.
v4:
* Comment formatting
* Describe "num_lanes" and "max_bit_rate" properties as optional in
d
Hi,
On Friday 03 August 2018 03:24 PM, Kunihiko Hayashi wrote:
> Add a driver for PHY interface built into USB3 controller
> implemented in UniPhier SoCs.
> This driver supports High-Speed PHY and Super-Speed PHY.
>
> Signed-off-by: Kunihiko Hayashi
> Signed-off-by: Motoya Tanigawa
> Signed-off
Signed-off-by: Scott Telford
---
.../devicetree/bindings/phy/phy-cadence-dp.txt | 30 ++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-dp.txt
diff --git a/Documentation/devicetree/bindings/phy/phy-cadence-dp.txt
b/
On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
> On Wed, Aug 08 2018 at 04:56 -0600, Lorenzo Pieralisi wrote:
> >On Mon, Aug 06, 2018 at 11:37:55AM +0200, Rafael J. Wysocki wrote:
> >>On Fri, Aug 3, 2018 at 1:42 PM, Ulf Hansson wrote:
> >>> [...]
> >>>
> >
> > Assuming that I h
On 09.08.2018 00:31, Dave Chinner wrote:
> On Wed, Aug 08, 2018 at 12:27:34PM +0200, Michal Hocko wrote:
>> [CC Josh - the whole series is
>> http://lkml.kernel.org/r/153365347929.19074.12509495712735843805.stgit@localhost.localdomain]
>>
>> On Wed 08-08-18 13:17:44, Kirill Tkhai wrote:
>>> On 08.0
On 08/08/18 17:57, Christoph Hellwig wrote:
> On Wed, Aug 08, 2018 at 05:47:40PM +0100, Marc Zyngier wrote:
>> The original GIC driver deals with 2.5 revisions of the architecture
>> (yes, there was something pre-GICv1...), and implementers have been
>> creative to the extreme. Still, we could have
The patch
regmap: Add regmap_noinc_read API
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.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 du
The patch
ASoC: da7219: Add delays to capture path to remove DC offset noise
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
On Tue, Aug 07, 2018 at 05:52:17PM +0300, Stefan Popa wrote:
> From: Crestez Dan Leonard
>
> The regmap API usually assumes that bulk read operations will read a
> range of registers but some I2C/SPI devices have certain registers for
The following changes since commit ce397d215ccd07b8ae3f71db68
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1
> fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for
> that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to describe
>
On Wed, 8 Aug 2018 10:44:18 -0400
Tony Krowiak wrote:
> diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> b/drivers/s390/crypto/vfio_ap_drv.c
> new file mode 100644
> index 000..d7e39ad
> --- /dev/null
> +++ b/drivers/s390/crypto/vfio_ap_drv.c
> @@ -0,0 +1,115 @@
> +// SPDX-License-Identifie
On some i.MX SoCs' low power mode, UART iomux settings
may be lost, need to add pinctrl sleep/default mode switch
during suspend/resume to make sure UART iomux settings are
correct after resume.
Signed-off-by: Anson Huang
---
drivers/tty/serial/imx.c | 5 +
1 file changed, 5 insertions(+)
d
In noirq suspend/resume stage with no_console_suspend enabled,
.imx_console_write() may be called to print out log_buf
message by .printk(), so there will be race condition between
.imx_console_write() and .serial_imx_save/restore_context(),
need to add lock to protect the registers save/restore op
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Now that we init the status field to ACPI_STA_DEFAULT rather then to
> 0,
> the workaround for acpi_match_device_ids() always returning -ENOENT
> when
> status is 0 is no longer needed.
>
Always good to have only "minus" statistics
Review
On Thu, 2018-08-09 at 11:15 +0200, Hans de Goede wrote:
> Some devices have multiple I2cSerialBus resources and for things to
> work
> an i2c-client must be instantiated for each, each with its own
> i2c_device_id.
>
> Normally we only instantiate an i2c-client for the first resource,
> using
> th
> As for the rest of the series I'll wait from comments from Wolfram and
> the other reviewers.
Well, I acked patch 4 now because I like the general approach. I can't
say much about the rest since this is mostly ACPI/FW related.
Thanks Hans, for keeping at it.
signature.asc
Description: PGP s
On Thu, Aug 9, 2018 at 11:58 AM, Hans de Goede wrote:
> Hi,
>
> On 09-08-18 11:51, Andy Shevchenko wrote:
>>
>> On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede
>> wrote:
>>>
>>> On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
>>
>>
On Thu, Aug 09, 2018 at 11:15:58AM +0200, Hans de Goede wrote:
> On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
> per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
> i2c-device.
>
> But in some rare cases the manufacturer has decided to describ
On Wed, Aug 08, 2018 at 12:02:48PM -0600, Lina Iyer wrote:
[...]
> I will not speak to any comparison of benchmarks between OSI and PC.
> AFAIK, there are no platforms supporting both.
>
That's the fundamental issue here. So we have never ever done a proper
comparison.
> But, the OSI feature is
Hi,
On 09-08-18 11:51, Andy Shevchenko wrote:
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
wrote:
I've applied the v4 of this patch and I don't think there are any
changes from it here.
From: Al Viro
smack ->d_instantiate() uses ->setxattr(), so to be able to call it before
we'd hashed the new dentry and attached it to inode, we need ->setxattr()
instances getting the inode as an explicit argument rather than obtaining
it from dentry.
Similar change for ->getxattr() had been do
From: Al Viro
commit ce23e640133484eebc20ca7b7668388213e11327 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
Documentation/filesystems/porting |6 +
.../staging/lustre/lustre/llite/llite_internal.h |4 +-
driver
From: Al Viro
commit b296821a7c42fa58baa17513b2b7b30ae66f3336 upstream.
... and do not assume they are already attached to each other
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 ---
fs/9p/xatt
From: Al Viro
preparation for similar switch in ->setxattr() (see the next commit for
rationale).
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18 including ext3]
Signed-off-by: Seung-Woo Kim
---
fs/9p/acl.c |7 +++
fs/9p/xattr_security.c |5 +++--
fs/9
From: Al Viro
commit b96809173e94ea2fa8c19c2e40e8545a1821bf57 upstream.
Signed-off-by: Al Viro
[sw0312.kim: backport to 3.18]
Signed-off-by: Seung-Woo Kim
---
fs/dcache.c | 18 +++---
1 files changed, 7 insertions(+), 11 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
inde
On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede wrote:
> On 09-08-18 11:35, Rafael J. Wysocki wrote:
>> On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede
>> wrote:
>> I've applied the v4 of this patch and I don't think there are any
>> changes from it here.
>
>
> Correct, there were only changes to
On 09/08/18 10:14, Patrick Bellasi wrote:
> On 07-Aug 14:35, Juri Lelli wrote:
> > On 06/08/18 17:39, Patrick Bellasi wrote:
> >
> > [...]
> >
> > > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > > *p,
> > > return retval;
> > > }
> > >
> > >
On some platforms it has been noted that a pop noise can be
witnessed when capturing audio, mainly for first time after a
headset jack has been inserted. This is due to a DC offset in the
Mic PGA and so to avoid this delays are required when powering
up the capture path.
This commit rectifies the
This new symbol needs to be in the workaround-list for buggy
binutils, otherwise the build with gcc-4.6 fails.
Fixes: 39d668e04eda ('x86/mm/pti: Make pti_clone_kernel_text() compile on 32
bit')
Signed-off-by: Joerg Roedel
---
arch/x86/tools/relocs.c | 1 +
1 file changed, 1 insertion(+)
diff -
On Wed, Aug 08, 2018 at 02:18:18PM -0700, skan...@codeaurora.org wrote:
> On 2018-08-08 01:47, Sudeep Holla wrote:
> >On Tue, Aug 07, 2018 at 12:37:07PM -0700, skan...@codeaurora.org wrote:
> >>On 2018-08-07 09:41, Rob Herring wrote:
> >>>On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan wr
Hi Stephen,
On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote:
> Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned
> /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target
> 'arch/x86/boot/compressed/vmlinux.relocs' failed
>
> Caused by commit
>
> 39d
Hi,
On 09-08-18 11:35, Rafael J. Wysocki wrote:
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status() and
On Thursday 09 Aug 2018 at 11:30:57 (+0200), Vincent Guittot wrote:
> On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
> >
> > From: Morten Rasmussen
> >
> > Energy-aware scheduling is only meant to be active while the system is
> > _not_ over-utilized. That is, there are spare cycles availabl
On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede wrote:
> Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
> initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
> gets set to 0 by acpi_bus_type_and_status() and filled with its actual
> value later when acp
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность В
On Wed, Aug 08, 2018 at 02:22:13PM -0500, Gustavo A. R. Silva wrote:
> @@ -518,7 +518,8 @@ static int adau1761_setup_digmic_jackdetect(struct
> snd_soc_component *component)
> ARRAY_SIZE(adau1761_jack_detect_controls));
> if (ret)
> return
On Tue, 24 Jul 2018 at 14:26, Quentin Perret wrote:
>
> From: Morten Rasmussen
>
> Energy-aware scheduling is only meant to be active while the system is
> _not_ over-utilized. That is, there are spare cycles available to shift
> tasks around based on their actual utilization to get a more
> ener
On Wed, Aug 08, 2018 at 02:19:33PM -0500, Gustavo A. R. Silva wrote:
> @@ -648,6 +648,7 @@ static int adav80x_set_pll(struct snd_soc_component
> *component, int pll_id,
> pll_ctrl1 |= ADAV80X_PLL_CTRL1_PLLDIV;
> break;
> }
> +
On Wed, 2018-08-08 at 22:22 +0200, Wolfram Sang wrote:
> On Mon, Aug 06, 2018 at 08:54:07PM +0200, Alexandre Belloni wrote:
> > Switch to device_get_match_data in probe to match the device
> > specific data
> > instead of using the acpi specific function.
> >
> > Suggested-by: Andy Shevchenko
> >
[dropping everyone else while we discuss the code]
Thanks. I assume that branch as all the code that there is. Let me
look and get back to you.
On Thu, Aug 9, 2018 at 2:19 PM, Mikko Perttunen wrote:
> Here's my current code:
>
> https://github.com/cyndis/linux/commits/wip/t194-tcu-4
>
> "fixup!
Hi,
> I believe the reason for these api is because some arch changed to can
> not do DMA on stack recently. Maybe we should have dma_mapping to bounce
It is not only arch dependent. You can enable virtual stacks in Kconfig,
too.
> buffer like it bounce un-dma-able address for those arch? or we
On 09.08.2018 10:14, Michal Hocko wrote:
> On Wed 08-08-18 16:20:54, Kirill Tkhai wrote:
>> [Added two more places needed srcu_dereference(). All ->shrinker_map
>> dereferences must be under SRCU, and this v2 adds missed in previous]
>>
>> The patch makes shrinker list and shrinker_idr SRCU-safe
>
On 09.08.2018 11:06, Cornelia Huck wrote:
> On Wed, 8 Aug 2018 10:44:14 -0400
> Tony Krowiak wrote:
>
>> From: Harald Freudenberger
>>
>> Move all the inline functions from the ap bus header
>> file ap_asm.h into the in-kernel api header file
>> arch/s390/include/asm/ap.h so that KVM can make us
Some devices have multiple I2cSerialBus resources and for things to work
an i2c-client must be instantiated for each, each with its own
i2c_device_id.
Normally we only instantiate an i2c-client for the first resource, using
the ACPI HID as id.
This commit adds a list of HIDs of devices, which nee
Since commit 63347db0affa ("ACPI / scan: Use acpi_bus_get_status() to
initialize ACPI_TYPE_DEVICE devs") the status field of normal acpi_devices
gets set to 0 by acpi_bus_type_and_status() and filled with its actual
value later when acpi_add_single_object() calls acpi_bus_get_status().
This means
On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
i2c-device.
But in some rare cases the manufacturer has decided to describe multiple
i2c-devices in a single ACPI fwnode with multiple I2cSerialBus
Now that we init the status field to ACPI_STA_DEFAULT rather then to 0,
the workaround for acpi_match_device_ids() always returning -ENOENT when
status is 0 is no longer needed.
Signed-off-by: Hans de Goede
---
Changes in v3:
-New patch in v3 of this patch-set
---
drivers/acpi/x86/utils.c | 10 -
On Wed, Aug 08, 2018 at 10:24:13AM -0700, Stephen Boyd wrote:
> Now that the /firmware/coreboot node in DT is populated by the core DT
> platform code with commit 3aa0582fdb82 ("of: platform: populate
> /firmware/ node from of_platform_default_populate_init()") we should and
> can remove the platfo
Hi,
On 08-08-18 19:00, Wolfram Sang wrote:
$subject still says "i2c:"
Ah, good point I will send a v5 with this fixed, I will also
do s/no_clients/num_clients/ for v5 as Andy requested.
Regards,
Hans
Hi All,
Here is v5 of my patch-series for dealing with multiple independent i2c
devices being described in a single ACPI fwnode.
Changes in v5:
-s/no_clients/num_clients/
-Change patch 4 Subject prefix to platform/x86
Changes in v4:
-Rewrite commit message of first patch as this is NOT a bug fix
On 07-Aug 14:35, Juri Lelli wrote:
> On 06/08/18 17:39, Patrick Bellasi wrote:
>
> [...]
>
> > @@ -4218,6 +4245,13 @@ static int __sched_setscheduler(struct task_struct
> > *p,
> > return retval;
> > }
> >
> > + /* Configure utilization clamps for the task */
> > +
On Wed, 2018-08-08 at 22:57 +0200, Wolfram Sang wrote:
> On Sat, Jul 07, 2018 at 05:29:54PM +0800, Jun Gao wrote:
> > From: Jun Gao
> >
> > This function is needed by i2c_get_dma_safe_msg_buf() potentially.
> > It is used to free DMA safe buffer when DMA operation fails.
> >
> > Signed-off-by: J
On Wed, 8 Aug 2018 10:44:14 -0400
Tony Krowiak wrote:
> From: Harald Freudenberger
>
> Move all the inline functions from the ap bus header
> file ap_asm.h into the in-kernel api header file
> arch/s390/include/asm/ap.h so that KVM can make use
> of all the low level AP functions.
>
> Signed-
When compiling bmips with SMP disabled, the build fails with:
drivers/irqchip/irq-bcm7038-l1.o: In function `bcm7038_l1_cpu_offline':
drivers/irqchip/irq-bcm7038-l1.c:242: undefined reference to
`irq_set_affinity_locked'
make[5]: *** [vmlinux] Error 1
Fix this by adding and setting bcm7038_l1_cp
On 09/08/2018 10:10, David Hildenbrand wrote:
On 08.08.2018 16:44, Tony Krowiak wrote:
From: Pierre Morel
When we clear the Crypto Control Block (CRYCB) used by a guest
level 2, the vSIE shadow CRYCB for guest level 3 must be updated
before the guest uses it.
We achieve this by using the KVM_
In SLUB, prefetch_freepointer() is used when allocating an object from cache's
freelist, to make sure the next object in the list is cache-hot, since it's
probable it will be allocated soon.
Commit 2482ddec670f ("mm: add SLUB free list pointer obfuscation") has
unintentionally changed the prefetch
On 09/08/2018 10:10, David Hildenbrand wrote:
On 08.08.2018 16:44, Tony Krowiak wrote:
From: Pierre Morel
When we clear the Crypto Control Block (CRYCB) used by a guest
level 2, the vSIE shadow CRYCB for guest level 3 must be updated
before the guest uses it.
We achieve this by using the KVM_
Hi Evan,
On 8/6/2018 10:56 PM, Evan Green wrote:
Hi Sayali,
On Wed, Aug 1, 2018 at 1:49 AM Sayali Lokhande wrote:
From: Subhash Jadavani
UFS host supplies the reference clock to UFS device and UFS device
specification allows host to provide one of the 4 frequencies (19.2 MHz,
26 MHz, 38.4 M
Here's my current code:
https://github.com/cyndis/linux/commits/wip/t194-tcu-4
"fixup! mailbox: tegra-hsp: Add support for shared mailboxes" splits up
the controller into two. "tegra-hsp: use polling" changes it to use polling.
There are two lines in the top patch with comments:
- at the end
Hi !
On 07/08/2018 15:00, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> When mode is set in atmel_config_iso7816() we backup last RS232 mode
> for coming back to this mode if requested.
> Also allow setup of T=0 and T=1 parameter and basic support in set_termios
> function as well.
>
> Sig
On Wed, Aug 08, 2018 at 03:14:19PM -0700, Joe Perches wrote:
> On Wed, 2018-08-08 at 22:00 +0100, John Whitmore wrote:
> > The macro eqMacAddr implements the same functionality as the
> > ether_addr_equal function defined in etherdevice.h, as a result the
> > macro has been removed from the code, a
On 06-Aug 09:50, Randy Dunlap wrote:
> Hi,
Hi Randy,
> On 08/06/2018 09:39 AM, Patrick Bellasi wrote:
> > diff --git a/init/Kconfig b/init/Kconfig
> > index 041f3a022122..1d45a6877d6f 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -583,6 +583,25 @@ config HAVE_UNSTABLE_SCHED_CLOCK
>
From: He Zhe
The check may fail not only because ${CC} does not support the asm
feature, but also due to potential defects of ${CC} itself like what
we experienced below or even it's missing.
Assembler messages:
Fatal error: The input and output files must be distinct
(introduced by binutils-2.3
On 09.08.2018 10:17, David Hildenbrand wrote:
> On 08.08.2018 16:44, Tony Krowiak wrote:
>> From: Tony Krowiak
>>
>> Introduces a new CPU model feature and two CPU model
>> facilities to support AP virtualization for KVM guests.
>>
>> CPU model feature:
>>
>> The KVM_S390_VM_CPU_FEAT_AP feature in
Bjorn Helgaas writes:
> On Wed, Aug 08, 2018 at 03:44:03PM +0100, Punit Agrawal wrote:
>> Bjorn Helgaas writes:
>> > On Thu, Aug 2, 2018 at 9:33 AM Lorenzo Pieralisi
>> > wrote:
>> >> On Wed, Aug 01, 2018 at 02:38:51PM -0500, Jeremy Linton wrote:
>> >>
>> >> Jiang Liu does not work on the kerne
On Thu, Aug 9, 2018 at 9:31 AM, 刘硕然 wrote:
> Thank you for the prompt reply.
>
> I tried this config, but still can get balance_dirty_pages triggered.
I think it may be due to BDI_CAP_STRICTLIMIT used by fuse. If you
remove that setting from fuse in the kernel you should not be getting
the balan
On 08.08.2018 16:44, Tony Krowiak wrote:
> From: Tony Krowiak
>
> This patch refactors the code that initializes and sets up the
> crypto configuration for a guest. The following changes are
> implemented via this patch:
>
> 1. Prior to the introduction of AP device virtualization, it
>was n
On Wed 08-08-18 12:58:15, Jerome Glisse wrote:
> On Wed, Aug 08, 2018 at 08:47:58AM +0200, Michal Hocko wrote:
> > On Tue 07-08-18 11:18:10, Jerome Glisse wrote:
> > > On Tue, Aug 07, 2018 at 04:59:00PM +0200, Michal Hocko wrote:
> > > > On Tue 07-08-18 09:52:21, Jerome Glisse wrote:
> > > > > On T
From: Jianxin
This attempt will try to add new DT files to support Meson-G12A SoC.
1) first, Please notice that, in this patch series, the DT node about 16M
reserved
memory for hwrom is removed, since it's not needed by G12A SoC.
2) second, the pclk for uart_AO need to be fixed once G12A clock_
* Pavel Machek [180808 21:35]:
> On Wed 2018-08-08 02:05:12, Tony Lindgren wrote:
> > Then for deeper idle modes, you need to also idle UARTs, and unbind or
> > unload USB related modules. You should get to something like 160mW
> > power consumption with mdm6600 enabled and SoC suspended that way.
v3: Added missed #ifdef CONFIG_MEMCG_KMEM around idr_replace()
v2: Improved comments to SHRINKER_REGISTERING and written
long description about all the things to the patch.
The patch introduces a special value SHRINKER_REGISTERING
to use instead of list_empty() to differ a registering
shrinke
Introduce new bindings for the Meson G12A SoC
Signed-off-by: Jianxin Pan
---
Documentation/devicetree/bindings/arm/amlogic.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
b/Documentation/devicetree/bindings/arm/amlogic.txt
index b5
Try to add basic DT support for the Amlogic's Meson-G12A S905D2 SoC,
which describe components as follows: Reserve Memory, CPU, GIC, IRQ,
Timer, UART. It's capable of booting up into the serial console.
Signed-off-by: Jianxin
---
arch/arm64/boot/dts/amlogic/Makefile| 1 +
arch/arm6
On 08/09/2018 10:16 AM, Murphy Zhou wrote:
Hi,
Looks like this missed v4.18 ?
Hi Murphy,
yes, Jeff planned to push those patches into 4.19 and they are in "linux-next"
now,
but not in 4.18 "master" currently.
On 06/14/2018 01:41 PM, Jeff Layton wrote:
> These look fine to me. I'll plan to p
On 08.08.2018 16:44, Tony Krowiak wrote:
> From: Tony Krowiak
>
> Introduces a new CPU model feature and two CPU model
> facilities to support AP virtualization for KVM guests.
>
> CPU model feature:
>
> The KVM_S390_VM_CPU_FEAT_AP feature indicates that
> AP instructions are available on the g
On Wed, Aug 8, 2018 at 8:02 PM, Lina Iyer wrote:
> On Wed, Aug 08 2018 at 04:56 -0600, Lorenzo Pieralisi wrote:
>>
>> On Mon, Aug 06, 2018 at 11:37:55AM +0200, Rafael J. Wysocki wrote:
>>>
>>> On Fri, Aug 3, 2018 at 1:42 PM, Ulf Hansson
>>> wrote:
>>> > [...]
>>> >
>>> >>>
>>> >>> Assuming that I
On Wed, Aug 08, 2018 at 11:55:48AM -0400, Steven Rostedt wrote:
> Having libtraceevent turn into a proper library has long been asked for.
> I never had time to do it before. Luckily, Tzvetomir was able to spend
> the time to start the preparation. The first thing that needs to be done
> is to hand
On 08.08.2018 16:44, Tony Krowiak wrote:
> From: Pierre Morel
>
> When we clear the Crypto Control Block (CRYCB) used by a guest
> level 2, the vSIE shadow CRYCB for guest level 3 must be updated
> before the guest uses it.
>
> We achieve this by using the KVM_REQ_VSIE_RESTART synchronous
> requ
On Wed, Aug 08, 2018 at 03:33:20PM -0700, Stephane Eranian wrote:
> This patch fixes a bug in ordered_event.c:alloc_event().
> An ordered_event struct was not initialized properly potentially
> causing crashes later on in free_dup_event() depending on the
> content of the memory. If it was NULL, th
Hi all,
Changes since 20180808:
The vfs tree still had its build failure but today I applied a suggested
patch and I have still disabled CONFIG_SAMPLE_STATX.
Non-merge commits (relative to Linus' tree): 11533
10452 files changed, 491910 insertions(+), 204122 deletions(-)
--
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have synchronous VCPU
requests that will also be handled before running the vSIE again.
So let's simulate a SIE entry of the VCPU when calling the sie during
vSIE handling and
When we change the crycb (or execution controls), we also have to make sure
that the vSIE shadow datastructures properly consider the changed
values before rerunning the vSIE. We can achieve that by simply using a
VCPU request now.
This has to be a synchronous request (== handled before entering t
While discussing AP changes, we discovered that we will have to force
a CPU using the vSIE to regenerate/reload shadow data structures. For now,
we have no mechanism for that.
E.g. when clearing AP masks later, we could still have a vSIE CPU making
use of AP adapters as the masks might not be cons
On Thu, Aug 09, 2018 at 03:44:40PM +0800, Alan Kao wrote:
> We expect that a kernel with CONFIG_FPU=y can still support no-FPU
> machines. To do so, the kernel should first examine the existence of a
> FPU, then do nothing if a FPU does exist; otherwise, it should
> disable/bypass all FPU-related f
From: Palmer Dabbelt
Add documentation for the SiFive implementation of the RISC-V Platform
Level Interrupt Controller (PLIC). The PLIC connects global interrupt
sources to the local interrupt controller on each hart.
Signed-off-by: Palmer Dabbelt
[hch: various fixes and updates]
Signed-off-by
Add a driver for the SiFive implementation of the RISC-V Platform Level
Interrupt Controller (PLIC). The PLIC connects global interrupt sources
to the local interrupt controller on each hart.
This driver is based on the driver in the RISC-V tree from Palmer Dabbelt,
but has been almost entirely r
This series tries adds support for interrupt handling and timers
for the RISC-V architecture.
The basic per-hart interrupt handling implemented by the scause
and sie CSRs is extremely simple and implemented directly in
arch/riscv/kernel/irq.c. In addition there is a irqchip driver
for the PLIC ex
From: Palmer Dabbelt
Add documentation on the RISC-V local interrupt controller, which is a
per-hart interrupt controller that manages all interrupts entering a
RISC-V hart. This interrupt controller is present on all RISC-V systems.
Signed-off-by: Palmer Dabbelt
[hch: minor cleanups]
Signed-o
On 08/08/2018 10:41, Jerome Brunet wrote:
> On Wed, 2018-08-08 at 00:00 +0200, Maxime Jourdan wrote:
>> Wrap the canvas node in a syscon node.
>>
>> Signed-off-by: Maxime Jourdan
>> ---
>> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 17 +
>> 1 file changed, 17 insertions(+)
>>
>>
On Thu, Aug 09, 2018 at 09:50:55AM +0200, Oscar Salvador wrote:
> On Wed, Aug 08, 2018 at 11:29:08PM +0200, Oscar Salvador wrote:
> > On Wed, Aug 08, 2018 at 01:55:59PM -0400, Jerome Glisse wrote:
> > > Note that Dan did post patches that already go in that direction (unifying
> > > code between de
On Wed, Aug 08, 2018 at 11:29:08PM +0200, Oscar Salvador wrote:
> On Wed, Aug 08, 2018 at 01:55:59PM -0400, Jerome Glisse wrote:
> > Note that Dan did post patches that already go in that direction (unifying
> > code between devm and HMM). I think they are in Andrew queue, looks for
> >
> > mm: Re
On Wed, Aug 08, 2018 at 05:07:08PM -0700, Matthew Wilcox wrote:
> On Thu, Aug 09, 2018 at 07:31:25AM +1000, Dave Chinner wrote:
> > IMO, we've had enough recent bugs to deal with from shrinkers being
> > called before the filesystem is set up and from trying to handle
> > allocation errors during s
We expect that a kernel with CONFIG_FPU=y can still support no-FPU
machines. To do so, the kernel should first examine the existence of a
FPU, then do nothing if a FPU does exist; otherwise, it should
disable/bypass all FPU-related functions.
In this patch, a new global variable, has_fpu, is creat
On Wed, Aug 08, 2018 at 02:47:42PM -0700, Stephane Eranian wrote:
> Hi,
>
> Ok, I found the problem. It still exists upstream , just very tricky to
> trigger.
> Took me lots of time with gdb + watchpoints to track this down, where
> in fact it was just in front of me.
>
> From the crashdump:
>
501 - 600 of 614 matches
Mail list logo
