The driver for Alcor Micro AU6601 and AU6621 controllers uses a pointer to
get from the private alcor_sdmmc_host structure to the generic mmc_host
structure. However the latter is always immediately preceding the former in
memory, so compute its address with a subtraction (which is cheaper than a
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> SoundWire support will be provided in Linux with the Sound Open
> Firmware (SOF) on Intel platforms. Before we start adding the missing
> pieces, there are a number of warnings and style issues reported by
> checkpatch, cppcheck and Coccinelle that
On 01.05.19 23:45, Stephen Rothwell wrote:
> Commit
> 2b731a920986 ("parisc: Update huge TLB page support to use per-pagetable
> spinlock")
> is missing a Signed-off-by from its committer.
Thanks. Fixed now.
Helge
signature.asc
Description: OpenPGP digital signature
On 01-05-19, 18:07, Greg KH wrote:
> On Wed, May 01, 2019 at 10:57:23AM -0500, Pierre-Louis Bossart wrote:
> > SoundWire support will be provided in Linux with the Sound Open
> > Firmware (SOF) on Intel platforms. Before we start adding the missing
> > pieces, there are a number of warnings and
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> For some reason the newlines are not used everywhere. Fix as needed.
>
> Reported-by: Joe Perches
> Reviewed-by: Takashi Iwai
> Signed-off-by: Pierre-Louis Bossart
> ---
> drivers/soundwire/bus.c| 74 +--
>
On Sat, Apr 27, 2019 at 03:09:15PM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 26 Apr 2019 23:31:40 +0800
> Changbin Du escreveu:
>
> > This converts the plain text documentation to reStructuredText format and
> > add it to Sphinx TOC tree. No essential content change.
> >
> > Signed-off-by:
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> Use Linux style. In some cases parenthesis alignment is modified to
> keep the code readable.
lgtm, It would have been okay to have this and previous as a single
patch. It is the same module, but more split is welcome, makes it easier to
review in
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> and make the code more readable
Well patch subject and log are not meant to be read as a continuous
statement, It would nice to have a proper lines for this
>
> Reviewed-by: Takashi Iwai
> Signed-off-by: Pierre-Louis Bossart
> ---
>
Built and booted on my x86 machine. No dmesg regression.
Built and booted on my x86 machine with defconfig. No dmesg regressions.
Thank you
Bharath
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> use Linux style
>
> Reviewed-by: Takashi Iwai
> Signed-off-by: Pierre-Louis Bossart
> ---
> drivers/soundwire/bus.h| 12 ++--
> drivers/soundwire/cadence_master.h | 18 +-
Again this touches core and lib.
On Thu, May 2, 2019 at 6:11 AM Rob Herring wrote:
>
> On Tue, Apr 30, 2019 at 09:50:45AM +0530, Yash Shah wrote:
> > On Fri, Apr 26, 2019 at 3:04 PM Sudeep Holla wrote:
> > >
> > > On Fri, Apr 26, 2019 at 11:20:17AM +0530, Yash Shah wrote:
> > > > On Thu, Apr 25, 2019 at 3:43 PM Sudeep Holla
>
On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> No C++ comments in .h files
>
> Reviewed-by: Takashi Iwai
> Signed-off-by: Pierre-Louis Bossart
> ---
> drivers/soundwire/bus.h| 4 ++--
> drivers/soundwire/cadence_master.h | 4 ++--
> drivers/soundwire/intel.h | 4 ++--
Hi Lukasz,
On 19. 4. 19. 오후 11:19, Lukasz Luba wrote:
> Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memory
> Controller frequencies for driver's DRAM timings.
>
> Signed-off-by: Lukasz Luba
> ---
> drivers/clk/samsung/clk-exynos5420.c | 13 -
> 1 file changed,
Hi Neil,
On 5/1/19 9:35 PM, NeilBrown wrote:
>
> If the upper and lower layers use incompatible ACL formats, it is not
> possible to copy the ACL xttr from one to the other, so overlayfs
attr (?)
> cannot work with them.
> This happens particularly with NFSv4 which
Currently, the setup_bootmem() reserves memory from RAM start to the
kernel end. This prevents us from exploring ways to use the RAM below
(or before) the kernel start hence this patch updates setup_bootmem()
to only reserve memory from the kernel start to the kernel end.
Suggested-by: Mike
Currently, the setup_vm() does initial page table setup in one-shot
very early before enabling MMU. Due to this, the setup_vm() has to map
all possible kernel virtual addresses since it does not know size and
location of RAM. This means we have kernel mappings for non-existent
RAM and any buggy
This patchset implements two-stagged initial page table setup using fixmap
to avoid mapping non-existent RAM and also reduce high_memory consumed by
initial page tables.
The patchset is based on Linux-5.1-rc7 and tested on SiFive Unleashed board
and QEMU virt machine.
These patches can be found
On 01-05-19, 07:53, Pierre-Louis Bossart wrote:
> Standards such as the MIPI DisCo for SoundWire 1.0 specification
> assume the _ADR field is 64 bits.
>
> _ADR is defined as an "Integer" represented as 64 bits since ACPI 2.0
> released in 2002. The low levels already use _ADR as 64 bits, e.g. in
If the upper and lower layers use incompatible ACL formats, it is not
possible to copy the ACL xttr from one to the other, so overlayfs
cannot work with them.
This happens particularly with NFSv4 which uses system.nfs4_acl, and
ext4 which uses system.posix_acl_access.
If all ACLs actually make
On 02/05/19 3:11 AM, Tony Lindgren wrote:
Hi all,
Here are few fixes for the am335x d_can boot issue Sebastian reported for
Beaglebone.
Tested for AM437x-gp-evm RTC+DDR mode and DS0.
Also tried DS0 on Am335x beaglebone black.
For the above:
Tested-by: Keerthy
Regards,
Tony
Tony
If we want to set rate to 64000 on da7219, it fails and returns
"snd_pcm_hw_params: Invalid argument".
We should remove 64000 from support rate list because it is not
available.
Signed-off-by: Yu-Hsuan Hsu
---
sound/soc/codecs/da7219.c | 10 --
1 file changed, 8 insertions(+), 2
Hi Andreas,
On Wed, Mar 27, 2019 at 2:34 PM Andreas Schwab wrote:
>
> I have now found out that the ledtrig modules don't load automatically.
> I would have expected that the linux,default-trigger entries would cause
> the load of the corresponding ledtrig modules.
>
> But there is another
On Wed, May 01 2019, Amir Goldstein wrote:
> On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote:
>>
>> On Tue, Dec 06 2016, J. Bruce Fields wrote:
>>
>> > On Tue, Dec 06, 2016 at 02:18:31PM +0100, Andreas Gruenbacher wrote:
>> >> On Tue, Dec 6, 2016 at 11:08 AM, Miklos Szeredi wrote:
>> >> > On
On 05/02, Stephen Rothwell wrote:
> Hi Jaegeuk,
>
> After merging the f2fs tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/trace/define_trace.h:96,
> from include/trace/events/f2fs.h:1724,
> from
On Sat, 27 Apr 2019, at 02:27, Patrick Venture wrote:
> Fix up mixed declarations and code in aspeed_p2a_mmap.
>
> Tested: Verified the build had the error and that this patch resolved it
> and there were no other warnings or build errors associated with
> compilation of this driver.
>
>
On Wed, 01 May 2019 16:28:31 -0400
Steven Rostedt wrote:
> diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S
> index d309f30cf7af..50bbf4035baf 100644
> --- a/arch/x86/entry/entry_32.S
> +++ b/arch/x86/entry/entry_32.S
> @@ -1478,6 +1478,17 @@ ENTRY(int3)
> ASM_CLAC
>
On Wed, 1 May 2019 19:34:27 -0700
Eric Biggers wrote:
> > Call Trace:
> > smp_call_function_many+0x750/0x8c0 kernel/smp.c:434
> > smp_call_function+0x42/0x90 kernel/smp.c:492
> > on_each_cpu+0x31/0x200 kernel/smp.c:602
> > text_poke_bp+0x107/0x19b arch/x86/kernel/alternative.c:821
> >
On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote:
>
> On Tue, Dec 06 2016, J. Bruce Fields wrote:
>
> > On Tue, Dec 06, 2016 at 02:18:31PM +0100, Andreas Gruenbacher wrote:
> >> On Tue, Dec 6, 2016 at 11:08 AM, Miklos Szeredi wrote:
> >> > On Tue, Dec 6, 2016 at 12:24 AM, Andreas Grünbacher
> >>
Hi,
This set patches kobject to add a predicate function for determining the
initialization state of a kobject. Stripped down, the predicate is:
bool kobject_is_initialized(struct kobject *kobj)
{
return kobj->state_initialized
}
This is RFC because
Currently error return from kobject_init_and_add() is not followed by a
call to kobject_put(). This means there is a memory leak.
Add call to kobject_put() in error path of kobject_init_and_add().
Signed-off-by: Tobin C. Harding
---
kernel/livepatch/core.c | 12 +---
1 file changed, 9
On Sun, Apr 28, 2019 at 10:28:16PM +, Chris Packham wrote:
> One other problem that I encounter is the interaction between cs-gpio
> and SPI_MASTER_GPIO_SS. Having cs-gpio automatically sets SPI_CS_HIGH
> which has the undesired side-effect that now my real chip select is
> inverted. I
The patch
ASoC: da7219: Use clk_round_rate to handle enabled bclk/wclk case
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
Currently we use custom logic to track kobject initialization. Recently
a predicate function was added to the kobject API so we now no longer
need to do this.
Use kobject API to check for initialized state of kobjects instead of
using custom logic to track state.
Signed-off-by: Tobin C. Harding
On Mon, Apr 29, 2019 at 09:42:39PM +, Sowjanya Komatineni wrote:
> Hi Mark,
>
> I don't see below patches that I see as applied in latest linux-next.
> Can you please confirm if they are applied?
>
> Applied "spi: tegra114: fix PIO transfer" to the spi tree
> Applied "spi: expand mode
On Tue, Apr 30, 2019 at 06:23:21PM +0800, masonccy...@mxic.com.tw wrote:
> > It'd be much better to describe what the above actually means - what
> > changes have been made in the introduction of the MFD driver? It does
> > feel like there's not as much abstraction as I'd expect between the MFD
Currently the docstring for kobject_get_path() mentions 'kset'. The
kset is not used in the function callchain starting from this function.
Remove docstring reference to kset from the function kobject_get_path().
Signed-off-by: Tobin C. Harding
---
lib/kobject.c | 5 ++---
1 file changed, 2
A call to kobject_init() is required to be paired with a call to
kobject_put() in order to correctly free up the kobject. During cleanup
functions it would be useful to know if a kobject was initialized in
order to correctly pair the call to kobject_put(). For example this is
necessary if we
kernel-doc comments have a prescribed format. This includes parenthesis
on the function name. To be _particularly_ correct we should also
capitalise the brief description and terminate it with a period.
In preparation for adding/updating kernel-doc function comments clean up
the ones currently
On Sun, Apr 28, 2019 at 02:24:54AM +, S.j. Wang wrote:
> Add pm runtime support and move clock handling there.
> Close the clocks at suspend to reduce the power consumption.
>
> fsl_esai_suspend is replaced by pm_runtime_force_suspend.
> fsl_esai_resume is replaced by pm_runtime_force_resume.
On 02/05/2019 00:42, Colin Ian King wrote:
> Hi,
>
> Static analysis with Coverity picked up an issue in the following commit:
>
> commit 2bde9b3ec8bdf60788e9e2ce8c07a2f8d6003dbd
> Author: Cédric Le Goater
> Date: Thu Apr 18 12:39:41 2019 +0200
>
> KVM: Introduce a 'release' method
On Wed, May 01, 2019 at 07:36:05AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:baf76f0c slip: make slhc_free() silently accept an error p..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1407f57f20
>
On Mon, Apr 29, 2019 at 02:31:55PM +0200, Jorge Ramirez wrote:
> On 4/27/19 20:21, Mark Brown wrote:
> > Since the point of this change is AFAICT that this regulator only has a
> > single linear range it seems like it should just be able to use the
> > existing generic functions shouldn't it?
On 5/1/2019 12:22 PM, Kamal Dasu wrote:
> The oobregion->offset for large page nand parts was wrong, change
> fixes this error in calculation.
>
> Fixes: ef5eeea6e911 ("mtd: nand: brcm: switch to mtd_ooblayout_ops")
> Signed-off-by: Kamal Dasu
Reviewed-by: Florian Fainelli
--
Florian
The patch
ASoC: tlv320aic32x4: Remove set but not used variable 'mclk_rate'
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
The patch
regulator: vexpress: Get rid of struct vexpress_regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
ASoC: fsl_micfil: Remove set but not used variable 'osr'
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
spi: Clear SPI_CS_HIGH flag from bad_bits for GPIO chip-select
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
spi: stm32-qspi: manage the get_irq error case
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
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
spi: expand mode support
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 during
the next
The patch
ASoC: fsl_audmix: cache pdev->dev pointer
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
The patch
spi: stm32: return the get_irq error
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.1
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
The patch
spi: pxa2xx: Add support for Intel Comet Lake
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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
The patch
ASoC: Mediatek: MT8183: Fix build err while CONFIG_I2C set to module
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
The patch
spi: spi-mem: Fix build error without CONFIG_SPI_MEM
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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
spi: spi-mem: Make spi_mem_default_supports_op() static inline
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: pxa2xx: use a module softdep for dw_dmac
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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
The patch
ASoC: mpc5200_psc_i2s: Fix invalid license ID
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
The patch
ASoC: mpc5200_dma: Fix invalid license ID
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
The patch
spi: spi-mem: zynq-qspi: Fix build error on architectures missing
readsl/writesl
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
regulator: hi6xxx: Switch to SPDX identifier
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
dt-bindings: spi: spi-mt65xx: add support for MT8516
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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
spi: pxa2xx: fix SCR (divisor) calculation
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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
The patch
spi: atmel-quadspi: fix crash while suspending
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.1
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
regulator: vexpress: Switch to SPDX identifier
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: amd: acp3x: Make acp3x_dai_i2s_ops static
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
The patch
ASoC: atmel: tse850: Make some functions static
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
The patch
ASoC: sprd: Fix to use list_for_each_entry_safe() when delete items
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
ASoC: imx: fix fiq dependencies
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 during
The patch
ASoC: da7213: fix DAI_CLK_EN register bit overwrite
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.1
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: rt5645: fix a NULL pointer dereference
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
The patch
ASoC: cs43130: fix a NULL pointer dereference
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
The patch
ASoC: sprd: Fix return value check in sprd_mcdt_probe()
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: SOF: Intel: fix spelling mistake "incompatble" -> "incompatible"
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime
On Tue, Apr 30, 2019 at 10:01:18PM +0200, Saravanan Sekar wrote:
> Add support to output level control for the analog high power output
> drivers HPOUT and HPCOM.
>
> Signed-off-by: Saravanan Sekar
This doesn't build with current code:
CC sound/soc/codecs/tlv320aic3x.o
On Tue, Dec 06 2016, J. Bruce Fields wrote:
> On Tue, Dec 06, 2016 at 02:18:31PM +0100, Andreas Gruenbacher wrote:
>> On Tue, Dec 6, 2016 at 11:08 AM, Miklos Szeredi wrote:
>> > On Tue, Dec 6, 2016 at 12:24 AM, Andreas Grünbacher
>> > wrote:
>> >> 2016-12-06 0:19 GMT+01:00 Andreas Grünbacher
On Fri, Apr 26, 2019 at 06:42:23PM +0200, Paweł Chmiel wrote:
> From: Tomasz Figa
>
> This patch adds dt-bindings for Samsung OneNAND driver.
>
> Signed-off-by: Tomasz Figa
> Signed-off-by: Paweł Chmiel
> ---
> .../bindings/mtd/samsung-onenand.txt | 46 +++
> 1 file
02.05.2019 3:52, Dmitry Osipenko пишет:
> 02.05.2019 3:17, Rob Herring пишет:
>> On Wed, May 1, 2019 at 7:06 PM Dmitry Osipenko wrote:
>>>
>>> 30.04.2019 1:05, Rob Herring пишет:
On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote:
> Add device-tree binding for NVIDIA Tegra30
On Wed, 1 May 2019 22:36:50 +0200
Viktor Rosendahl wrote:
> This new option CONFIG_TRACE_CONSOLE_LATENCY will enable the latency
> tracers to trace the console latencies. Previously this has always been
> implicitely disabled. I guess this is because they are considered
> to be well known and
Hi Lukasz,
On 19. 5. 1. 오전 5:30, Lukasz Luba wrote:
> Hi Chanwoo,
>
> On 4/30/19 6:46 AM, Chanwoo Choi wrote:
>> On 19. 4. 19. 오후 11:19, Lukasz Luba wrote:
>>> The patch adds description for DT binding for a new Exynos5422 Dynamic
>>> Memory Controller device.
>>>
>>> Signed-off-by: Lukasz Luba
On Mon, Apr 29, 2019 at 09:16:08AM +, Adam Thomson wrote:
> On 27 April 2019 18:20, Mark Brown wrote:
> > Don't we need to validate that the rounded rate is actually viable for
> > the parameters we're trying to set here? If there's missing constraints
> > causing something to try to do
The increment operator of pointer in be32_to_cpu() is not explicitly.
It made the warning from clang:
drivers/power/supply/power_supply_core.c:674:36: error: multiple
unsequenced modifications to 'list' [-Werror,-Wunsequenced]
drivers/power/supply/power_supply_core.c:675:41: error: multiple
Hi Lukasz,
On 19. 5. 1. 오전 6:19, Lukasz Luba wrote:
> Hi Chanwoo,
>
> On 4/30/19 9:34 AM, Chanwoo Choi wrote:
>> Hi Lukasz,
>>
>> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
>>> This patch adds posibility to choose what type of data should be counted
>>> by the PPMU counter. Now the type comes
On 5/1/19 1:00 PM, Alex Williamson wrote:
Commit 0e7df22401a3 ("PCI: Add sysfs sriov_drivers_autoprobe to control
VF driver binding") allows the user to specify that drivers for VFs of
a PF should not be probed, but it actually causes pci_device_probe() to
return success back to the driver core
02.05.2019 3:17, Rob Herring пишет:
> On Wed, May 1, 2019 at 7:06 PM Dmitry Osipenko wrote:
>>
>> 30.04.2019 1:05, Rob Herring пишет:
>>> On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote:
Add device-tree binding for NVIDIA Tegra30 External Memory Controller.
The binding
Hi Jaegeuk,
After merging the f2fs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/trace/define_trace.h:96,
from include/trace/events/f2fs.h:1724,
from fs/f2fs/super.c:35:
include/trace/events/f2fs.h: In
On Fri, Apr 26, 2019 at 10:30:17AM +0200, Michal Vokáč wrote:
> Normally, the MPR121 controller uses separate interrupt line to notify
> the I2C host that a key was touched/released. To support platforms that
> can not use the interrupt line, polling of the MPR121 registers can be
> used.
Other
On Wed, May 1, 2019 at 2:27 AM Matteo Croce wrote:
>
> On Tue, Apr 30, 2019 at 11:25 PM Cong Wang wrote:
> >
> > On Mon, Apr 29, 2019 at 10:38 AM Matteo Croce wrote:
> > >
> > > When a matchall classifier is added, there is a small time interval in
> > > which tp->root is NULL. If we receive a
On Fri, 26 Apr 2019 08:26:17 +0530, Krishna Yarlagadda wrote:
> Add new compatible string and other fields used in pinctrl
> driver for Tegra194 in nvidia,tegra210-pinmux.txt
>
> Signed-off-by: Krishna Yarlagadda
> ---
> .../bindings/pinctrl/nvidia,tegra210-pinmux.txt| 43
>
On Fri, Apr 26, 2019 at 11:06:32AM +0900, Takao Orito wrote:
Needs a commit msg.
> Signed-off-by: Takao Orito
> ---
> .../devicetree/bindings/mmc/sdhci-milbeaut.txt | 35
> ++
> 1 file changed, 35 insertions(+)
> create mode 100644
On Thu, 25 Apr 2019 18:25:06 +0530, Manivannan Sadhasivam wrote:
> Add devicetree binding for Bitmain BM1880 SoC reset controller. This SoC
> has two reset controllers each controlling reset lines of different
> peripherals.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
On Tue, Apr 30, 2019 at 09:50:45AM +0530, Yash Shah wrote:
> On Fri, Apr 26, 2019 at 3:04 PM Sudeep Holla wrote:
> >
> > On Fri, Apr 26, 2019 at 11:20:17AM +0530, Yash Shah wrote:
> > > On Thu, Apr 25, 2019 at 3:43 PM Sudeep Holla wrote:
> > > >
> > > > On Thu, Apr 25, 2019 at 11:24:55AM +0530,
On Thu, Apr 25, 2019 at 09:45:54AM +0800, jojo_z...@126.com wrote:
> From: Jojo Zeng
>
> the comments which discribed the input parameters of of_match_device().
> the name is changed, so fix it.
>
> Signed-off-by: Jojo Zeng
> ---
> drivers/of/device.c | 2 +-
> 1 file changed, 1
> On May 1, 2019, at 2:04 PM, Bae, Chang Seok wrote:
>
>
>> On May 1, 2019, at 13:25, Andy Lutomirski wrote:
>>
>>
>>
>>> On May 1, 2019, at 1:21 PM, Bae, Chang Seok
>>> wrote:
>>>
>>>
> On May 1, 2019, at 11:01, Bae, Chang Seok
> wrote:
>
> On May 1, 2019, at
The QCS404 has a PCIe2 PHY and a Qualcomm PCIe controller, add these to
the platform dtsi and enable them for the EVB with the perst gpio
and analog supplies defined.
Reviewed-by: Niklas Cassel
Signed-off-by: Bjorn Andersson
---
The patch depends on the acceptance of:
Enabling PCIe requires several of the PCIe related resets from GCC, so
add them all.
Reviewed-by: Niklas Cassel
Acked-by: Stephen Boyd
Acked-by: Rob Herring
Signed-off-by: Bjorn Andersson
---
Changes since v2:
- Rebased patch
drivers/clk/qcom/gcc-qcs404.c | 7 +++
The QCS404 platform contains a PCIe controller of version 2.4.0 and a
Qualcomm PCIe2 PHY. The driver already supports version 2.4.0, for the
IPQ4019, but this support touches clocks and resets related to the PHY
as well, and there's no upstream driver for the PHY.
On QCS404 we must initialize the
Before introducing the QCS404 platform, which uses the same PCIe
controller as IPQ4019, migrate this to use the bulk clock API, in order
to make the error paths slighly cleaner.
Acked-by: Stanimir Varbanov
Reviewed-by: Niklas Cassel
Signed-off-by: Bjorn Andersson
---
Changes since v2:
-
The Qualcomm QCS404 platform contains a PCIe controller, add this to the
Qualcomm PCI binding document. The controller is the same version as the
one used in IPQ4019, but the PHY part is described separately, hence the
difference in clocks and resets.
Reviewed-by: Rob Herring
Signed-off-by:
This series adds support for the PCIe controller in the Qualcomm QCS404
platform.
Bjorn Andersson (3):
PCI: qcom: Use clk_bulk API for 2.4.0 controllers
dt-bindings: PCI: qcom: Add QCS404 to the binding
PCI: qcom: Add QCS404 PCIe controller support
1 - 100 of 465 matches
Mail list logo
