Fix this.
>
> Signed-off-by: Marcel Ziswiler
Reviewed-by: Stefan Agner
>
> ---
>
> arch/arm/boot/dts/tegra20.dtsi | 26 +-
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/te
On 20.07.2018 10:04, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Actually report the error codes from of_get_named_gpio() resp.
> devm_gpio_request_one() upon trying to get the codec reset resp. sync
> GPIOs which may as well just be a probe deferrals.
>
> Signed-off-by: Marcel Ziswiler
On 20.07.2018 10:04, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Actually report the error codes from of_get_named_gpio() resp.
> devm_gpio_request_one() upon trying to get the codec reset resp. sync
> GPIOs which may as well just be a probe deferrals.
>
> Signed-off-by: Marcel Ziswiler
On 23.07.2018 14:36, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Use proper irq-gpio for stmpe811 touch controller.
I don't think this change is necessary, interrupts/interrupt-parent
specification seems to be supported by the driver as well.
--
Stefan
>
> Signed-off-by: Marcel
On 23.07.2018 14:36, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Use proper irq-gpio for stmpe811 touch controller.
I don't think this change is necessary, interrupts/interrupt-parent
specification seems to be supported by the driver as well.
--
Stefan
>
> Signed-off-by: Marcel
On 26.07.2018 09:31, Stephen Boyd wrote:
> Quoting Peter Geis (2018-07-25 16:42:34)
>> On 7/25/2018 7:24 PM, Stephen Boyd wrote:
>> > Quoting Marcel Ziswiler (2018-07-20 00:54:22)
>> >> From: Marcel Ziswiler
>> >>
>> >> Actually report the error code from devm_regulator_get() which may as
>> >>
On 26.07.2018 09:31, Stephen Boyd wrote:
> Quoting Peter Geis (2018-07-25 16:42:34)
>> On 7/25/2018 7:24 PM, Stephen Boyd wrote:
>> > Quoting Marcel Ziswiler (2018-07-20 00:54:22)
>> >> From: Marcel Ziswiler
>> >>
>> >> Actually report the error code from devm_regulator_get() which may as
>> >>
On 24.07.2018 12:43, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> PLX got bought by Broadcom therefore fix device tree compatible string
> vendor which silences the following checkpatch.pl warning:
>
> WARNING: DT compatible string vendor "plx" appears un-documented
> -- check
On 24.07.2018 12:43, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> PLX got bought by Broadcom therefore fix device tree compatible string
> vendor which silences the following checkpatch.pl warning:
>
> WARNING: DT compatible string vendor "plx" appears un-documented
> -- check
On 24.07.2018 12:42, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Reorder PCIe properties.
Hm, first vs. last property, as far as I can tell there is no official
recommendation. Maybe Rob can comment on that?
Most device trees put status last, also the base device trees
On 24.07.2018 12:42, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> Reorder PCIe properties.
Hm, first vs. last property, as far as I can tell there is no official
recommendation. Maybe Rob can comment on that?
Most device trees put status last, also the base device trees
nd_scan_tail().
Reviewed-by: Stefan Agner
>
> Signed-off-by: Miquel Raynal
> ---
> drivers/mtd/nand/raw/vf610_nfc.c | 127
> ---
> 1 file changed, 66 insertions(+), 61 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/vf610_nfc.c
nd_scan_tail().
Reviewed-by: Stefan Agner
>
> Signed-off-by: Miquel Raynal
> ---
> drivers/mtd/nand/raw/vf610_nfc.c | 127
> ---
> 1 file changed, 66 insertions(+), 61 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/vf610_nfc.c
On 13.07.2018 01:01, Russell King - ARM Linux wrote:
> On Thu, Jul 12, 2018 at 03:43:10PM -0700, Kees Cook wrote:
>> On Tue, Apr 17, 2018 at 1:11 AM, Thierry Reding wrote:
>> > On Mon, Apr 16, 2018 at 08:21:09PM +0200, Stefan Agner wrote:
>> >> On 16.04.20
On 13.07.2018 01:01, Russell King - ARM Linux wrote:
> On Thu, Jul 12, 2018 at 03:43:10PM -0700, Kees Cook wrote:
>> On Tue, Apr 17, 2018 at 1:11 AM, Thierry Reding wrote:
>> > On Mon, Apr 16, 2018 at 08:21:09PM +0200, Stefan Agner wrote:
>> >> On 16.04.20
Use the the DRM driver for MXSFB LCD controller (used in i.MX23/
i.MX28/i.MX6SX or i.MX7). Remove CONFIG_FB_MXS which will soon be
removed.
Signed-off-by: Stefan Agner
---
arch/arm/configs/imx_v6_v7_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs
Use the the DRM driver for MXSFB LCD controller (used in i.MX23/
i.MX28/i.MX6SX or i.MX7). Remove CONFIG_FB_MXS which will soon be
removed.
Signed-off-by: Stefan Agner
---
arch/arm/configs/imx_v6_v7_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs
Use the the DRM driver for MXSFB LCD controller (used in i.MX23/
i.MX28/i.MX6SX or i.MX7). Remove CONFIG_FB_MXS which will soon be
removed.
Note that this does not remove CONFIG_FB. CONFIG_FB gets selected
implicity by CONFIG_DRM/CONFIG_DRM_KMS_FB_HELPER.
Signed-off-by: Stefan Agner
---
arch
Use the the DRM driver for MXSFB LCD controller (used in i.MX23/
i.MX28/i.MX6SX or i.MX7). Remove CONFIG_FB_MXS which will soon be
removed.
Note that this does not remove CONFIG_FB. CONFIG_FB gets selected
implicity by CONFIG_DRM/CONFIG_DRM_KMS_FB_HELPER.
Signed-off-by: Stefan Agner
---
arch
On 12.07.2018 10:06, Stefan Agner wrote:
> In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
> is set to 0. However, it could be that the stack asks for a frequency
> change while clocks are on. In that case the function clears the
> divider registers
On 12.07.2018 10:06, Stefan Agner wrote:
> In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
> is set to 0. However, it could be that the stack asks for a frequency
> change while clocks are on. In that case the function clears the
> divider registers
-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..acacd8481473 100644
--- a/drivers/mmc/host/sdhci-esdhc-imx.c
+++ b
-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..acacd8481473 100644
--- a/drivers/mmc/host/sdhci-esdhc-imx.c
+++ b
Fix indent. This also makes disable/enable clock blocks look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index acacd8481473
Fix indent. This also makes disable/enable clock blocks look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index acacd8481473
-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..acacd8481473 100644
--- a/drivers/mmc/host/sdhci-esdhc-imx.c
+++ b
-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..acacd8481473 100644
--- a/drivers/mmc/host/sdhci-esdhc-imx.c
+++ b
-CMD23 being
used for now. With this the eMMC works stable on high-speed mode
while still announcing SD3.0.
This allows to use mmc-ddr-1_8v to enables DDR52 mode. In DDR52
mode read speed improves from about 42MiB/s to 72MiB/s on an
Apalis T30.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci
Make sure the clock is doubled when using eMMC DDR52 mode.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-tegra.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 137df06b9b6e..888a1ad511db 100644
-CMD23 being
used for now. With this the eMMC works stable on high-speed mode
while still announcing SD3.0.
This allows to use mmc-ddr-1_8v to enables DDR52 mode. In DDR52
mode read speed improves from about 42MiB/s to 72MiB/s on an
Apalis T30.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci
Make sure the clock is doubled when using eMMC DDR52 mode.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-tegra.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 137df06b9b6e..888a1ad511db 100644
controller simply does not support HS200.
Fixes: 7ad2ed1dfcbe ("mmc: tegra: enable UHS-I modes")
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-tegra.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host
controller simply does not support HS200.
Fixes: 7ad2ed1dfcbe ("mmc: tegra: enable UHS-I modes")
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-tegra.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host
>>
>> is missing a Signed-off-by from its author.
>
> Thanks for spotting, but it's worse than that. It does have a sign-off
> from its author, but the authorship wasn't preserved by Stefan Agner
> (no From: line in the email body, as there was in Steven's original
> post
>>
>> is missing a Signed-off-by from its author.
>
> Thanks for spotting, but it's worse than that. It does have a sign-off
> from its author, but the authorship wasn't preserved by Stefan Agner
> (no From: line in the email body, as there was in Steven's original
> post
On 04.07.2018 13:30, Stefan Agner wrote:
> On 21.06.2018 18:47, Steven Rostedt wrote:
>> From: Steven Rostedt (VMware)
>>
>> Dynamic ftrace requires modifying the code segments that are usually
>> set to read-only. To do this, a per arch function is called both bef
On 04.07.2018 13:30, Stefan Agner wrote:
> On 21.06.2018 18:47, Steven Rostedt wrote:
>> From: Steven Rostedt (VMware)
>>
>> Dynamic ftrace requires modifying the code segments that are usually
>> set to read-only. To do this, a per arch function is called both bef
Use the disable-wp to indicate that Apalis and Colibri iMX6 do not
make use of the native write-protect signal available on the i.MX 6
SoCs. This prevents warnings:
mmc0: host does not support reading read-only switch, assuming write-enable
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts
Use the disable-wp to indicate that Apalis and Colibri iMX6 do not
make use of the native write-protect signal available on the i.MX 6
SoCs. This prevents warnings:
mmc0: host does not support reading read-only switch, assuming write-enable
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts
The fixed 1.8V regulator is not used, and there is in fact no
fixed 1.8V regulator on the module. Remove it.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 8
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 8
2 files changed, 16 deletions(-)
diff --git
The fixed 1.8V regulator is not used, and there is in fact no
fixed 1.8V regulator on the module. Remove it.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 8
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 8
2 files changed, 16 deletions(-)
diff --git
voltage (VAG) from this
supply. The new value should allow higher output swings before
clipping occurs. Refer to the SGTL5000 datasheet for details.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 22 +++---
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 20
voltage (VAG) from this
supply. The new value should allow higher output swings before
clipping occurs. Refer to the SGTL5000 datasheet for details.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 22 +++---
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 20
100/200MHz states for USDHC3 are not required since the SoC
does not support modes faster than DDR52 for the on board eMMC.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 34 --
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 34
100/200MHz states for USDHC3 are not required since the SoC
does not support modes faster than DDR52 for the on board eMMC.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 34 --
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 34
VDDD is connected to VGEN4 of the PF0100. This rail should only
run at 1.8V since there are multiple consumer and they all
expect the rail to be at 1.8V.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 3 ++-
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 3 ++-
2 files
VDDD is connected to VGEN4 of the PF0100. This rail should only
run at 1.8V since there are multiple consumer and they all
expect the rail to be at 1.8V.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 3 ++-
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 3 ++-
2 files
Add Apalis UART1 as default serial console.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6q-apalis-eval.dts | 4
arch/arm/boot/dts/imx6q-apalis-ixora-v1.1.dts | 4
arch/arm/boot/dts/imx6q-apalis-ixora.dts | 4
3 files changed, 12 insertions(+)
diff --git
Add the 3.3V main supply on the carrier board. Currently as a fixed
supply since not all consumer are modeled yet. This gets also rid of
some missing supply warnings.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6q-apalis-eval.dts | 12
1 file changed, 12 insertions
Add Apalis UART1 as default serial console.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6q-apalis-eval.dts | 4
arch/arm/boot/dts/imx6q-apalis-ixora-v1.1.dts | 4
arch/arm/boot/dts/imx6q-apalis-ixora.dts | 4
3 files changed, 12 insertions(+)
diff --git
Add the 3.3V main supply on the carrier board. Currently as a fixed
supply since not all consumer are modeled yet. This gets also rid of
some missing supply warnings.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6q-apalis-eval.dts | 12
1 file changed, 12 insertions
Use no-1-8-v device tree property to indicate that the board does
not support 1.8V signaling. The property voltage-ranges seems not
appropriate in our case since we do not have level shifters in
place.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 6 +++---
arch/arm
Use no-1-8-v device tree property to indicate that the board does
not support 1.8V signaling. The property voltage-ranges seems not
appropriate in our case since we do not have level shifters in
place.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 6 +++---
arch/arm
IRQ19 for ARM PMU counters
hw perfevents: /pmu: failed to register PMU devices!
armv7-pmu: probe of pmu failed with error -16
The driver is clearly not designed to be removed. Disable bind/
unbind for this driver.
Signed-off-by: Stefan Agner
---
arch/arm/kernel/perf_event_v7.c | 1 +
1 file
IRQ19 for ARM PMU counters
hw perfevents: /pmu: failed to register PMU devices!
armv7-pmu: probe of pmu failed with error -16
The driver is clearly not designed to be removed. Disable bind/
unbind for this driver.
Signed-off-by: Stefan Agner
---
arch/arm/kernel/perf_event_v7.c | 1 +
1 file
Hi Vinod, Hi Angelo,
On 05.07.2018 14:45, Angelo Dureghello wrote:
> Hi Vinod,
>
> On Thu, Jul 05, 2018 at 10:12:53AM +0200, Angelo Dureghello wrote:
>> Hi Vinod,
>>
>> On Thu, Jul 05, 2018 at 01:05:52PM +0530, Vinod wrote:
>> > On 04-07-18, 10:54, Krzysztof Kozlowski wrote:
>> > > Hi,
>> > >
>>
Hi Vinod, Hi Angelo,
On 05.07.2018 14:45, Angelo Dureghello wrote:
> Hi Vinod,
>
> On Thu, Jul 05, 2018 at 10:12:53AM +0200, Angelo Dureghello wrote:
>> Hi Vinod,
>>
>> On Thu, Jul 05, 2018 at 01:05:52PM +0530, Vinod wrote:
>> > On 04-07-18, 10:54, Krzysztof Kozlowski wrote:
>> > > Hi,
>> > >
>>
On 05.07.2018 14:45, Angelo Dureghello wrote:
> Hi Vinod,
>
> On Thu, Jul 05, 2018 at 10:12:53AM +0200, Angelo Dureghello wrote:
>> Hi Vinod,
>>
>> On Thu, Jul 05, 2018 at 01:05:52PM +0530, Vinod wrote:
>> > On 04-07-18, 10:54, Krzysztof Kozlowski wrote:
>> > > Hi,
>> > >
>> > > The commit
On 05.07.2018 14:45, Angelo Dureghello wrote:
> Hi Vinod,
>
> On Thu, Jul 05, 2018 at 10:12:53AM +0200, Angelo Dureghello wrote:
>> Hi Vinod,
>>
>> On Thu, Jul 05, 2018 at 01:05:52PM +0530, Vinod wrote:
>> > On 04-07-18, 10:54, Krzysztof Kozlowski wrote:
>> > > Hi,
>> > >
>> > > The commit
On 05.07.2018 15:09, Ulf Hansson wrote:
> On 5 July 2018 at 14:15, Stefan Agner wrote:
>> In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
>> is set to 0. However, it could be that the stack asks for a frequency
>> change while clocks are on. In that cas
On 05.07.2018 15:09, Ulf Hansson wrote:
> On 5 July 2018 at 14:15, Stefan Agner wrote:
>> In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
>> is set to 0. However, it could be that the stack asks for a frequency
>> change while clocks are on. In that cas
On 05.07.2018 15:10, Ulf Hansson wrote:
> On 4 July 2018 at 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver cur
On 05.07.2018 15:10, Ulf Hansson wrote:
> On 4 July 2018 at 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver cur
is
not available. This prevents the stack from even trying to use
3.3V signaling and avoids the above warning.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
is
not available. This prevents the stack from even trying to use
3.3V signaling and avoids the above warning.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
to make disable/enable clock look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..aa48f4b2541a
to make disable/enable clock look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..aa48f4b2541a
On 05.07.2018 13:23, Ulf Hansson wrote:
> On 4 July 2018 at 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver cur
On 05.07.2018 13:23, Ulf Hansson wrote:
> On 4 July 2018 at 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver cur
to make disable/enable clock look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..aa48f4b2541a
to make disable/enable clock look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 85fd5a8b0b6d..aa48f4b2541a
On 05.07.2018 11:48, Ulf Hansson wrote:
> On 4 July 2018 at 17:18, Stefan Agner wrote:
>> On 04.07.2018 17:07, Stefan Agner wrote:
>>> If pinctrl nodes for 100/200MHz are missing, the controller should
>>> not select any mode which need signal frequencies 100MH
On 05.07.2018 11:48, Ulf Hansson wrote:
> On 4 July 2018 at 17:18, Stefan Agner wrote:
>> On 04.07.2018 17:07, Stefan Agner wrote:
>>> If pinctrl nodes for 100/200MHz are missing, the controller should
>>> not select any mode which need signal frequencies 100MH
On 05.07.2018 04:52, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Thursday, June 28, 2018 4:13 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Dong ;
On 05.07.2018 04:52, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Thursday, June 28, 2018 4:13 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Dong ;
On 05.07.2018 04:40, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Wednesday, July 4, 2018 11:08 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Do
On 05.07.2018 04:40, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Wednesday, July 4, 2018 11:08 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Do
On 04.07.2018 17:07, Stefan Agner wrote:
> If pinctrl nodes for 100/200MHz are missing, the controller should
> not select any mode which need signal frequencies 100MHz or higher.
> To prevent such speed modes the driver currently uses the quirk flag
> SDHCI_QUIRK2_NO_1_8_V. This
On 04.07.2018 17:07, Stefan Agner wrote:
> If pinctrl nodes for 100/200MHz are missing, the controller should
> not select any mode which need signal frequencies 100MHz or higher.
> To prevent such speed modes the driver currently uses the quirk flag
> SDHCI_QUIRK2_NO_1_8_V. This
if no faster pinctrl states are available:
# cat /sys/kernel/debug/mmc1/ios
...
timing spec:8 (mmc DDR52)
signal voltage: 1 (1.80 V)
...
Link: http://lkml.kernel.org/r/20180628081331.13051-1-ste...@agner.ch
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 21
if no faster pinctrl states are available:
# cat /sys/kernel/debug/mmc1/ios
...
timing spec:8 (mmc DDR52)
signal voltage: 1 (1.80 V)
...
Link: http://lkml.kernel.org/r/20180628081331.13051-1-ste...@agner.ch
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 21
On 04.07.2018 13:16, Ulf Hansson wrote:
> On 4 July 2018 at 12:55, Stefan Agner wrote:
>> On 04.07.2018 12:07, Ulf Hansson wrote:
>>> On 3 July 2018 at 10:48, Stefan Agner wrote:
>>>> On 02.07.2018 16:36, Ulf Hansson wrote:
>>>>> On 28 June 2018 at
On 04.07.2018 13:16, Ulf Hansson wrote:
> On 4 July 2018 at 12:55, Stefan Agner wrote:
>> On 04.07.2018 12:07, Ulf Hansson wrote:
>>> On 3 July 2018 at 10:48, Stefan Agner wrote:
>>>> On 02.07.2018 16:36, Ulf Hansson wrote:
>>>>> On 28 June 2018 at
et set. This is
> similar to the x86 solution from commit 162396309745 ("ftrace, x86:
> make kernel text writable only for conversions").
>
> Reported-by: Stefan Agner
> Tested-by: Stefan Agner
> Link: http://lkml.kernel.org/r/20180620212906.24b7b...@vmware.local.home
&g
et set. This is
> similar to the x86 solution from commit 162396309745 ("ftrace, x86:
> make kernel text writable only for conversions").
>
> Reported-by: Stefan Agner
> Tested-by: Stefan Agner
> Link: http://lkml.kernel.org/r/20180620212906.24b7b...@vmware.local.home
&g
On 04.07.2018 12:07, Ulf Hansson wrote:
> On 3 July 2018 at 10:48, Stefan Agner wrote:
>> On 02.07.2018 16:36, Ulf Hansson wrote:
>>> On 28 June 2018 at 10:13, Stefan Agner wrote:
>>>> Some hosts are capable of running higher speed modes but do not
>>>>
On 04.07.2018 12:07, Ulf Hansson wrote:
> On 3 July 2018 at 10:48, Stefan Agner wrote:
>> On 02.07.2018 16:36, Ulf Hansson wrote:
>>> On 28 June 2018 at 10:13, Stefan Agner wrote:
>>>> Some hosts are capable of running higher speed modes but do not
>>>>
sks for a chip select we currently do
not support.
Reported-by: Dan Carpenter
Signed-off-by: Stefan Agner
---
drivers/mtd/nand/raw/tegra_nand.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/raw/tegra_nand.c
b/drivers/mtd/nand/raw/tegra_nand.c
in
sks for a chip select we currently do
not support.
Reported-by: Dan Carpenter
Signed-off-by: Stefan Agner
---
drivers/mtd/nand/raw/tegra_nand.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/raw/tegra_nand.c
b/drivers/mtd/nand/raw/tegra_nand.c
in
Hi Thierry, Hi Miquel,
On 25.06.2018 14:34, Miquel Raynal wrote:
> Hi Stefan,
>
> On Sun, 24 Jun 2018 23:27:21 +0200, Stefan Agner
> wrote:
>
>> Eigth and hopefully final revision gets rid of nand_release() as
>> suggested by Boris.
>>
>> --
>&
Hi Thierry, Hi Miquel,
On 25.06.2018 14:34, Miquel Raynal wrote:
> Hi Stefan,
>
> On Sun, 24 Jun 2018 23:27:21 +0200, Stefan Agner
> wrote:
>
>> Eigth and hopefully final revision gets rid of nand_release() as
>> suggested by Boris.
>>
>> --
>&
On 02.07.2018 16:36, Ulf Hansson wrote:
> On 28 June 2018 at 10:13, Stefan Agner wrote:
>> Some hosts are capable of running higher speed modes but do not
>> have the board support for it. Introduce a quirk which prevents
>> the stack from using modes running at 100MHz o
On 02.07.2018 16:36, Ulf Hansson wrote:
> On 28 June 2018 at 10:13, Stefan Agner wrote:
>> Some hosts are capable of running higher speed modes but do not
>> have the board support for it. Introduce a quirk which prevents
>> the stack from using modes running at 100MHz o
x144/0x1d8)
> [<80900d48>] (kernel_init_freeable) from [<805ff6a8>]
> (kernel_init+0x10/0x114)
> [<805ff698>] (kernel_init) from [<80107be8>] (ret_from_fork+0x14/0x2c)
>
> Cc:
> Fixes: 5ee67b587a2b ("spi: dspi: clear SPI_SR before enable inter
x144/0x1d8)
> [<80900d48>] (kernel_init_freeable) from [<805ff6a8>]
> (kernel_init+0x10/0x114)
> [<805ff698>] (kernel_init) from [<80107be8>] (ret_from_fork+0x14/0x2c)
>
> Cc:
> Fixes: 5ee67b587a2b ("spi: dspi: clear SPI_SR before enable inter
DDR52)
signal voltage: 1 (1.80 V)
...
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 20a420b765b3..4a1c33018072 100644
DDR52)
signal voltage: 1 (1.80 V)
...
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index 20a420b765b3..4a1c33018072 100644
Some hosts are capable of running higher speed modes but do not
have the board support for it. Introduce a quirk which prevents
the stack from using modes running at 100MHz or faster.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci.c | 8
drivers/mmc/host/sdhci.h | 2 ++
2 files
Some hosts are capable of running higher speed modes but do not
have the board support for it. Introduce a quirk which prevents
the stack from using modes running at 100MHz or faster.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci.c | 8
drivers/mmc/host/sdhci.h | 2 ++
2 files
The field support_vsel is currently only used in the device tree
case. Get rid of it. No change in behavior.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 8 ++--
include/linux/platform_data/mmc-esdhc-imx.h | 2 --
2 files changed, 2 insertions(+), 8
401 - 500 of 3440 matches
Mail list logo
