From: Denis Osterland
This patches addresses following problem:
rtc_allocate_device
devm_device_add_group <-- kernel oops / null pointer, because
sysfs entry does not yet exist
rtc_register_device
rc = devm_device_add_group
if (rc)
return rc; <-- forbidden to
changes since v4:
- fix 'souces' typo and change interrupt documentation
- change "isil,ev-evienb" type to int and do not touch bit if not present
- pass ISL1219_REG_EV_EVEN directly instead of assigning it to rc
- fix module build by adding EXPORT_SYMBOL to rtc_add_group(s)
- use kcalloc
-
From: Denis Osterland
Add support to disable event in pull-up.
Signed-off-by: Denis Osterland
---
drivers/rtc/rtc-isl1208.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-isl1208.c b/drivers/rtc/rtc-isl1208.c
index
From: Denis Osterland
Add support for "evdet" named interrupt source.
The check if i2c client irq matches evdet irq is needed
for the case that there is only one interrupt named "evdet".
In this case i2c client code handles this like an unnamed
interrupt souce and assigns the value.
From: Denis Osterland
The devicetree documentation for the ISL1219 device tree
binding is added with an short example. It is not a trivial
device, because it supports two interrupt sources.
Signed-off-by: Denis Osterland
---
.../devicetree/bindings/rtc/isil,isl1219.txt | 29
From: Michael Grzeschik
We add support for the ISL1219 chip that got an integrated tamper
detection function. This patch implements the feature by adding
an additional timestamp0 file to sysfs device path.
This file contains seconds since epoch, if an event occurred,
or is empty, if none
Hi!
> >> > >Please keep in mind that this is ABI documentation for the pattern file
> >> > >to be exposed by LED core, and not by the pattern trigger, that, as we
> >> > >agreed, will be implemented later. In this case, I'd go for
> >> >
> >> > Gosh, I got completely distracted by the recent
On Tue, 2018-07-24 at 09:46 +, Sven Schmitt wrote:
> Remove unused #defines.
This should be the title of the patch, "clean up" is too vague.
> --- a/drivers/soc/imx/gpc.c
> +++ b/drivers/soc/imx/gpc.c
> @@ -24,15 +24,11 @@
> #define GPC_PGC_CTRL_OFFS0x0
> #define GPC_PGC_PUPSCR_OFFS
Dmitry,
Can you temporarily disable config options which are causing this build error?
syzbot is failing to test next-20180723 and next-20180724 due to this problem.
By the way, ".config" at
https://syzkaller.appspot.com/bug?id=bd788040e839b85be53a030f219a2a1e4dc8acd2 is
failing becaus
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 arm_smmu_v3_x_pmcg_y where x
denotes the associated smmuv3 dev id(if any) and y
This adds an helper to retrieve the smmuv3 dev(if any) associated
with the PMCG node. This will be used in subsequent SMMUv3 PMU
driver patch to name the pmu device.
Signed-off-by: Shameer Kolothum
---
drivers/acpi/arm64/iort.c | 84 ---
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMU v3 PMU driver.
Signed-off-by: Neil Leeder
Signed-off-by: Hanjun Guo
Signed-off-by: Shameer Kolothum
---
drivers/acpi/arm64/iort.c | 95
From: Neil Leeder
Adds a new driver to support the SMMU v3 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 arm_smmu_v3_x_pmcg_y where x
denotes the associated
This adds support for MSI based counter overflow interrupt.
Signed-off-by: Shameer Kolothum
---
drivers/perf/arm_smmuv3_pmu.c | 105 +-
1 file changed, 84 insertions(+), 21 deletions(-)
diff --git a/drivers/perf/arm_smmuv3_pmu.c
On Tue, 2018-07-24 at 09:46 +, Sven Schmitt wrote:
> Use GPC_PGC_DOMAIN_* indexes consistent.
>
> Signed-off-by: Sven Schmitt
Reviewed-by: Leonard Crestez
On Di, 2018-07-24 at 00:23 +0800, Yu Chen wrote:
> Hi,
> On Mon, Jul 23, 2018 at 01:42:36PM +0200, Oliver Neukum wrote:
> > On Fr, 2018-07-20 at 12:25 +0200, Pavel Machek wrote:
> > > So your goal is to make hibernation compatible with kernel
> > > lockdown? Do your patches provide sufficient
On 24/07/18 12:06, Mark Brown wrote:
On Mon, Jul 23, 2018 at 04:54:02PM +0100, Srinivas Kandagatla wrote:
This patch adds bindings for wcd9335 audio codec which can support both SLIMbus
and I2S/I2C interface.
...
+Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
+It supports
Hi!
> Thanks for showing your thoughts. But I failed to compile your code,
> would you like to send out formal patches (Or only including software
> pattern, I will help to add hardware pattern part and do some testing
> with our driver)? Thanks.
Random thoughts:
I am not sure "struct
On 24/07/18 06:56, Vinod wrote:
On 23-07-18, 16:53, Srinivas Kandagatla wrote:
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC, supports
Qualcomm Technologies, Inc. (QTI) multimedia solutions, including
the MSM8996, MSM8976, and MSM8956 chipsets. It has in-build
in-built
The patch
ASoC: core: add support to snd_soc_dai_get_channel_map()
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: meson: axg-spdifout: select SND_PCM_IEC958
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
On Tue, 2018-07-24 at 09:46 +, Sven Schmitt wrote:
> imx6_pm_domain_power_off() reads iso and iso2sw from
> GPC_PGC_PUPSCR_OFFS
> which stores the power up delays.
> So use GPC_PGC_PDNSCR_OFFS for the correct delays.
>
> Signed-off-by: Sven Schmitt
Reviewed-by: Leonard Crestez
> ---
This is necessary to be able to include when
CONFIG_GENERIC_MSI_IRQ_DOMAIN is enabled. Without this, a build with
CONFIG_GENERIC_MSI_IRQ_DOMAIN fails with:
In file included from include/linux/kvm_host.h:20:0,
from arch/mips/kernel/asm-offsets.c:24:
>>
The patch
regulator: bd9571mwv: Make symbol 'dev_attr_backup_mode' static
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
This is necessary to be able to include when
CONFIG_GENERIC_MSI_IRQ_DOMAIN is enabled. Without this, a build with
CONFIG_GENERIC_MSI_IRQ_DOMAIN fails with:
In file included from drivers//ata/ahci.c:45:0:
>> include/linux/msi.h:226:10: error: unknown type name 'msi_alloc_info_t'; did
>> you
The definitions in arch/sparc/include/asm/msi.h are only used in
arch/sparc/mm/srmmu.c, so it makes sense to have them in the C file
directly.
In addition, having a custom arch/sparc/include/asm/msi.h prevents
from using the asm-generic version of this header, which is necessary
to be able to
On Tue, Jul 24, 2018 at 01:13:28PM +0200, Arnd Bergmann wrote:
> drivers/staging/rtl8188eu/include/odm.h uses an incorrect encoding
> for the '...' character in two comments, which makes it one of the
> few non-UTF-8 source files.
>
> This removes the odd characters and uses the same ASCII
On Tue, Jul 24, 2018 at 01:53:17PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 24, 2018 at 01:13:28PM +0200, Arnd Bergmann wrote:
> > drivers/staging/rtl8188eu/include/odm.h uses an incorrect encoding
> > for the '...' character in two comments, which makes it one of the
> > few non-UTF-8
On Tue, Jul 24, 2018 at 1:44 PM, Tetsuo Handa
wrote:
> Dmitry,
>
> Can you temporarily disable config options which are causing this build error?
> syzbot is failing to test next-20180723 and next-20180724 due to this problem.
Do you know what are these configs?
> By th
On 20/07/2018 21:17, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Fri, Jul 20, 2018 at 11:40 AM Neil Armstrong
> wrote:
>>
>> Add support the VID_PLL fully programmable divider used right after the
>> HDMI PLL clock source. It is used to achieve complex fractional division
>> with a programmble
Some randconfig builds fail in the mtk-eint driver:
drivers/pinctrl/mediatek/mtk-eint.c: In function 'mtk_eint_irq_handler':
drivers/pinctrl/mediatek/mtk-eint.c:324:2: error: implicit declaration of
function 'chained_irq_enter'; did you mean 'rcu_irq_enter'?
On Mon, Jul 23, 2018 at 04:54:05PM +0100, Srinivas Kandagatla wrote:
> +static inline int wcd_clsh_get_int_mode(struct wcd_clsh_ctrl *ctrl,
> + int clsh_state)
> +{
> + int mode;
> +
> + if ((clsh_state != WCD_CLSH_STATE_EAR) &&
> + (clsh_state
On Sat, Jul 21, 2018 at 01:17:58PM +0100, Mark Railton wrote:
> Removed a commented out case statement
>
> Signed-off-by: Mark Railton
> ---
> drivers/staging/pi433/rf69.c | 3 ---
> 1 file changed, 3 deletions(-)
Where is patch 1/2 of this series?
And this patch doesn't apply at all, what
On Mon, Jul 23, 2018 at 11:54:29AM +0100, Laurence Rochfort wrote:
> Fix sparse warning: Using plain integer as NULL pointer
>
> Signed-off-by: Laurence Rochfort
> ---
> drivers/staging/most/dim2/dim2.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This patch does not apply to my
On Tue, 2018-07-24 at 12:09 +0200, Lucas Stach wrote:
> Am Montag, den 23.07.2018, 12:37 + schrieb Leonard Crestez:
> > On Mon, 2018-07-23 at 11:38 +0200, Lucas Stach wrote:
> > > Am Freitag, den 20.07.2018, 15:47 +0300 schrieb Leonard Crestez:
> > > > On imx7d the pcie-phy power domain is
On 20/07/2018 21:00, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Fri, Jul 20, 2018 at 11:40 AM Neil Armstrong
> wrote:
>>
>> Add the clocks entries used in the video clock path, the clock path
>> is doubled to permit having different synchronized clocks for different
>> parts of the video
Thanks for the review!
On 24/07/18 12:59, Mark Brown wrote:
On Mon, Jul 23, 2018 at 04:54:05PM +0100, Srinivas Kandagatla wrote:
+static inline int wcd_clsh_get_int_mode(struct wcd_clsh_ctrl *ctrl,
+ int clsh_state)
+{
+ int mode;
+
+ if
Hi!
> > > Yes. But you are objecting to encryption in kernel space at all,
> > > aren't you?
> >
> > I don't particulary love the idea of doing hibernation encryption in
> > the kernel, correct.
> >
> > But we have this weird thing called secure boot, some people seem to
> > want. So we may
On Tue, 2018-07-24 at 11:34 +0200, Arnd Bergmann wrote:
> On 32-bit targets, size_t is often 'unsigned int', so printing it as %lu
> causes a warning:
>
> drivers/fsi/fsi-master-ast-cf.c: In function 'fsi_master_acf_read':
> drivers/fsi/fsi-master-ast-cf.c:609:23: error: format '%u' expects
On 24/07/2018 14:04, Neil Armstrong wrote:
> On 20/07/2018 21:00, Martin Blumenstingl wrote:
>> Hi Neil,
>>
>> On Fri, Jul 20, 2018 at 11:40 AM Neil Armstrong
>> wrote:
>>>
>>> Add the clocks entries used in the video clock path, the clock path
>>> is doubled to permit having different
Fix the following sparse error:
drivers/gpio/gpio-ath79.c:54:16: error: return expression in void function
Signed-off-by: zhong jiang
---
drivers/gpio/gpio-ath79.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-ath79.c b/drivers/gpio/gpio-ath79.c
index
Not all VMAs allocated with vm_area_alloc(). Some of them allocated on
stack or in data segment.
The new helper can be use to initialize VMA properly regardless where
it was allocated.
Signed-off-by: Kirill A. Shutemov
---
include/linux/mm.h | 6 ++
kernel/fork.c | 6 ++
2 files
Make sure to initialize all VMAs properly, not only which comes from
vm_area_cachep.
Signed-off-by: Kirill A. Shutemov
---
arch/arm/kernel/process.c| 1 +
arch/arm/mach-rpc/ecard.c| 2 +-
arch/arm64/include/asm/tlb.h | 4 +++-
arch/arm64/mm/hugetlbpage.c | 7 +--
Fix crash found by syzkaller.
Build on top of Linus' changes in 4.18-rc6.
Andrew, could you please drop mm-drop-unneeded-vm_ops-checks-v2.patch for
now. Infiniband drivers have to be fixed first.
Kirill A. Shutemov (3):
mm: Introduce vma_init()
mm: Use vma_init() to initialize VMAs on stack
vma_is_anonymous() relies on ->vm_ops being NULL to detect anonymous
VMA. This is unreliable as ->mmap may not set ->vm_ops.
False-positive vma_is_anonymous() may lead to crashes:
next 8801ce5e7040 prev 8801d20eca50 mm 88019c1e13c0
prot 27 anon_vma 88019680cdd8
Hi Mani,
Patch title should be dmaengine: ... Please always use the apt tags and
one can find them using git log
On 23-07-18, 09:47, Manivannan Sadhasivam wrote:
> Add devicetree binding for Actions Semi Owl SoCs DMA controller.
It would help for review to describe the controller here
>
>
On 24.07.2018 09:25, Michal Hocko wrote:
> On Mon 23-07-18 19:20:43, David Hildenbrand wrote:
>> On 23.07.2018 14:30, Michal Hocko wrote:
>>> On Mon 23-07-18 13:45:18, Vlastimil Babka wrote:
On 07/20/2018 02:34 PM, David Hildenbrand wrote:
> Dumping tools (like makedumpfile) right now
Hi Vinod,
Am 24.07.2018 um 14:16 schrieb Vinod:
> Patch title should be dmaengine: ... Please always use the apt tags and
> one can find them using git log
Do you mean dt-bindings: dmaengine: ...? Because this is clearly a DT
binding and not a driver patch.
Regards,
Andreas
--
SUSE Linux
Sorry, I meant to write "minor revamp" in the subject line here as
Apalis TK1 was already in quite good a shape but this are still some
worthy improvements (;-p).
On Tue, 2018-07-24 at 12:42 +0200, Marcel Ziswiler wrote:
> This series is a minor overhaul for the Toradex Apalis TK1 system on
>
On 07/24/2018 01:19 PM, Michal Hocko wrote:
>> When creating a crashdump, I definitely need the pages containing memmap
>> included in the dump, so I can inspect the struct pages. But this is a
>> bit recursive issue, so I'll try making it clearer:
>>
>> 1) there are kernel pages with data (e.g.
The schedutil governor maps utilization values to frequencies by applying
a 25% margin. Since this sort of mapping mechanism can be needed by other
users (i.e. EAS), factor the utilization-to-frequency mapping code out
of schedutil and move it to include/linux/sched/cpufreq.h to avoid code
The existing scheduling domain hierarchy is defined to map to the cache
topology of the system. However, Energy Aware Scheduling (EAS) requires
more knowledge about the platform, and specifically needs to know about
the span of Frequency Domains (FD), which do not always align with
caches.
To
The Energy Aware Scheduler (EAS) based on Morten Rasmussen's posting on
LKML [1] is currently part of the AOSP Common Kernel and runs on today's
smartphones with Arm's big.LITTLE CPUs. This series implements a new and
largely simplified version of EAS based on an Energy Model (EM) of the
platform
Expose the Energy Model (read-only) of all frequency domains in sysfs
for convenience. To do so, add a kobject to the CPU subsystem under the
umbrella of which a kobject for each frequency domain is attached.
The resulting hierarchy is as follows for a platform with two frequency
domains for
In order to ensure a minimal performance impact on non-energy-aware
systems, introduce a static_key guarding the access to Energy-Aware
Scheduling (EAS) code.
The static key is set iff all the following conditions are met for at
least one root domain:
1. all online CPUs of the root domain are
Add another member to the family of per-cpu sched_domain shortcut
pointers. This one, sd_ea, points to the lowest level at which energy
aware scheduling should be used.
Generally speaking, the largest opportunity to save energy via scheduling
comes from a smarter exploitation of heterogeneous
Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a
Schedutil aggregates the PELT signals of CFS, RT, DL and IRQ in order
to decide which frequency to request. Energy Aware Scheduling (EAS)
needs to be able to predict those requests to assess the energy impact
of scheduling decisions. However, the PELT signals aggregation is only
done in schedutil
By default, arch_scale_cpu_capacity() is only visible from within the
kernel/sched folder. Relocate it to include/linux/sched/topology.h to
make it visible to other clients needing to know about the capacity of
CPUs, such as the Energy Model framework.
Cc: Ingo Molnar
Cc: Peter Zijlstra
In preparation for the definition of an energy-aware wakeup path,
introduce a helper function to estimate the consequence on system energy
when a specific task wakes-up on a specific CPU. compute_energy()
estimates the capacity state to be reached by all frequency domains and
estimates the
Energy Aware Scheduling (EAS) starts when the scheduling domains are
built if the Energy Model (EM) is present. However, in the typical case
of Arm/Arm64 systems, the EM is provided after the scheduling domains
are first built at boot time, which results in EAS staying disabled.
Fix this issue by
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
energy-efficient task distribution without depriving any tasks. When
In preparation for the introduction of a new root domain flag which can
be set during load balance (the 'overutilized' flag), clean-up the set
of parameters passed to update_sg_lb_stats(). More specifically, the
'local_group' and 'local_idx' parameters can be removed since they can
easily be
***
* This patch illustrates the usage of the newly introduced Energy *
* Model framework and isn't supposed to be merged as-is. *
***
The Energy Model
If an Energy Model (EM) is available and if the system isn't
overutilized, re-route waking tasks into an energy-aware placement
algorithm. The selection of an energy-efficient CPU for a task
is achieved by estimating the impact on system-level active energy
resulting from the placement of the task
Am Dienstag, den 24.07.2018, 12:04 + schrieb Leonard Crestez:
> On Tue, 2018-07-24 at 12:09 +0200, Lucas Stach wrote:
> > Am Montag, den 23.07.2018, 12:37 + schrieb Leonard Crestez:
> > > On Mon, 2018-07-23 at 11:38 +0200, Lucas Stach wrote:
> > > > Am Freitag, den 20.07.2018, 15:47 +0300
From: Leon Romanovsky
Signed-off-by: Leon Romanovsky
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c79f306a936a..6be664ed0527 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5444,6 +5444,7 @@ F:drivers/iommu/exynos-iommu.c
EZchip
On Fri, Jul 20, 2018 at 6:38 PM, Daniel Kurtz wrote:
> Sounds reasonable. How about:
>
> - /* Clear interrupt.
> -* We must read the pin register again, in case the
> -* value was changed while executing
> -
> On Fri, 2018-07-20 at 11:16 +0530, Udit Agarwal wrote:
> > Secure keys are derieved using CAAM crypto block.
> >
> > Secure keys derieved are the random number symmetric keys from CAAM.
> > Blobs corresponding to the key are formed using CAAM. User space will
> > only be able to view the blob of
On 24/07/18 12:31, Dmitry Osipenko wrote:
On Monday, 23 July 2018 16:05:21 MSK Dmitry Osipenko wrote:
On Friday, 20 July 2018 16:45:30 MSK Ben Dooks wrote:
The 2D and 3D clocks have an IDLE field in bits 15:8 so add these
clocks by making a 2D and 3D mux, and split the divider into the
On 24.07.2018 14:22, Vlastimil Babka wrote:
> On 07/24/2018 01:19 PM, Michal Hocko wrote:
>>> When creating a crashdump, I definitely need the pages containing memmap
>>> included in the dump, so I can inspect the struct pages. But this is a
>>> bit recursive issue, so I'll try making it clearer:
On 21.07.2018 00:41, Laura Abbott wrote:
> This adds support for the STACKLEAK gcc plugin to arm64 by implementing
> stackleak_check_alloca(), based heavily on the x86 version, and adding the
> two helpers used by the stackleak common code: current_top_of_stack() and
> on_thread_stack(). The stack
On Tuesday, 24 July 2018 15:24:34 MSK Marcel Ziswiler wrote:
> Sorry, I meant to write "minor revamp" in the subject line here as
> Apalis TK1 was already in quite good a shape but this are still some
> worthy improvements (;-p).
>
> On Tue, 2018-07-24 at 12:42 +0200, Marcel Ziswiler wrote:
>
Hi!
On Sun, Jul 22, 2018 at 09:16:49PM +0530, Akash Gajjar wrote:
> This board has a 128M SPI flash. add spi flash support in device tree.
>
> Tested on pine64 LTS.
>
> Signed-off-by: Akash Gajjar
The author email should match the one in the SoB, and the prefix of
your commit title should be
Add TODDR and FRDDR audio fifos of the AXG SoC.
These fifos are the capture and playback memory interfaces of audio
subsystem of the AXG.
Signed-off-by: Jerome Brunet
---
Kevin,
As you will see below, this patch depends on the ARB reset bindings which
have been accepted by Philip recently.
The usb power regulator is supplied by the vcc 5v regulator and
controlled by a GPIO. This will be needed to enable usb.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git
Enable the audio devices on the s400.
Signed-off-by: Jerome Brunet
---
.../arm64/boot/dts/amlogic/meson-axg-s400.dts | 72 +++
1 file changed, 72 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
index
Add the sound card of the s400. With it the following interface
should be working:
* Lineout
* Daugther card speaker 1 (same output as lineout)
* Linein
* SPDIF output
Signed-off-by: Jerome Brunet
---
Compared to what is actually available on the platform, the following
is not provided
Add the SPDIF output device of the axg audio subsystem
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
index
Add the SPDIF playback codec to the axg s400 board
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
index
This regulator is controlled by a GPIO and supplies various devices
on the board, such as the lineout codec, the usb supply or the lcd
controller.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git
The main purpose of this patchset is to add the audio devices on amlogic's
AXG SoCs.
Some codecs require some power supplies. This is why the 3 first patches
deal with the S400 power supplies, even if some are not related to audio.
In term of dependency, apart from the clock bindings you have
Add the devices reponsible for managing the i2s/tdm clocks and pads
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 33 ++
1 file changed, 33 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
Add the es7241 analog to digital converter which is fed by the
lienin jack of the s400
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
Add the tdm devices responsible for serializing audio samples
for i2s/tdm interfaces
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 42 ++
1 file changed, 42 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
Add the tdm devices responsible for decoding the data provided
through audio serial interface.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 56 ++
1 file changed, 56 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
Add the es7154 digital to analog converter which supplies the
lienout jack of the s400
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
Add the parent supply of the s400 power supplies.
Also add 'regulator-always-on' property on the regulators which can't
be disabled
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9 +
1 file changed, 9 insertions(+)
diff --git
Add the audio memory arbiter which control the access of the audio
fifos to the DDR.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
On Mon, Jul 23, 2018 at 06:09:54PM +0200, stevenvandenbrandenst...@gmail.com
wrote:
> From: Steven Vanden Branden
>
> Add mali gpu node to sun4i a10 platforms.
> Tested with offscreen rendering with lima mesa (freedesktop gitlab)
>
> Signed-off-by: Steven Vanden Branden
Applied (while
On Tue, Jul 24, 2018 at 12:15:22PM +0200, Emmanuel Vadot wrote:
> The SID controller on H5 look the same as the one present in the A64.
> But in case we find some difference one day at a compatible string
> of it's own and a fallback to the A64 one.
>
> Signed-off-by: Emmanuel Vadot
> ---
>
On Tue, Jul 24, 2018 at 12:15:21PM +0200, Emmanuel Vadot wrote:
> The H5 SoC have a SID controller that looks like the one in A64, but
> in case we find some difference in the futur at a binding for it.
>
> Signed-off-by: Emmanuel Vadot
The prefix in your commit title should start with
Hello Dmitry,
On Wed, 4 Jul 2018 16:21:58 +
Dmitry Torokhov wrote:
> Hi Mylène,
>
> On Tue, Jul 03, 2018 at 11:43:07AM +0200, Mylène Josserand wrote:
> > Hello,
> >
> > Here is a V6 series to add the driver of the touchscreen Cypress,
> > TrueTouch Generation 5.
> > Based on v4.18-rc3.
>
iput() ends up calling ->evict() on new inode, which is not yet initialized
by owning fs. So use destroy_inode() instead.
Add to sb->s_inodes list only if inode is not in I_CREATING state (meaning
that it wasn't allocated with new_inode(), which already does the
insertion).
Reported-by: Al Viro
On Tue, Jul 24, 2018 at 01:13:13PM +0200, Ingo Molnar wrote:
>
> * Mark Rutland wrote:
>
> > On Tue, Jul 24, 2018 at 11:20:36AM +0200, Peter Zijlstra wrote:
> > > On Tue, Jul 24, 2018 at 09:15:18AM +0200, Ingo Molnar wrote:
> > > >
> > > > * Mark Rutland wrote:
> > > >
> > > > > From: Peter
On Tue 24-07-18 14:22:06, Vlastimil Babka wrote:
> On 07/24/2018 01:19 PM, Michal Hocko wrote:
> >> When creating a crashdump, I definitely need the pages containing memmap
> >> included in the dump, so I can inspect the struct pages. But this is a
> >> bit recursive issue, so I'll try making it
Hello,
On Fri, 20 Jul 2018 07:43:55 -0600
Rob Herring wrote:
> On Wed, Jul 18, 2018 at 08:27:17PM +0200, Mylène Josserand wrote:
> > Add the support of regulator to use it as VCC source.
> >
> > Signed-off-by: Mylène Josserand
> > ---
> > .../bindings/input/touchscreen/edt-ft5x06.txt |
On 24-07-18, 14:19, Andreas Färber wrote:
> Hi Vinod,
>
> Am 24.07.2018 um 14:16 schrieb Vinod:
> > Patch title should be dmaengine: ... Please always use the apt tags and
> > one can find them using git log
>
> Do you mean dt-bindings: dmaengine: ...? Because this is clearly a DT
> binding and
somehow this got stuck so sending again...
On 24-07-18, 18:16, Vinod wrote:
> On 23-07-18, 09:47, Manivannan Sadhasivam wrote:
>
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
>
On 24-07-18, 13:09, Paul Cercueil wrote:
> Hi,
>
> Le lun. 23 juil. 2018 à 19:58, Paul Burton a écrit :
> > Hi Paul & Vinod,
> >
> > On Sat, Jul 21, 2018 at 01:06:25PM +0200, Paul Cercueil wrote:
> > > This is the version 3 of my jz4780-dma driver update patchset.
> > >
> > > Apologies to
901 - 1000 of 1482 matches
Mail list logo
