[PATCH] regulator: pf8x00: set ramp_delay for bucks

This patch sets ramp_delay for bucks to the max value given by the datasheet. Signed-off-by: Christoph Fritz --- drivers/regulator/pf8x00-regulator.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator/pf8x00-regulator.c index

[PATCH] regulator: pf8x00: set ramp_delay for bucks

This patch sets ramp_delay for bucks to the max value given by the datasheet. Signed-off-by: Christoph Fritz Reviewed-by: Adrien Grassein --- drivers/regulator/pf8x00-regulator.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator

Re: [PATCH] regulator: pf8x00: Add suspend support

Hello Jagan, as your new role as Maintainer of this driver, is there a chance to get your Feedback/Ack/Review/Signed anytime soon? Thanks -- Christoph On Sun, 2021-01-17 at 21:49 +0100, Christoph Fritz wrote: > This patch adds suspend/resume support so that it is possible to > configu

[PATCH] regulator: pf8x00: Add suspend support

This patch adds suspend/resume support so that it is possible to configure the LDOs and BUCKs as on or off during suspend phase as well as to configure suspend specific voltages. Signed-off-by: Christoph Fritz --- drivers/regulator/pf8x00-regulator.c | 75 ++-- 1 file

[PATCH] regulator: fan53880: Add support for COMPILE_TEST

This patch adds support for COMPILE_TEST while fixing a warning when no support for device tree is there. Reported-by: kernel test robot Signed-off-by: Christoph Fritz --- drivers/regulator/Kconfig| 2 +- drivers/regulator/fan53880.c | 2 ++ 2 files changed, 3 insertions(+), 1 deletion

[PATCH] regulator: fan53880: fix Kconfig dependency

Currently the fan53880 regulator driver needs a device tree to get probed, this patch provides the necessary dependency. Reported-by: kernel test robot Signed-off-by: Christoph Fritz --- drivers/regulator/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers

[PATCH v2 2/2] dt-bindings: regulator: Document bindings for fan53880

Add device tree binding information for fan53880 regulator driver. Signed-off-by: Christoph Fritz --- .../bindings/regulator/onnn,fan53880.yaml | 85 +++ 1 file changed, 85 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/onnn,fan53880.yaml

[PATCH v2 0/2] regulator: Add FAN53880 support

compared to the older FAN53555 which already has driver support. Changelog v1 -> v2: - rebase to current linux-next and adapt by s/struct regulator_linear_range/struct linear_range Christoph Fritz (2): regulator: fan53880: Add initial support dt-bindings: regulator: Document bindings

[PATCH v2 1/2] regulator: fan53880: Add initial support

: Christoph Fritz --- drivers/regulator/Kconfig| 10 ++ drivers/regulator/Makefile | 1 + drivers/regulator/fan53880.c | 179 +++ 3 files changed, 190 insertions(+) create mode 100644 drivers/regulator/fan53880.c diff --git a/drivers/regulator/Kconfig b

Re: [PATCH 1/2] regulator: fan53880: Add initial support

On Wed, 2020-07-01 at 19:09 +0100, Mark Brown wrote: > /mnt/kernel/drivers/regulator/fan53880.c:63:2: note: in expansion of > macro 'FAN53880_LDO' > FAN53880_LDO(1, "VIN12", 280), > ^~~~ > /mnt/kernel/include/linux/regulator/driver.h:47:2: error: field name > not in record or union

[PATCH 1/2] regulator: fan53880: Add initial support

: Christoph Fritz --- drivers/regulator/Kconfig| 10 ++ drivers/regulator/Makefile | 1 + drivers/regulator/fan53880.c | 179 +++ 3 files changed, 190 insertions(+) create mode 100644 drivers/regulator/fan53880.c diff --git a/drivers/regulator/Kconfig b

[PATCH 2/2] dt-bindings: regulator: Document bindings for fan53880

Add device tree binding information for fan53880 regulator driver. Signed-off-by: Christoph Fritz --- .../bindings/regulator/onnn,fan53880.yaml | 85 +++ 1 file changed, 85 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/onnn,fan53880.yaml

[PATCH 0/2] regulator: Add FAN53880 support

compared to the older FAN53555 which already has driver support. Christoph Fritz (2): regulator: fan53880: Add initial support dt-bindings: regulator: Document bindings for fan53880 .../bindings/regulator/onnn,fan53880.yaml | 85 + drivers/regulator/Kconfig | 10

Re: lockup when C1E and high-resolution timers enabled

Hi, the whole error (freeze under heavy IO when C1E enabled) here is referable to motherboard 'GA-970A-UD3P (rev. 1.0)', changing it to a 'Asus M5A97 PLUS' fixes my problems here. I'm not sure if this GA-970A board is just broken or has some general problems. Thanks -- chf -- To unsubscribe

Re: lockup when C1E and high-resolution timers enabled

On Mon, 2015-06-15 at 09:54 +0200, Borislav Petkov wrote: > Just to rule out the aspect that your issue might be fixed by microcode > but that microcode needs to be loaded early, can you enable the early > microcode loader, put the microcode in initrd as described here: > > Documentation/x86/early

Re: lockup when C1E and high-resolution timers enabled

On Sun, 2015-06-14 at 23:24 +0800, Daniel J Blueman wrote: > val=0x$(setpci -s 00:18.3 0xd4.l) # read D18F3xD4 > val=$((val &~(1 << 13))) # clear bit13 (MTC1eEn) > setpci -d 1022:1603 0xd4.l=$(printf %x $val) # write back This slows down the whole system dramatically: - before: MTC1eEn set: Boot

Re: lockup when C1E and high-resolution timers enabled

> > already using latest microcode: > > > > [0.514490] microcode: CPU0: patch_level=0x06000822 > > [0.514497] microcode: CPU1: patch_level=0x06000822 > > [0.514508] microcode: CPU2: patch_level=0x06000822 > > [0.514519] microcode: CPU3: patch_level=0x06000822 > > [0.514529] mic

Re: lockup when C1E and high-resolution timers enabled

On Sun, 2015-06-14 at 15:54 +0800, Daniel J Blueman wrote: > As a workaround, you can probably just disable message triggered C1E > (see the BKDG p399 [1]): > > val=0x$(setpci -s 00:18.4 0xd4.l) # read D18F3xD4 mhm... $(setpci -s 00:18.4 0xd4.l) returns zero, this can't be right. -- To unsubscr

Re: lockup when C1E and high-resolution timers enabled

On Sun, 2015-06-14 at 11:13 +0800, Daniel J Blueman wrote: > On Sunday, June 14, 2015 at 4:00:06 AM UTC+8, Christoph Fritz wrote: > > Hi, > > > > on following computer configuration, I do get hard lockup under heavy > > IO-Load (using rsync): > > > > - CONF

Re: lockup when C1E and high-resolution timers enabled

On Sat, 2015-06-13 at 22:19 +0200, Heinz Diehl wrote: > On 13.06.2015, Christoph Fritz wrote: > > > - add kernel parameter "idle=halt" -> system runs fine > > - disable CONFIG_HIGH_RES_TIMERS -> system runs fine > > - change motherboard and disable C1E

lockup when C1E and high-resolution timers enabled

Hi, on following computer configuration, I do get hard lockup under heavy IO-Load (using rsync): - CONFIG_HIGH_RES_TIMERS=y - CPU: AMD FX(tm)-8350 Eight-Core Processor (family 0x15 model 0x2) - Motherboard: 'GA-970A-UD3P (rev. 1.0)' AMD 970/SB950 - BIOS: C1E enabled (on 'GA-970A-UD3P' there

Re: [PATCH 2/2] UBI: rename_volumes: Use UBI_METAONLY

On Wed, 2014-12-17 at 14:49 -0300, Guido Martínez wrote: > > (for both patches) > Tested-by: Guido Martínez here too, Tested-by: Christoph Fritz By the way, when will this patch get merged? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the b

Re: OMAP: clock DT conversion issues with omap36xx

clock patches" series to l-o > and arm lists, which hopefully solves issues discussed in this thread. Yes, thanks Tomi. I tested your patch series on a83x board. 96m clock and DSS-clocks are fine now. If you want, you can add my: Tested-by: Christoph Fritz to your series "

Re: OMAP: clock DT conversion issues with omap36xx

On Fri, 2014-02-07 at 15:49 +0200, Tomi Valkeinen wrote: > On 07/02/14 12:12, Christoph Fritz wrote: > > > Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want, > > you can add my: > > Tested-by: Christoph Fritz > > > > Below is

Re: OMAP: clock DT conversion issues with omap36xx

On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote: > On 01/29/2014 01:21 PM, Christoph Fritz wrote: > >> Currently I only analyzed sys_clkout2 (see attachments for full > >> clk_summary files): > >> > >> clk_summary__next-20140115__works_as_expected:

Re: OMAP: clock DT conversion issues with omap36xx

On Sat, 2014-02-01 at 19:52 +0100, Christoph Fritz wrote: > On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote: > > To help us debug similar problems, I wrote a tool today: > > https://github.com/nmenon/ctt-dump - it is a simple memory read utility, > > Input

Re: OMAP: clock DT conversion issues with omap36xx

On Wed, Jan 29, 2014 at 04:57:00PM +0200, Tero Kristo wrote: > > Hmm, well, the omap96m_alwon_fck rate is still wrong. Try adding > ti,min-div = <2>; and ti,max-div = <4>; to properties of the clock > node. Hmm, doesn't change anything here. Thanks -- Christoph -- To unsubscribe from this list

Re: OMAP: clock DT conversion issues with omap36xx

On Wed, Jan 29, 2014 at 01:03:52PM -0600, Nishanth Menon wrote: > To help us debug similar problems, I wrote a tool today: > https://github.com/nmenon/ctt-dump - it is a simple memory read utility, > Input file is CTT dump-out > For example: 3630 CTT is here: > http://www.ti.com/pdfs/wtbu/CTT-OMAP3

OMAP: clock DT conversion issues with omap36xx

On Tue, 2014-01-28 at 18:02 +0100, Christoph Fritz wrote: > On Tue, 2014-01-28 at 15:40 +0200, Tero Kristo wrote: > > > > >> Due to a regression since next-20140122 the following errors are present: > > >> > > >> - pin sys_clkout2, which

Re: [BISECTED] OMAP: DSS: clk rate mismatch

On Tue, 2014-01-28 at 11:04 +0200, Tomi Valkeinen wrote: > On 2014-01-27 20:41, Christoph Fritz wrote: > > On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote: > >> linux-next-20140124 DSS is broken on N900 - display stays black (there > >> is some noise though

Re: [BISECTED] OMAP: DSS: clk rate mismatch

On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote: > linux-next-20140124 DSS is broken on N900 - display stays black (there > is some noise though). I booted the kernel with qemu and it gives the > following warning: > > [0.623779] DSS: set fck to 17280 > [0.624237] -

Re: [PATCH v3] ipconfig: add nameserver IPs to kernel-parameter ip=

On Fri, 2012-09-21 at 14:51 -0400, David Miller wrote: > From: Christoph Fritz > Date: Fri, 21 Sep 2012 20:31:19 +0200 > > > On small systems (e.g. embedded ones) IP addresses are often configured > > by bootloaders and get assigned to kernel via parameter "ip=".

[PATCH v3] ipconfig: add nameserver IPs to kernel-parameter ip=

etc/resolv.conf. To configure nameservers for networks without DHCP, this patch adds option and to kernel-parameter 'ip='. Signed-off-by: Christoph Fritz Tested-by: Jan Weitzel --- v2: - fix indent v3: - fix docu: add new arguments to option "ip=" --- Documentation/filesys

[PATCH v2] ipconfig: add nameserver IPs to kernel-parameter ip=

etc/resolv.conf. To configure nameservers for networks without DHCP, this patch adds option and to kernel-parameter 'ip='. Signed-off-by: Christoph Fritz Tested-by: Jan Weitzel --- v2: - fix indent --- Documentation/filesystems/nfs/nfsroot.txt |7 + net/ipv4/ipconfig.

[PATCH] ipconfig: add nameserver IPs to kernel-parameter ip=

etc/resolv.conf. To configure nameservers for networks without DHCP, this patch adds option and to kernel-parameter 'ip='. Signed-off-by: Christoph Fritz Tested-by: Jan Weitzel --- Documentation/filesystems/nfs/nfsroot.txt |7 + net/ipv4/ipconfig.