On 2/4/2019 2:37 PM, Jarkko Sakkinen wrote:
Rename TPM_BUFSIZE defined in drivers/char/tpm/st33zp24/st33zp24.h to
ST33ZP24_BUFSIZE.
Rename TPM_BUFSIZE defined in drivers/char/tpm/tpm_i2c_infineon.c to
TPM_I2C_INFINEON_BUFSIZE.
Please also add a prefix to TPM_RETRY in tpm_i2c_nuvoton.c.
Thanks
On Fri, Feb 01, 2019 at 11:18:22PM +0100, Ard Biesheuvel wrote:
> On Fri, 1 Feb 2019 at 20:21, Nathan Chancellor
> wrote:
> >
> > As of commit e2a2e56e4082 ("arm64: dump: no need to check return value
> > of debugfs_create functions") in the arm64 for-next/core branch,
> > ptdump_debugfs_register
On Mon, 4 Feb 2019 at 13:03, Torsten Duwe wrote:
>
> On Tue, Jan 22, 2019 at 02:55:12PM +0100, Ard Biesheuvel wrote:
> > On Tue, 22 Jan 2019 at 14:28, Torsten Duwe wrote:
> > >
> > > On Tue, Jan 22, 2019 at 10:18:17AM +, Julien Thierry wrote:
> > > > Hi Torsten,
> > > >
> > > > A few suggesti
On Mon, Feb 04, 2019 at 11:49:56AM +0100, Uladzislau Rezki wrote:
> On Fri, Feb 01, 2019 at 01:45:28PM +0100, Michal Hocko wrote:
> > On Thu 31-01-19 17:24:52, Uladzislau Rezki (Sony) wrote:
> > > vmap_lazy_nr variable has atomic_t type that is 4 bytes integer
> > > value on both 32 and 64 bit syst
On Mon, Feb 04, 2019 at 06:16:24PM +0800, Chen-Yu Tsai wrote:
> On Mon, Feb 4, 2019 at 5:34 PM Maxime Ripard
> wrote:
> >
> > On Sun, Feb 03, 2019 at 11:56:27PM +0800, Chen-Yu Tsai wrote:
> > > The MMC device tree bindings include properties used to signal various
> > > signalling speed modes. Un
On Mon, 4 Feb 2019 at 14:29, Anders Roxell wrote:
>
> Commit e2a2e56e4082 ("arm64: dump: no need to check return value of
> debugfs_create functions")
> changed the return value from 'int' to 'void'.
>
> ../drivers/firmware/efi/arm-runtime.c: In function ‘ptdump_init’:
> ../drivers/firmware/efi/a
Currently "0xf << 36" is used to
clear SSIU-9 internal buffer state, which overflows 32-bit value
according to user reference manual, it is always bit4 ~ bit7
of SSI_SYS_STATUS[1,3,5,7] registers indicate
SSIU-9's buffer state, so "0xf << 4" should be used.
This patch fix incorrect shifting issue
On 4/02/19 12:54 PM, Ulf Hansson wrote:
> On Mon, 4 Feb 2019 at 10:58, Adrian Hunter wrote:
>>
>> On 1/02/19 10:10 AM, Ulf Hansson wrote:
>>> On Fri, 1 Feb 2019 at 02:38, Chaotian Jing
>>> wrote:
On Thu, 2019-01-31 at 16:58 +0100, Ulf Hansson wrote:
> On Thu, 31 Jan 2019 at 08:53,
Rename TPM_BUFSIZE defined in drivers/char/tpm/st33zp24/st33zp24.h to
ST33ZP24_BUFSIZE.
Rename TPM_BUFSIZE defined in drivers/char/tpm/tpm_i2c_infineon.c to
TPM_I2C_INFINEON_BUFSIZE.
Cc: sta...@vger.kernel.org
Fixes: bf38b8710892 ("tpm/tpm_i2c_stm_st33: Split tpm_i2c_tpm_st33 in 2 layers
(core +
Hi,
On 03/02/19 5:50 PM, tudor.amba...@microchip.com wrote:
> + Vignesh
>
Thanks for looping in.
> On 01/28/2019 07:02 AM, Purna Chandra Mandal wrote:
>> cadence-quadspi controller allows upto eight bytes of data to
>> be written in software Triggered Instruction generator (STIG) mode
>> of ope
Commit e2a2e56e4082 ("arm64: dump: no need to check return value of
debugfs_create functions")
changed the return value from 'int' to 'void'.
../drivers/firmware/efi/arm-runtime.c: In function ‘ptdump_init’:
../drivers/firmware/efi/arm-runtime.c:52:9: error: void value not ignored as it
ought to
On 30/01/2019 16:58, Valentin Schneider wrote:
> On 15/01/2019 13:58, Julien Thierry wrote:
> [...]> @@ -6151,6 +6159,20 @@ void ___might_sleep(const char *file, int line,
> int preempt_offset)
>> EXPORT_SYMBOL(___might_sleep);
>> #endif
>>
>> +#ifdef CONFIG_DEBUG_UACCESS_SLEEP
>> +void __mig
On 2/4/2019 1:07 PM, Jarkko Sakkinen wrote:
On Mon, Feb 04, 2019 at 10:14:38AM +0100, Roberto Sassu wrote:
On 2/1/2019 8:15 PM, Mimi Zohar wrote:
Hi Roberto,
Sorry for the delayed review. A few comments inline below, minor
suggestions.
diff --git a/security/integrity/ima/ima.h b/security/in
/commits/michael-kao-mediatek-com/Add-Mediatek-thermal-dirver-for-mt8183/20190204-131145
base:
https://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git
next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagn
Added the tests that I've been using for testing TPM 2.0 functionality
for a long time but have been out-of-tree so far, residing in
https://github.com/jsakkine-intel/tpm2-scripts
Cc: Tadeusz Struk
Signed-off-by: Jarkko Sakkinen
Acked-By: Joey Pabalinas
Reviewed-by: Petr Vorel
---
v2: TARGETS
Hi Mark,
> On Mon, Feb 04, 2019 at 01:52:42PM +0100, Lukasz Majewski wrote:
> > > On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
>
> > > You've been sending ARM: patches to me (the SPI maintainer) and
> > > one of the DT maintainers.
>
> ...
>
> > Moreover, I've CC'ed dev
Dear, please confirm you received my mail
Rufus
Hello Heiko,
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 properties
from UART2 node for rock64.
The DMAC of rk3328 can use 8 channels at same time. Currently, total
7 channe
On Mon, Feb 04, 2019 at 01:52:42PM +0100, Lukasz Majewski wrote:
> > On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
> > You've been sending ARM: patches to me (the SPI maintainer) and one of
> > the DT maintainers.
...
> Moreover, I've CC'ed developers (Esben, Andrey, Martin)
On Mon, 2019-02-04 at 14:07 +0200, Jarkko Sakkinen wrote:
> On Mon, Feb 04, 2019 at 10:14:38AM +0100, Roberto Sassu wrote:
> > On 2/1/2019 8:15 PM, Mimi Zohar wrote:
> > > Hi Roberto,
> > >
> > > Sorry for the delayed review. A few comments inline below, minor
> > > suggestions.
> > >
> > > > di
03.02.2019 17:47, Dmitry Osipenko пишет:
> 01.02.2019 20:07, Sowjanya Komatineni пишет:
>> This patch adds DMA support for Tegra I2C.
>>
>> Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
>> transfer size of the max FIFO depth and DMA mode is used for
>> transfer size higher than ma
Hi Mark,
> On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
>
> > Is there any interest in adding new code (or fixes) to VF610 ?
>
> You've been sending ARM: patches to me (the SPI maintainer) and one of
> the DT maintainers.
> You need to send patches for that platform to th
pon., 4 lut 2019 o 12:30 Linus Walleij napisał(a):
>
> On Thu, Jan 31, 2019 at 1:08 PM Matti Vaittinen
> wrote:
>
> > ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
> > controlled by GPIO framework.
> >
> > IRQs are handled by regmap-irq and GPIO driver is not
> > aware of the irq usage.
> >
Header rohm-bd718x7.h was split to generic and component specific
parts. This changed the struct bd718x7. Adapt the clk driver to
these changes.
Signed-off-by: Matti Vaittinen
---
drivers/clk/clk-bd718x7.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/clk/clk-
Header rohm-bd718x7.h was split to generic and component specific
parts. This changed the struct bd718x7. Adapt the regulator driver to
these changes.
Signed-off-by: Matti Vaittinen
Acked-by: Mark Brown
---
drivers/regulator/bd718x7-regulator.c | 22 +++---
1 file changed, 11 in
Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
drivers) and 4 GPIO pins which can be configured for I/O or
as interrupt sources withe configurable trigger levels.
Signed-off-by: Matti Vaittinen
Reviewed-by: Rob Herring
Acked-by: Linus Walleij
---
.../devicetree/bindings/mfd/rohm,b
Patch series introducing support for ROHM BD70528 PMIC
Please note that patch 1 breaks compilation without patches 2 and 3
ROHM BD70528 is a programmable Power Management IC for battery
powered 'ultra low power' systems like the pre-announced NXP
i.MX7 ULP. This patch series introduces support fo
Support RTC block in ROHM bd70528 power management IC. Support
getting and setting the time and date as well as arming an alarm
which can also be used to wake the PMIC from standby state.
HW supports wake interrupt only for the next 24 hours (sec, minute
and hour information only) so we limit also
ROHM BD70528MWV is an ultra-low quiescent current general
purpose single-chip power management IC for battery-powered
portable devices.
Add MFD core which enables chip access for following subdevices:
- regulators/LED drivers
- battery-charger
- gpios
- 32.768kHz cl
Initial support for watchdog block included in ROHM BD70528
power management IC.
Configurations for low power states are still to be checked.
Signed-off-by: Matti Vaittinen
---
drivers/watchdog/Kconfig | 12 +++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/bd70528_wdt.c | 187
ROHM BD70528 PMIC includes battery charger block. Support charger
staus queries and doing few basic settings like input current limit
and charging current.
Signed-off-by: Matti Vaittinen
---
drivers/power/supply/Kconfig | 9 +
drivers/power/supply/Makefile | 1 +
drivers/p
Bindings for dac7612.
Cc: devicet...@vger.kernel.org
Signed-off-by: Ricardo Ribalda Delgado
---
v4 Changelog by Rob Herring
-Add ti, prefix to gpio
-Fix example da@1
-Fix partname
.../bindings/iio/dac/ti,dac7612.txt | 29 +++
MAINTAINERS
It is a driver for Texas Instruments Dual, 12-Bit Serial Input
Digital-to-Analog Converter.
Datasheet of this chip:
http://www.ti.com/lit/ds/sbas106/sbas106.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
Changelog v4 by: Jonathan Cameron ,
dt related:
-Fix pin name
-Fix part name
-improve comm
ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
controlled by GPIO framework.
IRQs are handled by regmap-irq and GPIO driver is not
aware of the irq usage.
Signed-off-by: Matti Vaittinen
Reviewed-by: Linus Walleij
---
drivers/gpio/Kconfig| 11 +++
drivers/gpio/Makefile | 1
On Mon, Feb 04, 2019 at 01:13:54PM +0100, Christian Zigotzky wrote:
>>> Results: The X1000 and X5000 boot but unfortunately the P.A. Semi Ethernet
>>> doesn't work.
>> Are there any interesting messages in the boot log? Can you send me
>> the dmesg?
>>
> Here you are: http://www.xenosoft.de/dmesg_
ROHM BD70528 is an ultra low power PMIC with similar 32K clk as
bd718x7. Only difference (from clk perspective) is register address.
Add support for controlling BD70528 clk using bd718x7 driver.
Signed-off-by: Matti Vaittinen
---
drivers/clk/Kconfig | 6 +++---
drivers/clk/clk-bd718x7.c |
Split the bd718x7.h to ROHM common and bd718x7 specific parts
so that we do not need to add same things in every new ROHM
PMIC header. Please note that this change requires changes also
in bd718x7 sub-device drivers for regulators and clk.
Signed-off-by: Matti Vaittinen
---
drivers/mfd/rohm-bd71
Add support for Texas Instruments ADS7866, ADS7867 and ADS7868
8/10/12 bit Single channel ADC.
Datasheet: http://www.ti.com/lit/ds/symlink/ads7868.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
v4: Changes by Alexandru Ardelean
Break Kconfig into a table
drivers/iio/adc/Kconfig | 11 +++
On Sat, Feb 02, 2019 at 12:58:07PM -0500, Vince Weaver wrote:
> On Fri, 1 Feb 2019, Jiri Olsa wrote:
>
> > >
> > > I've just started fuzzing with the patch applied. Often it takes a few
> > > hours to trigger the bug.
> >
> > cool, thanks
>
> I let it run overnight and no crash.
>
> > > Adde
Hi,
Den mån 4 feb. 2019 kl 12:18 skrev Shivamurthy Shastri (sshivamurthy)
:
>
> Driver is redesigned using parameter page to support all the Micron
> SPI NAND flashes.
>
> Parameter page of Micron flashes is similar to ONFI parameter table and
> functionality is same, so copied some of the common
On Thu, Jan 31, 2019 at 10:08:11AM +0100, Stefan Agner wrote:
> On 30.01.2019 18:54, Lorenzo Pieralisi wrote:
> > On Tue, Dec 04, 2018 at 05:55:26PM +0100, Stefan Agner wrote:
> >> Add length to the struct dw_pcie and check that the accessors
> >> dw_pcie_(rd|wr)_conf() do not read/write beyond tha
On 02/02/2019 05:37, Christian Kujau wrote:
> Hi,
>
> I'm running an Ubuntu "mainline" kernel[0] as a Xen 4.11.1 DomU (PV) and
> ever since upgrading to Linux 5.0-rcX I get these WARNING messages shown
> below. Going back in my logs[1] I can see that I got a similar messages
> for v4.20 too, bu
On 02/02/2019 11:57, Tom Burkart wrote:
This patch implements the pps echo functionality for pps-gpio, that
sysfs claims is available already.
Configuration is done via device tree bindings.
This patch was originally written by Lukas Senger as part of a masters
thesis project and modified for i
On 02/02/2019 11:57, Tom Burkart wrote:
This patch changes the GPIO access for the pps-gpio driver from the
integer based API to the descriptor based API.
Reviewed-by: Philipp Zabel
Signed-off-by: Tom Burkart
Acked-by: Rodolfo Giometti
--
GNU/Linux Solutions e-mail: giome.
On Mon, Feb 04, 2019 at 12:29:53PM +0100, Linus Walleij wrote:
> On Thu, Jan 31, 2019 at 1:08 PM Matti Vaittinen
> wrote:
>
> > ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
> > controlled by GPIO framework.
> >
> > IRQs are handled by regmap-irq and GPIO driver is not
> > aware of the irq
Hi Masahiro,
On 1/30/19 3:52 AM, Masahiro Yamada wrote:
> For the include directive with double-quotes "", the preprocessor
> searches the header in the relative path to the current file.
>
> Fix them up, and remove the header search path option.
>
> Signed-off-by: Masahiro Yamada
Acked-by: Eri
On Thu, Oct 18, 2018 at 03:33:18PM +0800, Icenowy Zheng wrote:
> This patchset brings the support for Analogix ANX6345 RGB-(e)DP bridge,
> which is used by some Allwinner A64 laptops, such as Pinebook and Olimex
> TERES-I.
>
So what's the status here? I'm working on the Teres-I and I find myself
On Mon, Feb 04, 2019 at 10:02:11AM +0100, Juri Lelli wrote:
> On 18/01/19 17:46, Juri Lelli wrote:
> > On 18/01/19 08:17, Tejun Heo wrote:
> > > On Thu, Jan 17, 2019 at 09:47:34AM +0100, Juri Lelli wrote:
> > > > Hi,
> > > >
> > > > v6 of a series of patches, originally authored by Mathieu, with t
This adds a driver for the SMMUv3 PMU into the perf framework.
It includes an IORT update to support PM Counter Groups.
This is based on the initial work done by Neil Leeder[1]
SMMUv3 PMCG devices are named as smmuv3_pmcg_
where is the physical page address of the SMMU PMCG.
For example, the PMC
From: Neil Leeder
Adds a new driver to support the SMMUv3 PMU and add it into the
perf events framework.
Each SMMU node may have multiple PMUs associated with it, each of
which may support different events.
SMMUv3 PMCG devices are named as smmuv3_pmcg_ where
is the physical page address of the
On Fri, Feb 01, 2019 at 04:15:19PM -0800, Andrey Smirnov wrote:
> Everyone:
>
> This series contains changes I made in order to enable support of PCIE
> IP block on i.MX8MQ SoCs.
>
> Changes since [v6]:
>
> - Patches rebased on Lorenzo's pci/dwc branch
>
> - Reworded commit message of "PCI: i
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMUv3 PMU driver.
Signed-off-by: Neil Leeder
Signed-off-by: Hanjun Guo
Signed-off-by: Shameer Kolothum
Reviewed-by: Robin Murphy
---
drivers/acpi/ar
From: Jarkko Sakkinen
> Sent: 01 February 2019 11:20
> The current approach to read first 6 bytes from the response and then tail
> of the response, can cause the 2nd memcpy_fromio() to do an unaligned read
> (e.g. read 32-bit word from address aligned to a 16-bits), depending on how
> memcpy_fromi
This adds support for MSI-based counter overflow interrupt.
Signed-off-by: Shameer Kolothum
Reviewed-by: Robin Murphy
---
drivers/perf/arm_smmuv3_pmu.c | 58 +++
1 file changed, 58 insertions(+)
diff --git a/drivers/perf/arm_smmuv3_pmu.c b/drivers/perf/a
HiSilicon erratum 162001800 describes the limitation of
SMMUv3 PMCG implementation on HiSilicon Hip08 platforms.
On these platforms, the PMCG event counter registers
(SMMU_PMCG_EVCNTRn) are read only and as a result it
is not possible to set the initial counter period value
on event monitor start.
On 04 February 2019 at 08:56AM, Christoph Hellwig wrote:
On Sun, Feb 03, 2019 at 05:49:02PM +0100, Christian Zigotzky wrote:
OK, next step: b50f42f0fe12965ead395c76bcb6a14f00cdf65b (powerpc/dma: use
the dma_direct mapping routines)
git clone git://git.infradead.org/users/hch/misc.git -b powerpc
On Thu, Jan 17, 2019 at 09:47:38AM +0100, Juri Lelli wrote:
> No synchronisation mechanism exists between the cpuset subsystem and calls
> to function __sched_setscheduler(). As such, it is possible that new root
> domains are created on the cpuset side while a deadline acceptance test
> is carried
On Mon, 4 Feb 2019 11:15:25 +0100
Harald Freudenberger wrote:
> On 01.02.19 15:35, Cornelia Huck wrote:
> > On Thu, 31 Jan 2019 18:50:57 -0500
> > Tony Krowiak wrote:
> >
> >> On 1/31/19 4:55 AM, Cornelia Huck wrote:
> >>> On Wed, 30 Jan 2019 12:48:46 -0500
> >>> Tony Krowiak wrote:
> >>> T
On Mon, Feb 04, 2019 at 10:14:38AM +0100, Roberto Sassu wrote:
> On 2/1/2019 8:15 PM, Mimi Zohar wrote:
> > Hi Roberto,
> >
> > Sorry for the delayed review. A few comments inline below, minor
> > suggestions.
> >
> > > diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
> >
On Mon, Feb 04, 2019 at 01:02:36PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 17, 2019 at 09:47:37AM +0100, Juri Lelli wrote:
> > @@ -3233,11 +3233,11 @@ void cpuset_cpus_allowed(struct task_struct *tsk,
> > struct cpumask *pmask)
> > {
> > unsigned long flags;
> >
> > - spin_lock_irqsave
On Sun, Feb 03, 2019 at 06:00:54PM -0500, Mimi Zohar wrote:
> Hi Jarkko,
>
> On Fri, 2019-02-01 at 19:41 +0200, Jarkko Sakkinen wrote:
> > Rename TPM_BUFSIZE defined in drivers/char/tpm/st33zp24/st33zp24.h to
> > ST33ZP24_BUFSIZE as it collides with TPM_BUFSIZE defined in
> > drivers/char/tpm/tpm.
04.02.2019 14:05, Thierry Reding пишет:
> On Mon, Feb 04, 2019 at 09:53:32AM +, Jon Hunter wrote:
>>
>>
>> On 04/02/2019 08:45, Thierry Reding wrote:
>>
>> ...
>>
>>> The idea was, as I was saying below, to reuse dev_pm_ops even if
>>> !CONFIG_PM. So pm_runtime_enable() could be something like
On Tue, Jan 22, 2019 at 02:55:12PM +0100, Ard Biesheuvel wrote:
> On Tue, 22 Jan 2019 at 14:28, Torsten Duwe wrote:
> >
> > On Tue, Jan 22, 2019 at 10:18:17AM +, Julien Thierry wrote:
> > > Hi Torsten,
> > >
> > > A few suggestions below.
> > >
> > > > +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS
>
On Thu, Jan 17, 2019 at 09:47:37AM +0100, Juri Lelli wrote:
> @@ -3233,11 +3233,11 @@ void cpuset_cpus_allowed(struct task_struct *tsk,
> struct cpumask *pmask)
> {
> unsigned long flags;
>
> - spin_lock_irqsave(&callback_lock, flags);
> + raw_spin_lock_irqsave(&callback_lock, fla
On Sun, Feb 03, 2019 at 11:26:55PM +0100, Petr Vorel wrote:
> Hi Jarkko,
>
> > Added the tests that I've been using for testing TPM 2.0 functionality
> > for long time but have out-of-tree so far residing in
>
> > https://github.com/jsakkine-intel/tpm2-scripts
>
> > Cc: Tadeusz Struk
> > Signed
Vlastimil correctly pointed out that when a fast search fails and
cc->migrate_pfn
is reinitialised to the lowest PFN found that the caller does not use the
updated
PFN.
He also pointed out that there is an inconsistency between
move_freelist_head and move_freelist_tail. This patch adds a new hel
On Fri, Feb 01, 2019 at 10:04:35AM -0800, Linus Torvalds wrote:
> On Thu, Jan 31, 2019 at 12:45 PM Jarkko Sakkinen
> wrote:
> >
> > I understand what you mean. Just surprised that this hasn't failed
> > before to anyone (the same driver has been even successfully used
> > on ARM64 with TrustZone b
On Thu, Jan 17, 2019 at 09:47:37AM +0100, Juri Lelli wrote:
> @@ -2366,7 +2366,7 @@ static int cpuset_common_seq_show(struct seq_file *sf,
> void *v)
> cpuset_filetype_t type = seq_cft(sf)->private;
> int ret = 0;
>
> - spin_lock_irq(&callback_lock);
> + raw_spin_lock_irq(&ca
Hi Robin,
On 2019-01-21 15:52, Robin Murphy wrote:
> Installing the appropriate non-IOMMU DMA ops in arm_iommu_detch_device()
> serves the case where IOMMU-aware drivers choose to control their own
> mapping but still make DMA API calls, however it also affects the case
> when the arch code itself
On Thu, Jan 31, 2019 at 11:52:32AM +, Pawel Laszczak wrote:
> This patch introduce new Cadence USBSS DRD driver
> to linux kernel.
>
> The Cadence USBSS DRD Driver is a highly
> configurable IP Core which can be
> instantiated as Dual-Role Device (DRD),
> Peripheral Only and Host Only (XHCI)
>
On Thu, Jan 31, 2019 at 11:52:31AM +, Pawel Laszczak wrote:
> Patch moves switch responsible for decoding descriptor type
> outside snprintf. It's little improves code readability.
Should that last sentence read: "It improves code readability a little"?
thanks,
greg k-h
On Fri, Feb 01, 2019 at 09:49:05AM -0800, Linus Torvalds wrote:
> On Fri, Feb 1, 2019 at 3:33 AM Jarkko Sakkinen
> wrote:
> >
> > Thus, it makes sense to fix this also in tpm_crb, not least because
> > the fix can be then backported to stable kernels and make them more robust
> > when compiled in
On Mon, Feb 04, 2019 at 02:29:56PM +0300, Alexey Budankov wrote:
> On 04.02.2019 13:36, Jiri Olsa wrote:
> > On Mon, Feb 04, 2019 at 01:12:11PM +0300, Alexey Budankov wrote:
> >>
> >> Hi,
> >>
> >> On 03.02.2019 18:30, Jiri Olsa wrote:
> >>> hi,
> >>> this patchset adds the --dir option to record c
Driver is redesigned using parameter page to support all the Micron
SPI NAND flashes.
Parameter page of Micron flashes is similar to ONFI parameter table and
functionality is same, so copied some of the common functions like crc16
and bit_wise_majority from nand_onfi.c.
This driver is tested usin
On Fri, Feb 01, 2019 at 07:20:42PM +, Winkler, Tomas wrote:
> >
> > The current approach to read first 6 bytes from the response and then tail
> > of
> > the response, can cause the 2nd memcpy_fromio() to do an unaligned read
> > (e.g. read 32-bit word from address aligned to a 16-bits), depe
On Mon, Feb 4, 2019 at 12:40 PM Rafael J. Wysocki wrote:
>
> On Fri, Feb 1, 2019 at 4:18 PM Ulf Hansson wrote:
> >
> > On Fri, 1 Feb 2019 at 02:04, Rafael J. Wysocki wrote:
> > >
> > > Hi Greg at al,
> > >
> > > This is a combination of the two device links series I have posted
> > > recently (h
On Thu, Jan 31, 2019 at 11:52:29AM +, Pawel Laszczak wrote:
> Patch moves some decoding functions from driver/usb/dwc3/debug.h driver
> to driver/usb/common/debug.c file. These moved functions include:
> dwc3_decode_get_status
> dwc3_decode_set_clear_feature
> dwc3_decode_set_addres
On Thu, Jan 31, 2019 at 11:52:29AM +, Pawel Laszczak wrote:
> Patch moves some decoding functions from driver/usb/dwc3/debug.h driver
> to driver/usb/common/debug.c file. These moved functions include:
> dwc3_decode_get_status
> dwc3_decode_set_clear_feature
> dwc3_decode_set_addres
On Fri, Feb 1, 2019 at 4:18 PM Ulf Hansson wrote:
>
> On Fri, 1 Feb 2019 at 02:04, Rafael J. Wysocki wrote:
> >
> > Hi Greg at al,
> >
> > This is a combination of the two device links series I have posted
> > recently (https://lore.kernel.org/lkml/2493187.oiopcwj...@aspire.rjw.lan/
> > and https
On Sun, Feb 03, 2019 at 05:30:39PM +0100, Thomas Gleixner wrote:
> On Sat, 2 Feb 2019, Heiko Carstens wrote:
> > I added a barrier between those two and now the code looks like this:
> >
> > 140: a5 1b 00 01 oill%r1,1
> > 144: e3 10 a0 e0 00 24 stg %r1,224(%r10)
> > 1
Some of the manufacturers support parameter page, which can be used
to get the device details during detection.
This function reads parameter page and this page can be accessed by
set of commands, which are common across the manufacturers.
Signed-off-by: Shivamurthy Shastri
Reviewed-by: Bean Huo
On Thu, Jan 31, 2019 at 1:08 PM Matti Vaittinen
wrote:
> ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
> controlled by GPIO framework.
>
> IRQs are handled by regmap-irq and GPIO driver is not
> aware of the irq usage.
>
> Signed-off-by: Matti Vaittinen
(...)
> I dropped the review-by from
On Thu, 31 Jan 2019, Huaisheng Ye wrote:
> From: Huaisheng Ye
>
> This patch set could be used for dm-writecache when use persistent
> memory as cache data device.
>
> Patch 1 and 2 go towards removing unused parameter and codes which
> actually doesn't really work.
I agree that there is so
On Thu, Jan 31, 2019 at 1:04 PM Matti Vaittinen
wrote:
> Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
> drivers) and 4 GPIO pins which can be configured for I/O or
> as interrupt sources withe configurable trigger levels.
>
> Signed-off-by: Matti Vaittinen
(...)
> +Required proper
On 04.02.2019 13:36, Jiri Olsa wrote:
> On Mon, Feb 04, 2019 at 01:12:11PM +0300, Alexey Budankov wrote:
>>
>> Hi,
>>
>> On 03.02.2019 18:30, Jiri Olsa wrote:
>>> hi,
>>> this patchset adds the --dir option to record command (and all
>>> the other record command that overload cmd_record) that allow
Parameter page is supported by some of the manufacturers and instead of
maintaining spinand_info structure for each flash it is better to use
the parameter page to get the flash info. As I have seen the different
datasheets, command required to access parameter page is same across the
manufacturers
On Mon, Feb 04, 2019 at 01:05:32PM +0200, Georgi Djakov wrote:
> On 2/4/19 12:35, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > commit 99d570da309813f67e9c741edeff55bafc6c1d5e upstream.
> >
> > Enable
On Mon, Feb 04, 2019 at 12:48:00PM +0200, Amir Goldstein wrote:
> On Mon, Feb 4, 2019 at 12:44 PM Greg Kroah-Hartman
> wrote:
> >
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Amir Goldstein
> >
> > commit b469e7e47c8a075c
On 31-01-19, 09:29, Bjorn Andersson wrote:
> The SDC controls live in the south tile, not the north one. Correct this
> so that we program the right registers.
Reviewed-by: Vinod Koul
>
> Cc: sta...@vger.kernel.org
> Fixes: 22eb8301dbc1 ("pinctrl: qcom: Add qcs404 pinctrl driver")
> Signed-off-
Christophe Leroy writes:
> The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
> moves the thread_info into task_struct.
Hi Christophe,
I've taken this series and split some of the patches up a bit more.
I'll just run it through some tests and then post my version.
cheer
As the function is responsible for executing the individual steps supplied
in the steps argument, execute_steps is a more descriptive name than the
rather generic next.
Signed-off-by: David Kozub
Reviewed-by: Scott Bauer
---
block/sed-opal.c | 37 +++--
1 file ch
On Mon, Feb 04, 2019 at 11:31:13AM +0100, Daniel Vetter wrote:
> The compiler already clears this for us.
>
> More important, someone might look what this is actually used for,
> and freak out about the dragon staring back at them.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc:
On Mon, Feb 04, 2019 at 11:31:14AM +0100, Daniel Vetter wrote:
> Noticed why wonder what vboxvideo is using the ->master_set/drop hooks
> for.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc: Fabio Rafael da Rosa
> Cc: Nicholas Mc Guire
> Cc: Daniel Vetter
> Cc: Hans de Goede
Hi Ulf,
On 2/4/2019 6:06 AM, Ulf Hansson wrote:
> On Fri, 1 Feb 2019 at 17:34, Wei Xu wrote:
>>
>> Hi Jan,
>>
>> On 1/24/2019 7:52 AM, Jan Kiszka wrote:
>>> From: Jan Kiszka
>>>
>>> Somewhere along recent changes to power control of the wl1835, power-on
>>> became very unreliable on the hikey, f
3.18-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 1fe627da30331024f453faef04d500079b901107 ]
libdwfl parses an ELF file itself and creates mappings for the
individual sections. perf on the other hand sees raw mmap events which
repre
3.18-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 3d20c6246690219881786de10d2dda93f616d0ac ]
Path passed to libdw for unwinding doesn't include symfs path
if specified, so unwinding fails because ELF file is not found.
Similar to u
Hi,
> Just want to check if you had a chance to review the following patch series?
I am sorry, but for some reason they are not listed in my patchwork
instance, so they fell through the cracks :( Can you please resend them?
I will double check they show up in patchwork then.
Thanks,
Wolfram
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
[ Upstream commit 63346650c1a94a92be61a57416ac88c0a47c4327 ]
sk_reset_timer() and sk_stop_timer() properly handle
sock refcnt for timer function. Switching to them
could fix a refcou
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Thore
[ Upstream commit e15aa3b2b1388c399c1a2ce08550d2cc4f7e3e14 ]
After a timeout event caused by for example a broadcast storm, when
the MAC and PHY are reset, the BQL TX queue needs
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Hildenbrand
commit e0a352fabce61f730341d119fbedf71ffdb8663f upstream.
We had a race in the old balloon compaction code before b1123ea6d3b3
("mm: balloon: use general non-lru movable page
701 - 800 of 1302 matches
Mail list logo
