On 26.02.2021 16:40, Anton Ivanov wrote:
These are two different clients, then what you see is possible on NFS
with client side caching. If you have multiple clients reading/writing
to the same files you usually need to tune the caching options and/or
use locking. I suspect that if you leave
it took me a while to correlate this) the logs it writes
have been truncated, but only while they're being observed on the
client, using tail -f or something like that.
Looks like this then:
On Server:
store01 /srv/export/home/users/timo/TestRun # ls -l slurm-41101.out
-rw-r--r-- 1 timo timo
Got a dmesg message on my AMD Renoir based Acer laptop:
"acer_wmi: Unknown key number - 0x84" when toggling keyboard
background light
Signed-off-by: Timo Witte
---
drivers/platform/x86/acer-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/acer-wmi.c
Zero the amount of padding bytes determined in perf_prepare_sample().
This prevents garbage being read from the ring buffer after it has wrapped
the page boundary at least once.
Signed-off-by: Timo Beckers
---
kernel/events/core.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions
*Timo Wischer*
Engineering Software Multimedia (ADITG/ESM)
Tel. +49 5121 49 6938
On 4/17/19 11:40 AM, Takashi Iwai wrote:
On Wed, 17 Apr 2019 11:30:10 +0200,
Timo Wischer wrote:
On 4/17/19 11:21, Takashi Iwai wrote:
On Wed, 17 Apr 2019 10:46:11 +0200,
wrote:
From: Timo Wischer
Since ARMv7
On 4/17/19 11:21, Takashi Iwai wrote:
On Wed, 17 Apr 2019 10:46:11 +0200,
wrote:
From: Timo Wischer
Since ARMv7 hardware cache coherence is supported.
"The SCU maintains coherency between the individual data caches in the
Cortex-A5 MPCore processor using a variation of the MOESI protoco
On 3/27/19 10:38, Takashi Iwai wrote:
On Wed, 27 Mar 2019 10:26:56 +0100,
Timo Wischer wrote:
On 3/27/19 10:11, Takashi Iwai wrote:
On Wed, 27 Mar 2019 09:34:40 +0100,
Timo Wischer wrote:
On 3/26/19 17:00, Takashi Iwai wrote:
On Tue, 26 Mar 2019 16:16:54 +0100,
Timo Wischer wrote:
On 3/26
On 3/27/19 10:11, Takashi Iwai wrote:
On Wed, 27 Mar 2019 09:34:40 +0100,
Timo Wischer wrote:
On 3/26/19 17:00, Takashi Iwai wrote:
On Tue, 26 Mar 2019 16:16:54 +0100,
Timo Wischer wrote:
On 3/26/19 15:23, Takashi Iwai wrote:
On Tue, 26 Mar 2019 12:25:37 +0100,
Timo Wischer wrote:
On 3/26
On 3/26/19 17:00, Takashi Iwai wrote:
On Tue, 26 Mar 2019 16:16:54 +0100,
Timo Wischer wrote:
On 3/26/19 15:23, Takashi Iwai wrote:
On Tue, 26 Mar 2019 12:25:37 +0100,
Timo Wischer wrote:
On 3/26/19 09:35, Takashi Iwai wrote:
On Tue, 26 Mar 2019 08:49:33 +0100,
wrote
On 3/26/19 15:23, Takashi Iwai wrote:
On Tue, 26 Mar 2019 12:25:37 +0100,
Timo Wischer wrote:
On 3/26/19 09:35, Takashi Iwai wrote:
On Tue, 26 Mar 2019 08:49:33 +0100,
wrote:
From: Timo Wischer
snd_pcm_link() can be called by the user as long
On 3/25/19 17:58, Takashi Iwai wrote:
On Mon, 25 Mar 2019 17:40:23 +0100,
Timo Wischer wrote:
Best regards
Timo Wischer
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6938
On 3/25/19 17:07, Takashi Iwai wrote:
On Mon, 25 Mar 2019 17:00:38 +0100,
wrote:
From
hm tegra_bpmp_i2c_algo = {
.master_xfer = tegra_bpmp_i2c_xfer,
+ .master_xfer_atomic = tegra_bpmp_i2c_xfer_atomic,
.functionality = tegra_bpmp_i2c_func,
};
Looks good to me.
Reviewed-by: Timo Alho
vice *pdev)
return err;
}
-static int tegra_bpmp_resume(struct device *dev)
+static int __maybe_unused tegra_bpmp_resume(struct device *dev)
{
struct tegra_bpmp *bpmp = dev_get_drvdata(dev);
unsigned int i;
Arnd, is this seen with 32-bit ARM configs?
Timo, does it make sen
vice *pdev)
return err;
}
-static int tegra_bpmp_resume(struct device *dev)
+static int __maybe_unused tegra_bpmp_resume(struct device *dev)
{
struct tegra_bpmp *bpmp = dev_get_drvdata(dev);
unsigned int i;
Arnd, is this seen with 32-bit ARM configs?
Timo, does it make sen
'ping' to check that firmware is alive, or 'tag' to read the firmware
version).
BR,
Timo
'ping' to check that firmware is alive, or 'tag' to read the firmware
version).
BR,
Timo
e and data to firmware via DRAM.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
Changes in v2:
- Address Jonathan's review feedback
* restructure error printing and what error codes passed to higher
layers
* don't use IS_ERR_OR_NULL()
* avoid overwriting last-character of filename in
e and data to firmware via DRAM.
Signed-off-by: Timo Alho
---
Changes in v2:
- Address Jonathan's review feedback
* restructure error printing and what error codes passed to higher
layers
* don't use IS_ERR_OR_NULL()
* avoid overwriting last-character of filename in one corner case
(n
On 29.09.2017 17:53, Jonathan Hunter wrote:
On 29/09/17 14:46, Timo Alho wrote:
Hi Jon,
On 21.09.2017 14:21, Jonathan Hunter wrote:
On 07/09/17 10:31, Timo Alho wrote:
Check return code in BPMP response message(s). The typical error case
is when clock operation is attempted with invalid
On 29.09.2017 17:53, Jonathan Hunter wrote:
On 29/09/17 14:46, Timo Alho wrote:
Hi Jon,
On 21.09.2017 14:21, Jonathan Hunter wrote:
On 07/09/17 10:31, Timo Alho wrote:
Check return code in BPMP response message(s). The typical error case
is when clock operation is attempted with invalid
On 29.09.2017 17:58, Jonathan Hunter wrote:
+static int bpmp_populate_dir(struct tegra_bpmp *bpmp, struct seqbuf
*seqbuf,
+ struct dentry *parent, uint32_t depth)
Do we need to use uint32_t here?
+{
+ int err;
+ uint32_t d, t;
And here?
It's part of the BPMP ABI
On 29.09.2017 17:58, Jonathan Hunter wrote:
+static int bpmp_populate_dir(struct tegra_bpmp *bpmp, struct seqbuf
*seqbuf,
+ struct dentry *parent, uint32_t depth)
Do we need to use uint32_t here?
+{
+ int err;
+ uint32_t d, t;
And here?
It's part of the BPMP ABI
Hi Jon,
On 21.09.2017 14:21, Jonathan Hunter wrote:
On 07/09/17 10:31, Timo Alho wrote:
Check return code in BPMP response message(s). The typical error case
is when clock operation is attempted with invalid clock identifier.
Also remove error print from call to clk_get_info
Hi Jon,
On 21.09.2017 14:21, Jonathan Hunter wrote:
On 07/09/17 10:31, Timo Alho wrote:
Check return code in BPMP response message(s). The typical error case
is when clock operation is attempted with invalid clock identifier.
Also remove error print from call to clk_get_info
e a generic warning message here? Looks like it could fail
silently.
I'll add a warning to call site (bpmp.c) if this fails.
-Timo
e a generic warning message here? Looks like it could fail
silently.
I'll add a warning to call site (bpmp.c) if this fails.
-Timo
Add checks for return code in BPMP response message.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/reset/tegra/reset-bpmp.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/reset/tegra/reset-bpmp.c b/drivers/reset/tegra/reset-bpmp.c
index 5
Add checks for return code in BPMP response message.
Signed-off-by: Timo Alho
---
drivers/reset/tegra/reset-bpmp.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/reset/tegra/reset-bpmp.c b/drivers/reset/tegra/reset-bpmp.c
index 5daf2ee..fac2db6 100644
this code and does not pass it to
caller. Fix this by adding an extra struct member to
tegra_bpmp_message and populate that with return code.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/firmware/tegra/bpmp.c | 22 --
include/soc/tegra/bpmp.h | 1 +
2
this code and does not pass it to
caller. Fix this by adding an extra struct member to
tegra_bpmp_message and populate that with return code.
Signed-off-by: Timo Alho
---
drivers/firmware/tegra/bpmp.c | 22 --
include/soc/tegra/bpmp.h | 1 +
2 files changed, 17
out when the clock id is unused.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/clk/tegra/clk-bpmp.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/tegra/clk-bpmp.c b/drivers/clk/tegra/clk-bpmp.c
index 638ace6..a896692 100644
--- a/d
out when the clock id is unused.
Signed-off-by: Timo Alho
---
drivers/clk/tegra/clk-bpmp.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/tegra/clk-bpmp.c b/drivers/clk/tegra/clk-bpmp.c
index 638ace6..a896692 100644
--- a/drivers/clk/tegra/clk
,
Timo
Timo Alho (4):
firmware: tegra: propagate error code to caller
clk: tegra: check BPMP response return code
reset: tegra: check BPMP response return code
soc/tegra: bpmp: check BPMP response return code
drivers/clk/tegra/clk-bpmp.c | 15 ++-
drivers/firmware/tegra
Add checks for return code in BPMP response message.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/soc/tegra/powergate-bpmp.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/soc/tegra/powergate-bpmp.c
b/drivers/soc/tegra/powergate-
,
Timo
Timo Alho (4):
firmware: tegra: propagate error code to caller
clk: tegra: check BPMP response return code
reset: tegra: check BPMP response return code
soc/tegra: bpmp: check BPMP response return code
drivers/clk/tegra/clk-bpmp.c | 15 ++-
drivers/firmware/tegra
Add checks for return code in BPMP response message.
Signed-off-by: Timo Alho
---
drivers/soc/tegra/powergate-bpmp.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/soc/tegra/powergate-bpmp.c
b/drivers/soc/tegra/powergate-bpmp.c
index 8fc3560
e and data to firmware via DRAM.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/firmware/tegra/Makefile | 4 +-
drivers/firmware/tegra/bpmp.c | 2 +
drivers/firmware/tegra/bpmp_debugfs.c | 446 ++
include/soc/tegra/bpmp.h |
e and data to firmware via DRAM.
Signed-off-by: Timo Alho
---
drivers/firmware/tegra/Makefile | 4 +-
drivers/firmware/tegra/bpmp.c | 2 +
drivers/firmware/tegra/bpmp_debugfs.c | 446 ++
include/soc/tegra/bpmp.h | 14 ++
4 files ch
-by: Timo Alho <ta...@nvidia.com>
---
drivers/mmc/host/sdhci-tegra.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index f668a6f..cdde9ff 100644
--- a/drivers/mmc/host/sdhci-tegra.c
+++ b/drivers/mmc/host
-by: Timo Alho
---
drivers/mmc/host/sdhci-tegra.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index f668a6f..cdde9ff 100644
--- a/drivers/mmc/host/sdhci-tegra.c
+++ b/drivers/mmc/host/sdhci-tegra.c
@@ -501,8
Subdevices of bpmp, such as bpmp-i2c, require the bpmp device's
drvdata to be set during their probe. Currently this is not always the
case. Fix this by calling platform_set_drvdata() earlier during bpmp's
probe.
Signed-off-by: Timo Alho <ta...@nvidia.com>
---
drivers/firmware/tegra/bpmp
Subdevices of bpmp, such as bpmp-i2c, require the bpmp device's
drvdata to be set during their probe. Currently this is not always the
case. Fix this by calling platform_set_drvdata() earlier during bpmp's
probe.
Signed-off-by: Timo Alho
---
drivers/firmware/tegra/bpmp.c | 4 ++--
1 file
This patch fixes the following checkpatch.pl warning in prism2sta.h:
WARNING: Block comments should align the * on each line
No more warnings block comments warnings for this file.
Signed-off-by: Timo Schmid <timo.sch...@gmail.com>
---
drivers/staging/wlan-ng/prism2sta.
This patch fixes the following checkpatch.pl warning in prism2sta.h:
WARNING: Block comments should align the * on each line
No more warnings block comments warnings for this file.
Signed-off-by: Timo Schmid
---
drivers/staging/wlan-ng/prism2sta.c | 36 ++--
1
Hi,
Riku Voipio schrieb am 13.09.2016 10:22:
> On 5 September 2016 at 02:43, Timo Sigurdsson
> <public_tim...@silentcreek.de> wrote:
>> The builddeb script has some hardcoded references to linux version 2.6
>> which is ancient. Use a variable instead in order to keep in s
Hi,
Riku Voipio schrieb am 13.09.2016 10:22:
> On 5 September 2016 at 02:43, Timo Sigurdsson
> wrote:
>> The builddeb script has some hardcoded references to linux version 2.6
>> which is ancient. Use a variable instead in order to keep in sync with
>> new rel
The builddeb script has some hardcoded references to linux version 2.6
which is ancient. Use a variable instead in order to keep in sync with
new releases and avoid the need to manually update this. In addition,
change the copyright notice to include the year 2016.
Signed-off-by: Timo Sigurdsson
The builddeb script has some hardcoded references to linux version 2.6
which is ancient. Use a variable instead in order to keep in sync with
new releases and avoid the need to manually update this. In addition,
change the copyright notice to include the year 2016.
Signed-off-by: Timo Sigurdsson
l now
turn off the USB power supply during boot by default if the driver isn't
present. (This was not the case in linux 4.3 or lower where the USB power
was always left on.)
Hence, add the driver to multi_v7_defconfig in order to keep USB support
working on those boards that require it.
Signed-of
Hi Arnd,
Arnd Bergmann schrieb am 31.12.2015 16:46:
> On Tuesday 29 December 2015 02:47:32 Timo Sigurdsson wrote:
>> Here is a late patch aimed for 4.4-rc8 (or 4.4). It would be nice if this
>> could make it into 4.4 in order to avoid unpleasent surprises (and
>>
Hi Maxime,
Maxime Ripard schrieb am 31.12.2015 17:00:
> Hi Arnd,
>
> On Thu, Dec 31, 2015 at 04:46:01PM +0100, Arnd Bergmann wrote:
>> On Tuesday 29 December 2015 02:47:32 Timo Sigurdsson wrote:
>> > Here is a late patch aimed for 4.4-rc8 (or 4.4). It would be nice if
Hi Arnd,
Arnd Bergmann schrieb am 31.12.2015 16:46:
> On Tuesday 29 December 2015 02:47:32 Timo Sigurdsson wrote:
>> Here is a late patch aimed for 4.4-rc8 (or 4.4). It would be nice if this
>> could make it into 4.4 in order to avoid unpleasent surprises (and
>>
Hi Maxime,
Maxime Ripard schrieb am 31.12.2015 17:00:
> Hi Arnd,
>
> On Thu, Dec 31, 2015 at 04:46:01PM +0100, Arnd Bergmann wrote:
>> On Tuesday 29 December 2015 02:47:32 Timo Sigurdsson wrote:
>> > Here is a late patch aimed for 4.4-rc8 (or 4.4). It would be nice if
l now
turn off the USB power supply during boot by default if the driver isn't
present. (This was not the case in linux 4.3 or lower where the USB power
was always left on.)
Hence, add the driver to multi_v7_defconfig in order to keep USB support
working on those boards that require it.
Signed-of
as a newly added driver is required to power them.
Timo Sigurdsson (1):
ARM: Fix broken USB support in sunxi_defconfig
arch/arm/configs/sunxi_defconfig | 1 +
1 file changed, 1 insertion(+)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
w turn off the USB power
supply during boot by default if the driver isn't present. (This was not the
case in linux 4.3 or lower where the USB power was always left on.)
Hence, add the driver to sunxi_defconfig in order to keep USB support working
on those boards that require it.
Signed-of
w turn off the USB power
supply during boot by default if the driver isn't present. (This was not the
case in linux 4.3 or lower where the USB power was always left on.)
Hence, add the driver to sunxi_defconfig in order to keep USB support working
on those boards that require it.
Signed-of
as a newly added driver is required to power them.
Timo Sigurdsson (1):
ARM: Fix broken USB support in sunxi_defconfig
arch/arm/configs/sunxi_defconfig | 1 +
1 file changed, 1 insertion(+)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
of
CONFIG_KEYBOARD_SUN4I_LRADC and not have it removed while cleaning up
Good night,
Timo
Am Freitag, den 20.11.2015, 02:46 +0100 schrieb Timo Sigurdsson:
> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> framework") moved the the sunxi SID driver to a new framework, but left
&
e the line disabling CONFIG_KEYBOARD in
order to really enable KEYBOARD_SUN4I_LRADC.
Signed-off-by: Timo Sigurdsson
---
arch/arm/configs/sunxi_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index 0bbc2ee..9025
-by: Timo Sigurdsson
---
arch/arm/configs/sunxi_defconfig | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index 90252ca..95b51fc 100644
--- a/arch/arm/configs/sunxi_defconfig
+++ b/arch/arm/configs
_defconfig.
Signed-off-by: Timo Sigurdsson
---
arch/arm/configs/sunxi_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index 3c36e16..0bbc2ee 100644
--- a/arch/arm/configs/sunxi_defconfig
+++
Sorry, sent out the reply first to Maxime only and forgot to include the
rest of the bunch. So, here we go again...
Hi Maxime,
Am Freitag, den 20.11.2015, 00:43 +0100 schrieb Maxime Ripard:
> Hi,
>
> On Thu, Nov 19, 2015 at 10:48:35PM +0100, Timo Sigurdsson wrote:
> > Hi Maxime,
Hi Maxime,
Hi Chen-Yu,
Am Dienstag, den 17.11.2015, 02:42 +0100 schrieb Timo Sigurdsson:
> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> framework") moved the the sunxi SID driver to a new framework, but left
> sunxi_defconfig with the depre
the driver
in multi_v7_defconfig.
Signed-off-by: Timo Sigurdsson
---
Changes in v2:
- Move the extra cleanup work for multi_v7_defconfig to a separate
patch (to be submitted at a later point to avoid conflicts with
another patch waiting to be merged)
---
arch/arm/configs/multi_v7_defconfig | 3 ++-
1 file
-by: Timo Sigurdsson <public_tim...@silentcreek.de>
---
arch/arm/configs/sunxi_defconfig | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index 90252ca..95b51fc 100644
--- a/arch/arm/configs/sunxi_defconfig
_defconfig.
Signed-off-by: Timo Sigurdsson <public_tim...@silentcreek.de>
---
arch/arm/configs/sunxi_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig
index 3c36e16..0bbc2ee 100644
--- a/
e the line disabling CONFIG_KEYBOARD in
order to really enable KEYBOARD_SUN4I_LRADC.
Signed-off-by: Timo Sigurdsson <public_tim...@silentcreek.de>
---
arch/arm/configs/sunxi_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi
Sorry, sent out the reply first to Maxime only and forgot to include the
rest of the bunch. So, here we go again...
Hi Maxime,
Am Freitag, den 20.11.2015, 00:43 +0100 schrieb Maxime Ripard:
> Hi,
>
> On Thu, Nov 19, 2015 at 10:48:35PM +0100, Timo Sigurdsson wrote:
> > Hi Maxime,
of
CONFIG_KEYBOARD_SUN4I_LRADC and not have it removed while cleaning up
Good night,
Timo
Am Freitag, den 20.11.2015, 02:46 +0100 schrieb Timo Sigurdsson:
> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> framework") moved the the sunxi SID driver to a new framework, but left
&
the driver
in multi_v7_defconfig.
Signed-off-by: Timo Sigurdsson <public_tim...@silentcreek.de>
---
Changes in v2:
- Move the extra cleanup work for multi_v7_defconfig to a separate
patch (to be submitted at a later point to avoid conflicts with
another patch waiting to be merged)
---
arch/arm/configs/mu
Hi Maxime,
Hi Chen-Yu,
Am Dienstag, den 17.11.2015, 02:42 +0100 schrieb Timo Sigurdsson:
> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> framework") moved the the sunxi SID driver to a new framework, but left
> sunxi_defconfig with the depre
> http://www.spinics.net/lists/dri-devel/msg93299.html
>>
>> I think the problem here is that I don't see this patch in linux-next
>> yet.
>>
>
> Indeed... and I don't know when it will go there so actually maybe it
> should be removed... but in the same time removing DRM_EXYNO
Hi,
Lee Jones schrieb am 17.11.2015 09:07:
> On Tue, 17 Nov 2015, Timo Sigurdsson wrote:
>
>> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
>> framework") moved the the sunxi SID driver to a new framework, but left
>> multi_v7_defconfig
Hi,
Am Dienstag, den 17.11.2015, 11:10 +0900 schrieb Krzysztof Kozlowski:
> On 17.11.2015 10:49, Timo Sigurdsson wrote:
> > Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> > framework") moved the the sunxi SID driver to a new framework, but le
Hi,
Lee Jones schrieb am 17.11.2015 09:07:
> On Tue, 17 Nov 2015, Timo Sigurdsson wrote:
>
>> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
>> framework") moved the the sunxi SID driver to a new framework, but left
>> multi_v7_defconfig
> http://www.spinics.net/lists/dri-devel/msg93299.html
>>
>> I think the problem here is that I don't see this patch in linux-next
>> yet.
>>
>
> Indeed... and I don't know when it will go there so actually maybe it
> should be removed... but in the same time removing DRM_EXYNO
Hi,
Am Dienstag, den 17.11.2015, 11:10 +0900 schrieb Krzysztof Kozlowski:
> On 17.11.2015 10:49, Timo Sigurdsson wrote:
> > Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> > framework") moved the the sunxi SID driver to a new framework, but le
the driver
in multi_v7_defconfig.
While at it, clean up multi_v7_defconfig by generating a fresh file via
make multi_v7_defconfig
make savedefconfig
While this moves around a few lines and removes unnecessary symbols,
it doesn't introduce any functional changes.
Signed-off-by: Timo Sigurdsson
diff --git
_defconfig.
While at it, clean up sunxi_defconfig by generating a fresh file via
make sunxi_defconfig
make savedefconfig
While this moves around a few lines and removes unnecessary symbols,
it doesn't introduce any functional changes.
Signed-off-by: Timo Sigurdsson
diff --git a/arch/a
_defconfig.
While at it, clean up sunxi_defconfig by generating a fresh file via
make sunxi_defconfig
make savedefconfig
While this moves around a few lines and removes unnecessary symbols,
it doesn't introduce any functional changes.
Signed-off-by: Timo Sigurdsson <public_tim...@silentcr
the driver
in multi_v7_defconfig.
While at it, clean up multi_v7_defconfig by generating a fresh file via
make multi_v7_defconfig
make savedefconfig
While this moves around a few lines and removes unnecessary symbols,
it doesn't introduce any functional changes.
Signed-off-by: Timo Sigurdsson &
at the default voltages inherited by sun7i-a20.dtsi.
Signed-off-by: Timo Sigurdsson
---
Changes since v2:
- (Re)Added board-specific OPP after Kevin Hilman reported problems with
the default voltages at lower frequencies
---
arch/arm/boot/dts/sun7i-a20-bananapi.dts | 45
Hi Maxime,
Maxime Ripard schrieb am 07.10.2015 19:49:
> Hi Timo,
>
> On Wed, Oct 07, 2015 at 05:49:18PM +0200, Timo Sigurdsson wrote:
>> Hi Kevin,
>> Hi Maxime,
>>
>> Kevin Hilman schrieb am 07.10.2015 16:36:
>>
>> > "Timo Sigurdsson"
Hi Kevin,
Hi Maxime,
Kevin Hilman schrieb am 07.10.2015 16:36:
> "Timo Sigurdsson" writes:
>> I still think that the lower voltages may be the cause of your problem
>> with that specific board, so could you please test the attached patch on
>> top of my p
at the default voltages inherited by sun7i-a20.dtsi.
Signed-off-by: Timo Sigurdsson <public_tim...@silentcreek.de>
---
Changes since v2:
- (Re)Added board-specific OPP after Kevin Hilman reported problems with
the default voltages at lower frequencies
---
arch/arm/boot/dts/sun7i-a20-bananapi.dt
Hi Kevin,
Hi Maxime,
Kevin Hilman schrieb am 07.10.2015 16:36:
> "Timo Sigurdsson" <public_tim...@silentcreek.de> writes:
>> I still think that the lower voltages may be the cause of your problem
>> with that specific board, so could you please test the attac
Hi Maxime,
Maxime Ripard schrieb am 07.10.2015 19:49:
> Hi Timo,
>
> On Wed, Oct 07, 2015 at 05:49:18PM +0200, Timo Sigurdsson wrote:
>> Hi Kevin,
>> Hi Maxime,
>>
>> Kevin Hilman schrieb am 07.10.2015 16:36:
>>
>> > "Timo Sigurdsson"
Hi Kevin,
Kevin Hilman schrieb am 24.09.2015 19:57:
> kernelci.org started finding boot faiulres[1] on bananapi linux-next
> around next-20150918, but it was only failing in some labs and not
> others. I finally bisected it down to this patch, which landed in
> linux-next in the form of
Hi Kevin,
Kevin Hilman schrieb am 24.09.2015 19:57:
> kernelci.org started finding boot faiulres[1] on bananapi linux-next
> around next-20150918, but it was only failing in some labs and not
> others. I finally bisected it down to this patch, which landed in
> linux-next in the form of
Hi Kevin,
Kevin Hilman schrieb am 25. Sept 2015 01:57:
> On Tue, Aug 18, 2015 at 8:36 AM, Maxime Ripard
> wrote:
>> On Sun, Aug 02, 2015 at 06:18:25PM +0200, Timo Sigurdsson wrote:
>>> sun7i-a20-bananapi.dts doesn't contain regulator nodes for the AXP209
>>> PMU
&g
Hi Kevin,
Kevin Hilman schrieb am 25. Sept 2015 01:57:
> On Tue, Aug 18, 2015 at 8:36 AM, Maxime Ripard
> <maxime.rip...@free-electrons.com> wrote:
>> On Sun, Aug 02, 2015 at 06:18:25PM +0200, Timo Sigurdsson wrote:
>>> sun7i-a20-bananapi.dts doesn't contain reg
stable across all SoCs and boards out there.
Signed-off-by: Timo Sigurdsson
---
Changes since v1:
- Fixed checkpatch warnings
- Changed the commit message and title to clarify that this is not a
board-specific issue, but rather a limitation by the SoC
---
arch/arm/boot/dts/sun7i-a20.dtsi | 2
. Am I
missing something? Is this not sufficient?
Thanks,
Timo
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/sun7i-a20-bananapi.dts?id=v4.2-rc5#n78
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
Hi Maxime,
Maxime Ripard schrieb am 03.08.2015 11:34:
> On Mon, Aug 03, 2015 at 11:03:52AM +0200, Timo Sigurdsson wrote:
>> Julian Calaby schrieb am 03.08.2015 06:22:
>> > My only real objection here is are there boards that can go down to
>> > 0.9v and if so, won't
Hi Maxime,
Maxime Ripard schrieb am 03.08.2015 11:13:
> On Sun, Aug 02, 2015 at 09:23:06PM +0200, Timo Sigurdsson wrote:
>> sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
>> boards
>> (or all?), however, do not allow the voltage to go be
Hi Maxime,
Maxime Ripard schrieb am 03.08.2015 11:13:
On Sun, Aug 02, 2015 at 09:23:06PM +0200, Timo Sigurdsson wrote:
sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
boards
(or all?), however, do not allow the voltage to go below 1.0V. Thus, raise
the
voltage
Hi Maxime,
Maxime Ripard schrieb am 03.08.2015 11:34:
On Mon, Aug 03, 2015 at 11:03:52AM +0200, Timo Sigurdsson wrote:
Julian Calaby schrieb am 03.08.2015 06:22:
My only real objection here is are there boards that can go down to
0.9v and if so, won't this change make them less power
something? Is this not sufficient?
Thanks,
Timo
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/sun7i-a20-bananapi.dts?id=v4.2-rc5#n78
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
stable across all SoCs and boards out there.
Signed-off-by: Timo Sigurdsson public_tim...@silentcreek.de
---
Changes since v1:
- Fixed checkpatch warnings
- Changed the commit message and title to clarify that this is not a
board-specific issue, but rather a limitation by the SoC
---
arch/arm/boot
1 - 100 of 261 matches
Mail list logo
