On 19/07/2016 16:23, Sebastian Frias wrote:
>
I don't think there's supposed to be an empty line at the beginning of
the patch. I don't know whether 'git am' knows to zap the spurious line.
> 3) The file is called 'irq-tango_v4.c' but I think it should match the
> compatible string, so I was thi
Marc Z pointed out that posting partial series is not ideal.
Collect last-minute fixups into a single patch series.
- Bump series to v9 to avoid any ambiguity
- Add Rob's Ack on patch 1
Marc Gonzalez (3):
PCI: Add DT binding for tango PCIe controller
PCI: Add tango PCIe host bridge su
The MSI controller in Tango supports 256 message-signaled interrupts,
and a single doorbell address.
Signed-off-by: Marc Gonzalez
---
drivers/pci/host/pcie-tango.c | 226 ++
1 file changed, 226 insertions(+)
diff --git a/drivers/pci/host/pcie-tango.c b
This driver is required to work around several hardware bugs
in the PCIe controller.
NB: Revision 1 does not support legacy interrupts, or IO space.
Signed-off-by: Marc Gonzalez
---
drivers/pci/host/Kconfig | 8 +++
drivers/pci/host/Makefile | 1 +
drivers/pci/host/pcie-tango.c
Binding for the Sigma Designs SMP8759 SoC.
Acked-by: Rob Herring
Signed-off-by: Marc Gonzalez
---
.../devicetree/bindings/pci/tango-pcie.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/tango-pcie.txt
diff
On 19/06/2017 16:50, Marc Gonzalez wrote:
> On 07/06/2017 10:19, Marc Gonzalez wrote:
>
>> On 31/05/2017 15:33, Marc Gonzalez wrote:
>>
>>> +static int tango_pcie_probe(struct platform_device *pdev)
>>> +{
>>> + int ret = -EINVAL;
>>>
Hello BDFL,
I am writing to you directly because Russell has bluntly stated (paraphrased)
"Send your patches to Linus; it's his kernel, and he has the final say." which
is his diplomatic way of telling me to fsck off.
Basically, I want to improve the accuracy of clock-based delays, in order to
im
On 01/11/2017 18:53, Alan Cox wrote:
> On Tue, 31 Oct 2017 17:15:34 +0100
>
>> Therefore, users are accustomed to having delays be longer (within a
>> reasonable margin).
>> However, very few users would expect delays to be *shorter* than requested.
>
> If your udelay can be under by 10% then ju
On 01/11/2017 10:26, Russell King - ARM Linux wrote:
> On Tue, Oct 31, 2017 at 05:23:19PM -0700, Doug Anderson wrote:
>
>> On Tue, Oct 31, 2017 at 10:45 AM, Linus Torvalds wrote:
>>
>>> So I'm very much open to udelay improvements, and if somebody sends
>>> patches for particular platforms to do p
On 01/11/2017 20:09, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 12:03 PM, Marc Gonzalez wrote:
>
>> By default, ndelay is implemented in terms of udelay.
>
> That's very much *NOT* the case.
>
> Yes, there is a *fallback* for when somebody doesn't do ndelay
On 13/10/2017 10:34, Masahiro Yamada wrote:
> 2017-10-04 20:05, Marc Gonzalez wrote:
>
>> On 29/09/2017 16:33, Masahiro Yamada wrote:
>>
>>> tango_nand.c is the only driver that sets NAND_WAIT_TCCS.
>>>
>>> Now, there is completely no delay when re
Date: Tue, 6 Oct 2015 16:49:28 +0200
Subject: [PATCH] clocksource: Sigma Designs Tango 27 MHz xtal
Sigma Designs Tango platforms provide a 27 MHz crystal oscillator.
Use it for clocksource, sched_clock, and delay_timer.
Signed-off-by: Marc Gonzalez
---
drivers/clocksource/Makefile | 1
Hello everyone,
On 07/10/2015 01:09, Daniel Lezcano wrote:
> On 10/06/2015 05:10 PM, Marc Gonzalez wrote:
>> Date: Tue, 6 Oct 2015 16:49:28 +0200
>> Subject: [PATCH] clocksource: Sigma Designs Tango 27 MHz xtal
>
> Fix the patch format.
OK.
> Subject is clocksource/dri
On 07/10/2015 11:47, Daniel Lezcano wrote:
> On 10/07/2015 10:23 AM, Marc Gonzalez wrote:
>> Daniel Lezcano wrote:
>>
>>> static u64 *notrace* read_sched_clock(void)
>>
>> What about read_clocksource? and read_xtal_counter?
>
> See commit 89e
Sigma Designs Tango platforms provide a 27 MHz crystal oscillator.
Use it for clocksource, sched_clock, and delay_timer.
Signed-off-by: Marc Gonzalez
---
AFAICS, clocksource_register_hz does not report failures via its
return value (always 0) but writes warnings to stdout?
Open question: can I
On 07/10/2015 14:31, Daniel Lezcano wrote:
> On 10/07/2015 01:35 PM, Marc Gonzalez wrote:
>> Sigma Designs Tango platforms provide a 27 MHz crystal oscillator.
>> Use it for clocksource, sched_clock, and delay_timer.
>>
>> Signed-off-by: Marc Gonzalez
>> ---
&
On 22/10/2015 16:02, Mans Rullgard wrote:
> This adds a binding for the Aurora VLSI NB8800 Ethernet controller
> using the "aurora,nb8800" compatible string. When used in Sigma
> Designs chips a few additional control registers are available.
> This variant is indicated by the "sigma,smp8640-ethe
On 23/10/2015 15:41, Måns Rullgård wrote:
> Marc Gonzalez wrote:
>
>> On 22/10/2015 16:02, Mans Rullgard wrote:
>>
>>> This adds a binding for the Aurora VLSI NB8800 Ethernet controller
>>> using the "aurora,nb8800" compatible string. When us
On 23/10/2015 15:41, Måns Rullgård wrote:
> Marc Gonzalez wrote:
>
>> On 22/10/2015 16:02, Mans Rullgard wrote:
>>
>>> This adds a binding for the Aurora VLSI NB8800 Ethernet controller
>>> using the "aurora,nb8800" compatible string. When us
On 26/10/2015 13:05, Måns Rullgård wrote:
> Marc Gonzalez writes:
>
>> On 23/10/2015 15:41, Måns Rullgård wrote:
>>
>>> Marc Gonzalez wrote:
>>>
>>>> On 22/10/2015 16:02, Mans Rullgard wrote:
>>>>
>>>>> This adds a bin
On 26/10/2015 14:54, Måns Rullgård wrote:
> Let's try something else:
>
> Device trees list the exact chip, the oldest chip with the same
> features, and the oldest compatible chip. From the sound of things,
> that means the smp8759 should use "sigma,smp8759-ethernet",
> "sigma,smp8910-ethernet"
On 20/04/2017 16:24, Marc Gonzalez wrote:
> This patch was split in two, to ease review of two orthogonal
> parts (MSI controller and host bridge). NB: the patch is
> just split in two where host bridge support starts.
>
> Changes from v3 to v4
>
> In the MSI part:
> -
On 30/11/2018 09:12, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-11-29 23:24:20)
>
>> On Thu 29 Nov 23:05 PST 2018, Stephen Boyd wrote:
>>
>>> Quoting Bjorn Andersson (2018-11-29 22:52:57)
>>>
Keep the two clocks enabled, so that the platform passes
clk_disable_unused().
>>>
On 30/11/2018 07:52, Bjorn Andersson wrote:
> Drop the halt check of the UFS symbol clocks, in accordance with other
> platforms. This makes clk_disable_unused() happy and makes it possible
> to turn the clocks on again without an error.
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/clk/qc
On 30/11/2018 11:55, Marc Gonzalez wrote:
> On 30/11/2018 07:52, Bjorn Andersson wrote:
>
>> Drop the halt check of the UFS symbol clocks, in accordance with other
>> platforms. This makes clk_disable_unused() happy and makes it possible
>> to turn the clocks o
On 09/11/2018 01:54, Marc Gonzalez wrote:
> Hello ARM maintainers,
>
> v3: Keep CRYPTO_DEV_FSL_DPAA2_CAAM in patch 7/9
>
> v2: Improve commit message for a few patches
>
> The set of Kconfig options slowly changes with every kernel version.
> This patch series regener
On 06/12/2018 23:11, Jeffrey Hugo wrote:
> Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
> for clients to vote on.
>
> Signed-off-by: Jeffrey Hugo
> ---
> v2
> -fix compatible ordering nits per Stephen
>
> .../devicetree/bindings/clock/qcom,rpmcc.txt | 1 +
> dri
On 06/12/2018 23:11, Jeffrey Hugo wrote:
> Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
> for clients to vote on.
>
> Signed-off-by: Jeffrey Hugo
> ---
> v2
> -fix compatible ordering nits per Stephen
>
> .../devicetree/bindings/clock/qcom,rpmcc.txt | 1 +
> dri
On 03/12/2018 19:33, Bjorn Andersson wrote:
> Disabling gcc_hmss_dvm_bus_clk and gcc_lpass_at_clk causes the board to
> lock up, and by that preventing the kernel to boot without
> clk_ignore_unused.
>
> gcc_hmss_dvm_bus_clk is marked always-on downstream, but not referenced,
> and gcc_lpass_at_c
PINCTRL_MTK_MOORE to
keep PINCTRL_MT7622, and adding FSL_MC_BUS and FSL_MC_DPIO to
keep CRYPTO_DEV_FSL_DPAA2_CAAM.
Marc Gonzalez (9):
arm64: defconfig: Regenerate for v4.20
arm64: defconfig: Drop ARM_BIG_LITTLE_CPUFREQ
arm64: defconfig: Drop NF_CONNTRACK_IPV{4,6}
arm64: defconfig: Drop
Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
dropped ARM_BIG_LITTLE_CPUFREQ support for ARM64, so remove it from
the defconfig.
Acked-by: Viresh Kumar
Acked-by: Sudeep Holla
Acked-by: Mark Rutland
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfi
Run the platform defconfig through kbuild, and handle the trivial case
where options merely move around.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 90 ++--
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/arch/arm64
Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code") made
USB_CHIPIDEA select USB_ULPI_BUS, and removed USB_CHIPIDEA_ULPI.
Reviewed-by: Fabio Estevam
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm
Commit a0ae2562c6c4 ("netfilter: conntrack: remove l3proto abstraction")
folded NF_CONNTRACK_IPV4 and NF_CONNTRACK_IPV6 into NF_CONNTRACK.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/
Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
which is not set. Enable FSL_MC_BUS, and build FSL_MC_DPIO and
CRYPTO_DEV_FSL_DPAA2_CAAM as modules.
Signed-off-by: Marc Gonzalez
---
arch/arm
Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that
implements the generic pinctrl dt-bindings") made PINCTRL_MT7622
depend on PINCTRL_MTK_MOORE.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_ROCKCHIP_I2S
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 725b9471b21c..8e181cca0a05 100644
--- a/arch/arm64/configs
SCSI_UFS_HISI depends on SCSI_UFSHCD_PLATFORM=m
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 2662f83c481c..2e173978eef8 100644
--- a/arch/arm64
SND_SOC_RK3399_GRU_SOUND selects SND_SOC_DA7219, SND_SOC_MAX98357A,
SND_SOC_RT5514, SND_SOC_RT5514_SPI.
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_RT5645.
SND_SOC_RL6231 is pulled in for SND_SOC_RT5514 and SND_SOC_RT5645.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 6
On 09/11/2018 14:03, Matthias Brugger wrote:
> On 09/11/2018 02:03, Marc Gonzalez wrote:
>
>> Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that
>> implements the generic pinctrl dt-bindings") made PINCTRL_MT7622
>> depend on PINCTRL_MTK_MOORE.
On 10/11/2018 09:57, Arnd Bergmann wrote:
> On Thu, Nov 8, 2018 at 10:36 AM Sudeep Holla wrote:
>>
>> On Wed, Nov 07, 2018 at 11:39:42PM +0100, Marc Gonzalez wrote:
>>> Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
>>> dropp
_clk is
> initialized by rpmcc.
>
> Signed-off-by: Jeffrey Hugo
> ---
> drivers/clk/qcom/gcc-msm8998.c | 14 --
> 1 file changed, 14 deletions(-)
Reviewed-by: Marc Gonzalez
Regards.
On 18/12/2018 08:42, Kalle Valo wrote:
> Amit Kucheria wrote:
>
>> Several drivers didn't have a specific maintainer (other than the
>> subsystem maintainer). Switch to using the 'qcom' and 'msm' regex
>> patterns to capture all of them and add exceptions to the couple of
>> drivers that contain
On 13/12/2018 07:51, Olof Johansson wrote:
> I've applied the patches from the series that were still needed. When
> re-running savedefconfig as part of patch 1, several of them were no longer
> applicable.
FWIW, Arnd had suggested that the first patch should only deal with the
trivial case (movi
; -F: arch/arm/boot/dts/qcom-*.dts
> -F: arch/arm/boot/dts/qcom-*.dtsi
> -F: arch/arm/mach-qcom/
> -F: arch/arm64/boot/dts/qcom/*
> +N: qcom
> +N: msm
> +X: drivers/rtc/rtc-msm6242.c
> +X: drivers/net/wireless/broadcom/brcm80211/brcmsmac/
I would exclude all of drivers/net/wireless/broadcom
Aside from that trivial issue,
Reviewed-by: Marc Gonzalez
Regards.
The private copy of readl_poll_timeout is no longer needed.
Use the implementation in iopoll.h instead.
Signed-off-by: Marc Gonzalez
---
drivers/phy/qualcomm/phy-qcom-ufs-i.h | 19 +--
1 file changed, 1 insertion(+), 18 deletions(-)
diff --git a/drivers/phy/qualcomm/phy-qcom
SND_SOC_RK3399_GRU_SOUND selects SND_SOC_DA7219, SND_SOC_MAX98357A,
SND_SOC_RT5514, SND_SOC_RT5514_SPI.
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_RT5645.
SND_SOC_RL6231 is pulled in for SND_SOC_RT5514 and SND_SOC_RT5645.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 6
Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
which is not set.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_ROCKCHIP_I2S
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 725b9471b21c..8e181cca0a05 100644
--- a/arch/arm64/configs
SCSI_UFS_HISI depends on SCSI_UFSHCD_PLATFORM=m
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e4957df18f23..75d5ed7ea53d 100644
--- a/arch/arm64
Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code")
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 58741c07a6ef..6fe418d72337 100644
--- a/
Commit a0ae2562c6c4 ("netfilter: conntrack: remove l3proto abstraction")
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 8d6878c1e794..58741c07a6ef 10
Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that implements
the generic pinctrl dt-bindings")
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm
Run the platform defconfig through kbuild, and handle the trivial case
where options merely move around.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 90 ++--
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/arch/arm64/configs
Hello ARM maintainers,
The set of Kconfig options slowly changes with every kernel version.
This patch series regenerates the arm64 defconfig for v4.20
No functional change intended, except adding PINCTRL_MTK_MOORE to
keep PINCTRL_MT7622.
Marc Gonzalez (9):
arm64: defconfig: Regenerate for
Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index f786c95504d3..8d6878c1e794 100644
Arnd, Olof,
The following patch series was sent to a...@kernel.org
but the messages bounced because the SMTP server is
currently blacklisted. Can you get the patches through
the LAKML mailing list?
Regards.
On 07/11/2018 21:12, Marc Gonzalez wrote:
> Hello ARM maintainers,
>
> T
[ Add interested parties ]
On 07/11/2018 21:18, Marc Gonzalez wrote:
> Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
> enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
> which is not set.
>
> Signed-off-by: Marc Gonzalez
&g
[ Add interested parties ]
On 07/11/2018 21:16, Marc Gonzalez wrote:
> Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that implements
> the generic pinctrl dt-bindings")
>
> Signed-off-by: Marc Gonzalez
> ---
> arch/arm64/configs/defconfig | 2 +-
&g
[ Add interested parties ]
On 07/11/2018 21:14, Marc Gonzalez wrote:
> Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
>
> Signed-off-by: Marc Gonzalez
> ---
> arch/arm64/configs/defconfig | 1 -
> 1 file changed, 1 deletion(-)
>
&g
[ Add interested parties ]
On 07/11/2018 21:15, Marc Gonzalez wrote:
> Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code")
>
> Signed-off-by: Marc Gonzalez
> ---
> arch/arm64/configs/defconfig | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --gi
Hello ARM maintainers,
v2: Improve commit message for a few patches
The set of Kconfig options slowly changes with every kernel version.
This patch series regenerates the arm64 defconfig for v4.20
No functional change intended, except adding PINCTRL_MTK_MOORE to
keep PINCTRL_MT7622.
Marc
Commit a0ae2562c6c4 ("netfilter: conntrack: remove l3proto abstraction")
folded NF_CONNTRACK_IPV4 and NF_CONNTRACK_IPV6 into NF_CONNTRACK.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/
Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code") made
USB_CHIPIDEA select USB_ULPI_BUS, and removed USB_CHIPIDEA_ULPI.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/
Run the platform defconfig through kbuild, and handle the trivial case
where options merely move around.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 90 ++--
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/arch/arm64/configs
Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
dropped ARM_BIG_LITTLE_CPUFREQ support for ARM64.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_ROCKCHIP_I2S
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 725b9471b21c..8e181cca0a05 100644
--- a/arch/arm64/configs
Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that
implements the generic pinctrl dt-bindings") made PINCTRL_MT7622
depend on PINCTRL_MTK_MOORE.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
SCSI_UFS_HISI depends on SCSI_UFSHCD_PLATFORM=m
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e4957df18f23..75d5ed7ea53d 100644
--- a/arch/arm64
Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
which is not set.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs
SND_SOC_RK3399_GRU_SOUND selects SND_SOC_DA7219, SND_SOC_MAX98357A,
SND_SOC_RT5514, SND_SOC_RT5514_SPI.
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_RT5645.
SND_SOC_RL6231 is pulled in for SND_SOC_RT5514 and SND_SOC_RT5645.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 6
On November 8, 2018 12:38:10 PM GMT+01:00, Horia Geanta
wrote:
>On 11/8/2018 1:23 PM, Horia Geanta wrote:
>> On 11/7/2018 10:49 PM, Marc Gonzalez wrote:
>>> [ Add interested parties ]
>>>
>>> On 07/11/2018 21:18, Marc Gonzalez wrote:
>>>
>>&g
On 16/04/2019 11:59, Srinivas Kandagatla wrote:
> Many nvmem providers are not very keen on having default sysfs
> nvmem entry, as most of the usecases for them are inside kernel
> itself. And in some cases read/writes to some areas in nvmem are
> restricted and trapped at secure monitor level, so
On 16/04/2019 22:25, Arnd Bergmann wrote:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architecture, where a compat
On 15/04/2019 14:58, Jitendra Sharma wrote:
> We are observing one kernel crash in next_tgid function through
> getdents64 path. Call stack is as shown below:
It might help if you specify the exact kernel version you are discussing,
as in which tag or commit hash you are running.
Also, what are
On 18/04/2019 07:29, Stephen Rothwell wrote:
> Today's linux-next merge of the phy-next tree got a conflict in:
>
> Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
>
> between commit:
>
> 369b89366a3d ("dt-bindings: phy-qcom-qmp: Tweak qcom,msm8998-qmp-ufs-phy")
>
> from the qcom tr
NB: it is preferable to avoid top-posting here.
On 17/04/2019 18:58, Jitendra Sharma wrote:
> Kernel version: 4.14.83
NB2: 4.14.83 is obsolete, as it stands 2255 patches behind the tip of
linux-4.14.y (though only 4 patches in fs/proc).
NB3: 4.14 is 108499(!!) patches behind v5.1-rc5 (latest re
[ Trimming recipients list ]
On 03/04/2019 17:51, Igor Plyatov wrote:
> 2) I want to improve description and replace magic numbers by constants
> in Device Tree for SDMA. I mean strings like "dmas = <&sdma 11 7 1>,
> <&sdma 12 7 2>;"?
>
> So, finally Device Tree will have strings like
>
> dma
On 23/04/2019 15:10, Marc Gonzalez wrote:
> Sure. I can give you a Tested-by once everything works on the MEDIABOX I have.
>
> You mention the 4 thermal_zone*/temp failures.
>
> What about the cluster0-mhm-thermal and cluster1-mhm-thermal failures?
I have synced up with tod
On 25/04/2019 08:31, Amit Kucheria wrote:
> Andy, patches 1 and 2 fix problems that already exist upstream. They
> were not introduced by my series.
On IRC, you wrote: "can you send me the same output against mainline
(or linux-next) w/o my patches applied?"
$ git show 58ad5ab73152
commit 58ad5a
On 25/04/2019 08:31, Amit Kucheria wrote:
> Marc, can you please test these 3 patches on top of my original series?
Roger that.
# dmesg | grep thermal
/* NOTHING */
# for F in $(find /sys/class/thermal/thermal_zone?/
/sys/class/thermal/thermal_zone??/ -type f); do echo $F; cat $F; done
/sys/cl
hout breaking the user-space ABI, since
THERMAL_NAME_LENGTH is defined in include/uapi/linux/thermal.h
Anyway, for msm8998 patches, you have my
Tested-by: Marc Gonzalez
Regards.
On 24/02/2019 04:53, Bjorn Andersson wrote:
> On Sat 23 Feb 10:37 PST 2019, Marc Zyngier wrote:
>
>> On Sat, 23 Feb 2019 18:12:54 +, Bjorn Andersson wrote:
>>>
>>> On Mon 11 Feb 06:59 PST 2019, Marc Zyngier wrote:
>>>
On 11/02/2019 14:29, AngeloGioacchino Del Regno wrote:
> Also
On 12/03/2019 13:42, Stanimir Varbanov wrote:
> On 3/11/19 4:56 PM, Marc Gonzalez wrote:
>
>> Some chips report an incorrect device class. Override the incorrect
>> value using a quirk, instead of code in the read function.
>>
>> Signed-off-by: Marc Gonzalez
&g
On 12/03/2019 18:18, Marc Gonzalez wrote:
> On 12/03/2019 13:42, Stanimir Varbanov wrote:
>
>> I wonder, in case that dw_pcie_setup_rc() already has a write to
>> PCI_CLASS_DEVICE configuration register to set it as a bridge do we
>> still need to do the above fixup?
&g
We don't need to fudge the device class in qcom_pcie_rd_own_conf()
because dw_pcie_setup_rc() already does the right thing:
/* Program correct class for RC */
dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI);
Signed-off-by: Marc Gonzalez
---
Changes from
On 13/03/2019 12:45, Marc Gonzalez wrote:
> We don't need to fudge the device class in qcom_pcie_rd_own_conf()
> because dw_pcie_setup_rc() already does the right thing:
>
> /* Program correct class for RC */
> dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLAS
On 13/03/2019 19:29, Srinivas Kandagatla wrote:
> On 13/03/2019 11:45, Marc Gonzalez wrote:
>
>> We don't need to fudge the device class in qcom_pcie_rd_own_conf()
>> because dw_pcie_setup_rc() already does the right thing:
>>
>> /* Program correct class fo
On 13/03/2019 22:52, Srinivas Kandagatla wrote:
> On 13/03/2019 20:39, Marc Gonzalez wrote:
>
>> Could you pastebin the output of lspci -vvv -n in the working case?
>
> This was already in my original reply:
> working without patch : https://paste.ubuntu.com/p/TJm4hgjGW4/
On 14/03/2019 12:10, Srinivas Kandagatla wrote:
> Here is the output: https://paste.ubuntu.com/p/kFWZ4kXCxT/
Could you test the following patch:
And report boot log as well as output of lspci -vv ?
diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c
b/drivers/pci/controller/dwc/pcie-
On 01/02/2019 15:40, Marc Gonzalez wrote:
> Still no cookie. Perhaps VBUS needs to be kicked in the nads...
> Boot log at https://pastebin.ubuntu.com/p/3fqgQkRmyF/
Wait a second... It actually works!
usb 1-1: new high-speed USB device number 2 using xhci-hcd
usb 1-1: New USB device
If I plug in a USB-to-Ethernet gadget, the kernel sees something:
usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
usb 2-1: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 1.00
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: AX881
On 05/02/2019 05:58, Alim Akhtar wrote:
> On 04/02/19 11:12 PM, Marc Gonzalez wrote:
>
>> This reverts commit 60f0187031c05e04cbadffb62f557d0ff3564490.
>>
>> Calling ufshcd_set_vccq_rail_unused hangs my system.
>> It seems vccq is not *not* needed.
>
> AFAIK
On 05/02/2019 18:24, Marc Gonzalez wrote:
> /*** system hangs here for several seconds, then reboots ***/
Silly me. The system crashes in ufshcd_dump_regs() which is a bug
I fixed myself. Once I cherry-pick the appropriate fix, the board
no longer reboots, but UFS init does fail.
Full boot
On 04/02/2019 18:36, Marc Gonzalez wrote:
> diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
> b/arch/arm64/boot/dts/qcom/msm8998.dtsi
> index 6f4f4b79853b..831af20143da 100644
> --- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
>
On 06/02/2019 12:42, Kishon Vijay Abraham I wrote:
> On 06/02/19 12:29 AM, Evan Green wrote:
>
>> Expose a reset controller that the phy will later use to control its
>> own PHY reset in the UFS controller. This will enable the combining
>> of PHY init functionality into a single function.
>>
>>
On 06/02/2019 13:39, Kishon Vijay Abraham I wrote:
> I don't seem to have the dt-binding patch in my inbox. Can you resend them
> please?
Jeffrey pointed out a few deficiencies in the series.
I'll CC you on the entire upcoming v4 series.
Regards.
On 12/10/2018 23:39, Douglas Anderson wrote:
> If you look at the bindings for the UFS Host Controller it says:
>
> - compatible: must contain "jedec,ufs-1.1" or "jedec,ufs-2.0", may
> also list one or more of the following:
> "qcom,msm8994-ufshc"
>
On 05/02/2019 18:51, Marc Gonzalez wrote:
> On 05/02/2019 18:24, Marc Gonzalez wrote:
>
> Silly me. The system crashes in ufshcd_dump_regs() which is a bug
> I fixed myself. Once I cherry-pick the appropriate fix, the board
> no longer reboots, but UFS init does fail.
>
&g
[ Google, stop making email so hard. No, this is not spam, you twat of a
Bayesian filter ]
On 05/02/2019 18:51, Marc Gonzalez wrote:
> On 05/02/2019 18:24, Marc Gonzalez wrote:
>
> Silly me. The system crashes in ufshcd_dump_regs() which is a bug
> I fixed myself. Once I che
1 - 100 of 408 matches
Mail list logo
