Re: [PATCH RFC] Watchdog: sbsa_gwdt: Enhance timeout range

2016-05-05 Thread Timur Tabi
Pratyush Anand wrote: I think, in the long run we must have SBSA watchdog specification improvement to keep WOR as 64 bit. I agree with this 100%. IMHO, using a 32-bit WOR was just a bad decision. -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code

Re: [PATCH RFC] Watchdog: sbsa_gwdt: Enhance timeout range

2016-05-05 Thread Timur Tabi
Guenter Roeck wrote: A 32-bit counter is absolutely fine. Letting it run with a 400MHz clock (or was it 200 MHz ?) is the problem. A resolution of 2.5ns for a watchdog timer does not really make any sense. The 10 second limit is based on a 20MHz clock. -- Qualcomm Innovation Center, Inc. The Q

Re: [PATCH RFC] Watchdog: sbsa_gwdt: Enhance timeout range

2016-05-05 Thread Timur Tabi
Timur Tabi wrote: A 32-bit counter is absolutely fine. Letting it run with a 400MHz clock (or was it 200 MHz ?) is the problem. A resolution of 2.5ns for a watchdog timer does not really make any sense. The 10 second limit is based on a 20MHz clock. No, that's not true. I misread the

Re: [PATCH] makedumpfile: Support ARM64

2015-06-23 Thread Timur Tabi
On Fri, May 15, 2015 at 1:30 PM, Pratyush Anand wrote: > Patch adds support for ARM64 in makedumpfile. It takes care of vmalloc, > vmemmap, module and directly map kernel memory region's translation. > > Currently we only support 2 leverl 64K pages and VA_BITS as 42. Support > to find these machin

Re: [PATCH] makedumpfile: Support ARM64

2015-06-23 Thread Timur Tabi
Pratyush Anand wrote: I can try to find out some time in weekend to refactor arm64 code and then add 3 level, 4K support. May be I will need a Tested-by. We'd be more than happy to test any code from you promptly. We're eager to get this to work. -- Sent by an employee of the Qualcomm Innov

Re: [PATCH 2/6] arm64: Convert hcalls to use HVC immediate value

2015-09-23 Thread Timur Tabi
On Thu, Mar 19, 2015 at 3:35 PM, Geoff Levand wrote: > The existing arm64 hcall implementations are limited in that they only allow > for two distinct hcalls; with the x0 register either zero or not zero. Also, > the API of the hyp-stub exception vector routines and the KVM exception vector > rou

Re: [PATCH 3/4] arm64: Fix KVBASE

2015-12-05 Thread Timur Tabi
Pratyush Anand wrote: + & (0xUL << (VA_BITS - 1)); Shouldn't this be ULL instead of just UL? -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.

[PATCH] elf: add remaining SHF_ flag macros

2025-03-07 Thread Timur Tabi
Add the remaining SHF_ flags, as listed in the "Executable and Linkable Format" Wikipedia page. This allows drivers to load and parse ELF images that use some of those flags. In particular, an upcoming change to the Nouveau GPU driver will use some of the flags. Signed-off-by: