> On Fri, Oct 20, 2017 at 12:53:27PM +0300, Elena Reshetova wrote:
> > This series, for nfs components, replaces atomic_t reference
> > counters with the new refcount_t type and API (see
> > include/linux/refcount.h).
> > By doing this we prevent intentional or accidental
> > underflows or
On Sun, Oct 22, 2017 at 01:30:46PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 22 Oct 2017 13:15:16 +0200
>
> A return was performed with the same error code after two condition checks.
> Thus use a single statement instead.
>
It's fine as-is, thanks.
regards,
dan
On Thu, Oct 19, 2017 at 09:33:48PM -0500, Brijesh Singh wrote:
> AMD's new Secure Encrypted Virtualization (SEV) feature allows the
> memory contents of virtual machines to be transparently encrypted with a
> key unique to the VM. The programming and management of the encryption
> keys are handled
On Fri, Oct 20, 2017 at 10:49:46AM -0700, Mike Kravetz wrote:
> On 10/19/2017 07:30 PM, Naoya Horiguchi wrote:
> > On Thu, Oct 19, 2017 at 04:00:07PM -0700, Mike Kravetz wrote:
> >
> > Thank you for addressing this. The patch itself looks good to me, but
> > the reported issue (negative reserve
> On Fri, 20 Oct 2017, Reshetova, Elena wrote:
>
> > Since I am not really sure what to do with this futex patch, I will drop it
> > from the new series that I am about to send now.
> >
> > Please let me know what exactly should I do with this patch, as I wrote
> > previously I really don't
Markus, you should focus on fixing bugs. The original code is fine.
These patches are a waste of reviewer time.
regards,
dan carpenter
On Thu, Oct 19, 2017 at 09:33:49PM -0500, Brijesh Singh wrote:
> The SEV_FACTORY_RESET command can be used by the platform owner to
> reset the non-volatile SEV related data. The command is defined in
> SEV spec section 5.4
>
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Borislav Petkov
> Cc:
The current mainline breakpoints test for arm64 fails to compile with
breakpoint_test_arm64.c: In function ‘set_watchpoint’:
breakpoint_test_arm64.c:97:28: error: storage size of ‘dreg_state’ isn’t known
struct user_hwdebug_state dreg_state;
Adding a direct include for asm/ptrace.h helps it to
Fixed 2 coding style issues.
There was two coding style issues and they were fixed.
c:2233 - unnecessary parenthesis was there, so removed.
c:652 - prohibited space was there, so removed.
Signed-off-by: Woohyung-Jeon
---
drivers/staging/rtlwifi/pci.c | 4 ++--
1 file changed, 2 insertions(+),
On Sat, Oct 21, 2017 at 10:16:12PM +0300, Pavel Nikulin wrote:
> If you say that your lawyers have comprehensively researched that,
> I can't say they did a good job.
Is there a open source knowledgable lawyer that you recommend we work
with in place of the ones that were consulted for this
ignore_func() is limited to check if a symbol has been manually
whitelisted using STACK_FRAME_NON_STANDARD macro. Change the function
description accordingly.
Cc: Ingo Molnar
Signed-off-by: Kamalesh Babulal
---
tools/objtool/check.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
On Sat, Oct 21, 2017 at 04:58:40PM +0530, Vinod Koul wrote:
> On Sat, Oct 21, 2017 at 09:57:44AM +0100, Mark Brown wrote:
> > There's lots of perfectly normal nouns in this document like Slave here
> > which are randomly capitalized. Is there some great reason for this?
> > It makes the document
On Mon, Oct 23, 2017 at 04:44:24PM +0900, Woohyung Jeon wrote:
> Fixed 2 coding style issues.
>
> There was two coding style issues and they were fixed.
> c:2233 - unnecessary parenthesis was there, so removed.
> c:652 - prohibited space was there, so removed.
That's two different things, please
On 21/10/2017 18:20, Guenter Roeck wrote:
This should be part of device programming in manufacturing, just like,
say, current calibration. It should not be user programmable, even less so
runtime programmable. On top of that, we definitely don't want to make
STORE_USER_ALL available to user
Le 28/08/2017 à 15:11, Neil Armstrong a écrit :
> Add JEDEC entry for the Winbond w25q16fw/w25q16dw with similar
> flags and format than the Winbond w25q32dw entry.
>
> Tested on a Khadas VIM2 SBC board with an Amlogic S912 SoC.
>
> Signed-off-by: Neil Armstrong
Applied to the spi-nor/next
On Sun, Oct 22 2017 at 12:15:52 pm BST, Stafford Horne wrote:
> From: Stefan Kristiansson
>
> IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as
> described in the Multi-core support section of the OpenRISC 1.2
> proposed architecture specification:
>
>
>
Hi,
the issue was found on Android using VTS, where its cpuinfo parser stumbled
upon an extra space while trying to extract information about FPU.
By comparing with ARM and Intel it seemed that only MIPS had this quirk in the
cpuinfo format, so we submitted this change to make it conform
to the
On 21/10/17 15:06, Thomas Gleixner wrote:
The recent rework of the cpu hotplug internals changed the usage of the per
cpu state->node field, but missed to clean it up after usage.
So subsequent hotplug operations use the stale pointer from a previous
operation and hand it into the callback
> > HI Paolo, Thanks for your clarify. Have understood. So, we should set
> > "use GPA for processor tracing" in any way( if we can do it) even in
> > system mode. There don't have problem in no nested but have problem in
> > nested if not set this bit. Still talking with hardware designer but
>
On Sun, Oct 22, 2017 at 08:40:36PM +0200, Christian Brauner wrote:
> +/**
> + * insert_extent - Safely insert a new idmap extent into struct uid_gid_map.
> + * Takes care to allocate a 4K block of memory if the number of mappings
> exceeds
> + * UID_GID_MAP_MAX_BASE_EXTENTS.
> + */
> +static int
Claim Donation
We've measured that we spend ~0.6% of sys cpu time in cpumask_next_and().
It's essentially a joined iteration in search for a non-zero bit, which
is currently implemented as a lookup join (find a nonzero bit on the
lhs, lookup the rhs to see if it's set there).
Implement a direct join (find a
On 10/21/2017 09:23 PM, Jonathan Cameron wrote:
> On Sat, 21 Oct 2017 18:54:01 +0100
> Jonathan Cameron wrote:
>
>> On Tue, 17 Oct 2017 15:15:43 +0200
>> Fabrice Gasnier wrote:
>>
>>> STM32H7 ADC channels may be configured either as single-ended or
>>> differential.
>>> Add
On Mon 23-10-17 14:23:09, Joonsoo Kim wrote:
> On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote:
> > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote:
> > > On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote:
> > > > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote:
> > > > > On Thu,
On 10/21/2017 09:25 PM, Jonathan Cameron wrote:
> On Tue, 17 Oct 2017 15:15:45 +0200
> Fabrice Gasnier wrote:
>
>> STM32H7 ADC channels can be configured either as single ended or
>> differential with 'st,adc-channels' or 'st,adc-diff-channels'
>> (positive and negative input pair: , ...).
>>
>>
On Fri, 2017-10-20 at 14:34 -0500, Rob Herring wrote:
> On Fri, Oct 20, 2017 at 3:30 AM, Jerome Brunet wrote:
> > On Thu, 2017-10-19 at 16:18 -0500, Rob Herring wrote:
> > > On Thu, Oct 19, 2017 at 5:25 AM, Kevin Hilman
> > > wrote:
> > > > Rob Herring writes:
> > > >
> > > > > On Thu, Oct 12,
On Fri, Oct 20 2017 at 4:33:35 pm BST, Aleksandar Markovic
wrote:
> From: Miodrag Dinic
>
> Add device driver for a virtual programmable interrupt controller
>
> The virtual PIC is designed as a device tree-based interrupt controller.
>
> The compatible string used by OS for binding the driver
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Signed-off-by: Stephen Lu
---
drivers/input/keyboard/gpio_keys.c | 6 --
1 file changed, 4
On 2017-10-22 17:54, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 22 Oct 2017 16:46:34 +0200
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of these functions.
>
> This issue was detected by using the Coccinelle software.
Acked-by:
Hi Zhi,
I have few comments regarding your patch. Please see them below.
Thanks,
Claudiu
On 22.08.2017 05:09, Zhi Mao wrote:
> Add support to MT2712 and MT7622.
> Due to register offset address of pwm7 for MT2712 is not fixed 0x40,
> add mtk_pwm_reg_offset array for pwm register offset.
>
>
From: Michal Hocko
Both load_elf_interp and load_elf_binary rely on elf_map to map segments
on a controlled address and they use MAP_FIXED to enforce that. This is
however dangerous thing prone to silent data corruption which can be
even exploitable. Let's take CVE-2017-1000253 as an example. At
Fixed a coding style issue.
There was a prohibited space.
Removed.
Signed-off-by: Woohyung-Jeon
---
drivers/staging/rtlwifi/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtlwifi/pci.c b/drivers/staging/rtlwifi/pci.c
index 4035b8835bd1..70a64a5f564a
Hi Hans,
On Mon, Oct 16, 2017 at 7:01 PM, Hans Verkuil wrote:
>> +static long v4l2_jobqueue_device_do_ioctl(struct file *filp, unsigned int
>> cmd,
>> + void *arg)
>> +{
>> + switch (cmd) {
>> + case VIDIOC_JOBQUEUE_INIT:
>> +
Hi Hans,
On Mon, Oct 16, 2017 at 8:06 PM, Hans Verkuil wrote:
> Hi Alexandre,
>
> Thank you very much for working on this. Much appreciated!
Thanks! I feel like there is still a long way before we get this right
though, so your guidance is highly appreciated! :)
> I only did a very high-level
On (10/20/17 15:08), Petr Mladek wrote:
> On Thu 2017-10-19 15:42:35, Sergey Senozhatsky wrote:
> > Sorry for the delay and thanks for taking a look.
> >
> > I'll try to re-spin the patch set by the end of this week/early next
> > week.
> >
> >
> > On (10/04/17 13:53), Petr Mladek wrote:
> >
On Mon, Oct 23, 2017 at 2:55 AM, Masahiro Yamada
wrote:
> Still waiting for DT people?
Nah I gave up now.
> As you know, it is almost deadline
> of DT pull requests to arm-soc maintainers.
>
> If the driver (and binding) is not applied,
> I cannot add GPIO nodes to my DT,
> i.e. I would have
In preparation for unconditionally passing the struct
timer_list pointer to all timer callbacks, switch to using the new
timer_setup() and from_timer() to pass the timer pointer explicitly.
Signed-off-by: Stephen Lu
---
drivers/input/touchscreen/ad7877.c | 6 +++---
1 file changed, 3
On Tue, Oct 10, 2017 at 03:44:03PM +0900, Byungchul Park wrote:
> Changes from v1
> - Enhance commit msg
> - Prevent WARN in cpumask_test_cpu() in cpudl_find() when best_cpu == -1
>
> -8<-
> >From 7735382d07ae6a61d740ae39ba2ecf169d43b8a2 Mon Sep 17 00:00:00 2001
> From: Byungchul Park
On Tue, Oct 10, 2017 at 03:37:53PM +0900, Byungchul Park wrote:
> It would be better to try to check other siblings first if
> SD_PREFER_SIBLING is flaged when pushing tasks - migration.
Is there any opinion about this patch? Could you consider this?
> Suggested-by: Peter Zijlstra
>
Hi Sakari, thanks for the feedback!
On Thu, Oct 19, 2017 at 11:43 PM, Sakari Ailus wrote:
> Hi Alexandre,
>
> On Thu, Sep 28, 2017 at 06:50:18PM +0900, Alexandre Courbot wrote:
>> Hi everyone,
>>
>> Here is a new attempt at the "request" (which I propose to rename "jobs") API
>> for V4L2,
>> ret = i2c_smbus_write_byte_data(client, offset, value);
>> -if (ret < 0) {
>> -dev_err(ctx->dev, "writebm: %4s[0x%02x] <- 0x%02x\n",
>> -sii9234_client_name[id], offset, value);
>> -ctx->i2c_error = ret;
>> -}
>> +if (!ret)
>> +
On Thu, Oct 19, 2017 at 09:33:50PM -0500, Brijesh Singh wrote:
> The SEV_PLATFORM_STATUS command can be used by the platform owner to
> get the current status of the platform. The command is defined in
> SEV spec section 5.5.
>
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Borislav Petkov
>
This business of moving the error code to the bottom of the function
just makes the code less readable. I know you never listen to anyone,
but you should stop doing it.
regards,
dan carpenter
Hi Linus,
On 16/10/17 19:09, Jon Hunter wrote:
> Hi Linus,
>
> On 13/10/17 16:49, Thierry Reding wrote:
>> From: Thierry Reding
>>
>> Hi Linus,
>>
>> here's the latest series of patches that implement the tighter IRQ chip
>> integration. I've dropped the banked infrastructure for now as per the
On Mon, Oct 23, 2017 at 11:26:49AM +0800, jeffy wrote:
> Hi Ard,
>
> On 10/22/2017 09:01 PM, Ard Biesheuvel wrote:
> >On 22 October 2017 at 13:47, Russell King - ARM Linux
> > wrote:
> >>On Sun, Oct 22, 2017 at 12:01:13PM +0100, Ard Biesheuvel wrote:
> >>>On 18 October 2017 at 06:01, Jeffy Chen
On Sun, Oct 22, 2017 at 10:18 PM, Martin Schwidefsky
wrote:
> On Fri, 20 Oct 2017 18:29:33 +0200
> Christoph Hellwig wrote:
>
>> On Fri, Oct 20, 2017 at 08:23:02AM -0700, Dan Williams wrote:
>> > Yes, however it seems these drivers / platforms have been living with
>> > the lack of struct page
The error handling in mvebu_armada_pm_init() is incomplete and this
patch just smudges it around without fixing anything.
regards,
dan carpenter
> This business of moving the error code to the bottom of the function
> just makes the code less readable.
I got an other software development opinion on this aspect.
Could you become used to the proposed control flow structure
in the affected function?
> I know you never listen to anyone,
My
From: Jim Quinlan
> Sent: 20 October 2017 16:28
> On Fri, Oct 20, 2017 at 10:57 AM, Christoph Hellwig wrote:
> > On Fri, Oct 20, 2017 at 10:41:56AM -0400, Jim Quinlan wrote:
> >> I am not sure I understand your comment -- the size of the request
> >> shouldn't be a factor. Let's look at your
On 18/10/17 16:22, Borislav Petkov wrote:
> On Thu, Oct 12, 2017 at 09:47:17AM +0200, Peter Zijlstra wrote:
>> Urgh.. I always get lost in that whole patching maze :/ Unless Juergen
>> can move it later, I think the below should also work. Moving
>> jump_label_init() before smp_prepare_boot_cpu()
On Thu, Oct 19, 2017 at 04:06:32PM -0400, Brian Masney wrote:
> This patch adds a return_max label for the two cases that need to set
> the lux to TSL2X7X_LUX_CALC_OVER_FLOW and return.
>
> Signed-off-by: Brian Masney
> ---
> drivers/staging/iio/light/tsl2x7x.c | 9 -
> 1 file changed,
On Mon, Oct 23, 2017 at 11:01:05AM +0200, SF Markus Elfring wrote:
> > This business of moving the error code to the bottom of the function
> > just makes the code less readable.
>
> I got an other software development opinion on this aspect.
> Could you become used to the proposed control flow
> The error handling in mvebu_armada_pm_init() is incomplete
How would you like to extend it?
> and this patch just smudges it around without fixing anything.
How does this kind of feedback fit to information from the section
“7) Centralized exiting of functions” in the document
From: Bjorn Helgaas
> Sent: 20 October 2017 19:19
> On Fri, Oct 13, 2017 at 09:10:38AM +0530, Pankaj Dubey wrote:
> >
> >
> > On 10/12/2017 04:09 PM, David Laight wrote:
> > >From: Pankaj Dubey
> > >>Sent: 12 October 2017 08:55
> > >>In pcie-designware.c many places we are calling "usleep_range"
>> Could you become used to the proposed control flow structure
>> in the affected function?
>>
>
> No. Don't do this.
Thanks for your information.
> It's pointless obfuscation.
I disagree for this view.
>> There are some challenges around change acceptance as usual.
>
> Yeah. I knew it
On Mon, 16 Oct 2017, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Lee Jones [mailto:lee.jo...@linaro.org]
> > Sent: Friday, October 13, 2017 4:15 PM
> > To: Limonciello, Mario
> > Cc: rui_f...@realsil.com.cn; gre...@linuxfoundation.org; linux-
> >
On 10/20/2017 3:57 PM, Minas Harutyunyan wrote:
> On 10/20/2017 12:20 AM, John Stultz wrote:
>> On Wed, Oct 18, 2017 at 11:46 PM, Minas Harutyunyan
>> wrote:
>>> Could you please apply this patch. Please not apply your patch series
>>> "[PATCH 0/3] dwc2 fixes for edge cases on hikey" to check
On Thu, Oct 19, 2017 at 09:33:48PM -0500, Brijesh Singh wrote:
> +static int __sev_platform_init(struct sev_data_init *data, int *error)
> +{
> + int rc = 0;
> +
> + mutex_lock(_init_mutex);
> +
> + if (!fw_init_count) {
I still don't like global semaphores. Can you get the status and
On Fri, Oct 20, 2017 at 04:51:24PM +0100, Jon Hunter wrote:
> Hi Philipp,
>
> On 19/10/17 16:17, Philipp Zabel wrote:
> > Hi Jon, Thierry,
> >
> > On Wed, 2017-07-19 at 17:59 +0200, Philipp Zabel wrote:
> >> From: Vivek Gautam
> >>
> >> Make use of of_reset_control_array_get_exclusive() to
On Sun, Oct 22, 2017 at 08:23:19PM -0700, santosh.shilim...@oracle.com wrote:
> On 10/10/17 12:19 AM, Mark Brown wrote:
> > a6f244505915f ("ARM: dts: keystone-k2g-evm: Add I2C EEPROM DT entry")
> > I've used the keystone tree from yesterday.
> I fixed this next day but forgot to reply to
On Fri, Oct 06, 2017 at 05:51:30PM +0200, srinivas.kandaga...@linaro.org wrote:
> ---
> Documentation/devicetree/bindings/slimbus/bus.txt | 57 ++
> Documentation/slimbus/summary | 109
This is a 40k patch which is a bit offputting for review. Splitting the
docs out
On Sat, Oct 21, 2017 at 05:05:13PM +0530, Vinod Koul wrote:
> On Sat, Oct 21, 2017 at 10:12:30AM +0100, Mark Brown wrote:
> > On Thu, Oct 19, 2017 at 08:33:19AM +0530, Vinod Koul wrote:
> > > + mutex_lock(>bus_lock);
> > > + if (!list_empty(>slaves))
> > > + list_del(>node);
> >
On Sun, Oct 22, 2017 at 03:36:32PM +0530, Pierre-Louis Bossart wrote:
> On 10/21/17 4:58 PM, Vinod Koul wrote:
> > On Sat, Oct 21, 2017 at 09:57:44AM +0100, Mark Brown wrote:
> > > There's lots of perfectly normal nouns in this document like Slave here
> > > which are randomly capitalized. Is
Hi!
>
> Thank you very much for your time to answer.
> Will create a VM and install all the enviroment needed to start testing.
> Again, thanks for your suggestions!
Using linux-next on some older (32-bit) machine for daily use would be
very valuable. As most people went 64-bit these days, there
Hi!
> > From: Aliaksandr Patseyenak
> >
> > Implement system call for bulk retrieveing of opened descriptors
> > in binary form.
> >
> > Some daemons could use it to reliably close file descriptors
> > before starting. Currently they close everything upto some number
> > which formally is not
Hi!
> BloodTest: an interface to call other analysing tools
>
> Linux kernel has a lot of analysing tools, perf, ftrace, systemtap, KGTP
> and so on.
> And kernel also supplies a lot of internal value from procfs and sysfs
> to analyse the performance.
> fs/proc/stat.c |8
From: Lei Yang
I see two extra binaries are in the untracked file
Untracked files:
(use "git add ..." to include in what will be committed)
tools/testing/selftests/vm/mlock-random-test
tools/testing/selftests/vm/virtual_address_range
Signed-off-by: Lei Yang
---
Hi!
> > drivers/platform/Kconfig| 2 +
> > drivers/platform/Makefile | 1 +
> > drivers/platform/rave/Kconfig | 26 ++
> > drivers/platform/rave/Makefile | 1 +
> > drivers/platform/rave/rave-sp.c | 677
> >
>
> First of all, why
Hi!
> > >> drivers/platform/Kconfig| 2 +
> > >> drivers/platform/Makefile | 1 +
> > >> drivers/platform/rave/Kconfig | 26 ++
> > >> drivers/platform/rave/Makefile | 1 +
> > >> drivers/platform/rave/rave-sp.c | 677
> > >>
> > >
In 30d6e0a4190d ("futex: Remove duplicated code and fix undefined
behaviour"), I let FUTEX_WAKE_OP to fail on invalid op. Namely when
op should be considered as shift and the shift is out of range (< 0 or
> 31).
But strace's test suite does this madness:
futex(0x7fabd78bcffc, 0x5, 0xfacefeed,
On Mon 2017-10-09 21:10:03, Jacek Anaszewski wrote:
> Add missing entries for the following documentation files:
>
> - leds-class-flash.txt
> - leds-lm3556.txt
> - leds-mlxcpld.txt
> - ledtrig-usbport.txt
> - uleds.txt
>
> Signed-off-by: Jacek Anaszewski
Acked-by: Pavel Machek
--
(english)
Hi!
> >> Did you use bounce buffers? Those were improving performance on
> >> some laptops with TI or Ricoh host controllers and nothing else was
> >> ever really using it (as can be seen from the commit).
> >
> > Thinkpad X220... how do I tell if I was using them? I believe so,
> > because I
On Thu, Oct 19, 2017 at 09:33:51PM -0500, Brijesh Singh wrote:
> The SEV_PEK_GEN command is used to generate a new Platform Endorsement
> Key (PEK). The command is defined in SEV spec section 5.6.
>
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Borislav Petkov
> Cc: Herbert Xu
> Cc: Gary
On Thu, 19 Oct 2017, Arnd Bergmann wrote:
> On Thu, Oct 19, 2017 at 5:22 AM, wrote:
> > From: Rui Feng
> >
> > Because Realtek PCIE card reader driver is a pcie driver,
> > and it bridges mmc subsystem and memstick subsystem, it's
> > not a mfd driver. Greg and Lee Jones had a discussion about
Those cases can be passed on fedora-26 with the same kernel(and configuration)
with rhel7.1
[root@localhost perf]# ./perf test vfs_getname
60: Add vfs_getname probe to get syscall args filenames : Ok
61: Use vfs_getname probe to get syscall args filenames : Ok
62: Check open filename arg
The patch
ASoC: rt5651: Convert rt5651 micbias1 to a supply widget
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The userfaultfd code sets the faulting task's state to TASK_KILLABLE for faults
originating from kernel accesses, which prevents the task being frozen during a
hibernate operation. For example, setting a userfaultfd region to trigger on
the signal stack leads to a task that requires a fatal signal
On 21.10.2017 01:25, Paolo Bonzini wrote:
> Two KVM ioctls (KVM_GET/SET_CPUID2) directly access the cpuid_entries
> field of struct kvm_vcpu_arch. Therefore, the new usercopy hardening
> work in linux-next, which forbids copies from and to slab objects
> unless they are from kmalloc or explicitly
The CPU is a CortexM4 @ 200MHZ and the clocks driving
the timers are at 90MHZ with a min delta at 1 you could
have an interrupt each 0.01 ms which is really to much.
By increase it to 0x60 it give more time (around 1 ms)
to CPU to handle the interrupt.
Signed-off-by: Benjamin Gaignard
---
Add this exit function to be able to undo what have been done
in timer_of_init().
Signed-off-by: Benjamin Gaignard
---
drivers/clocksource/timer-of.c | 12
drivers/clocksource/timer-of.h | 3 +++
2 files changed, 15 insertions(+)
diff --git a/drivers/clocksource/timer-of.c
16 bits timers aren't accurate enough to be used as
clocksource, remove them from stm32f4 and stm32f7 devicetree.
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32f429.dtsi | 32
arch/arm/boot/dts/stm32f746.dtsi | 32
The clock driving counters is at 90MHz so resolution is 11 ns and wrap
depends of the number of bits of the counter.
For 32 bits counters the wrap time is around 21 seconds while for 16
bits it is around 0.3 ms which is really to short to be used.
If a 16 bits counter become used it could block
The stm32 timer hardware is currently only used as a clock event device,
but it can be utilized as a clocksource as well.
Implement this by enabling the free running counter in the hardware block
and converting the clock event part from a count down event timer to a
comparator based timer.
Convert driver to use timer_of helpers. This allow to remove
custom proprietary structure.
Signed-off-by: Benjamin Gaignard
---
drivers/clocksource/Kconfig | 1 +
drivers/clocksource/timer-stm32.c | 160 ++
2 files changed, 58 insertions(+), 103
version 7:
- reword "clocksource: stm32: only use 32 bits timers" commit message
to give more details about why 16 bits are problematics.
version 6:
- add dedicated patch min delta change
- rework commit messages, I hope it will be better now
- change new function name from timer_of_deinit
added new line, if messages dropped, so error message not mess with next
one message.
--
--
Best regards,
Maxim Akristiniy
Kernel Developer
Yota Devices
M +7 (916) 967 37 57
E maksim.akristi...@yotadevices.com I
Hi all,
I’ve just put up a blog-entry explaining the rationale behind yaml and device
tree.
https://www.konsulko.com/yaml-and-device-tree/
Please give it a quick glance and give feedback if you can.
Regards
— Pantelis
On 2017/10/20 3:12, Jaegeuk Kim wrote:
> On 10/18, Chao Yu wrote:
>> On 2017/10/18 6:03, Jaegeuk Kim wrote:
>>> On 10/16, Chao Yu wrote:
On 2017/10/14 1:31, Jaegeuk Kim wrote:
> If there's some data written through inline data or dentry, we need to
> shouw
> st_blocks. This fixes
On 2017/10/23 0:01, Jaegeuk Kim wrote:
> On 10/22, Chao Yu wrote:
>> On 2017/10/20 23:53, Jaegeuk Kim wrote:
>>> Before changing readonly, it needs to turn quota off.
>>>
>>> Signed-off-by: Jaegeuk Kim
>>> ---
>>> fs/f2fs/checkpoint.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git
On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote:
> From: Thomas Gleixner
>
> Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
> callback in softirq context and remove the hrtimer_tasklet.
This doesn't build on my tree, due to HRTIMER_MODE_REL_SOFT not
existing.
> On Fri, 20 Oct 2017, Elena Reshetova wrote:
>
> > atomic_t variables are currently used to implement reference
> > counters with the following properties:
> > - counter is initialized to 1 using atomic_set()
> > - a resource is freed upon counter reaching zero
> > - once counter reaches
Hi Philipp,
On Thursday, 19 October 2017 17:54:16 EEST Philipp Zabel wrote:
> On Thu, 2017-10-19 at 16:39 +0300, Laurent Pinchart wrote:
> > On Thursday, 19 October 2017 16:01:54 EEST Philipp Zabel wrote:
> >> On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote:
> >>> In theory the MMSYS
On Mon, 23 Oct 2017, Johannes Berg wrote:
> On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote:
> > From: Thomas Gleixner
> >
> > Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
> > callback in softirq context and remove the hrtimer_tasklet.
I can't build as its part
Hi Russell,
Thanks for your reply.
On 10/23/2017 04:50 PM, Russell King - ARM Linux wrote:
>
>hmm, right, didn't notice the data is already aligned...
>so it's indeed caused by the ksym:
>
> [ 9] .data PROGBITS006ce000 6d6000 000200 00 WA 0
>0 4096
> [10]
On Mon, 2017-10-23 at 12:23 +0200, Thomas Gleixner wrote:
> On Mon, 23 Oct 2017, Johannes Berg wrote:
>
> > On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote:
> > > From: Thomas Gleixner
> > >
> > > Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
> > > callback in
On Mon, 23 Oct 2017, Reshetova, Elena wrote:
> > On Fri, 20 Oct 2017, Elena Reshetova wrote:
> > How did you make sure that these atomic operations have no other
> > serialization effect and can be replaced with refcount?
>
> What serialization effects? Are you taking about smth else than memory
This product is named 'TP-LINK USB 3.0 Gigabit Ethernet Network
Adapter (Model No.is UE300)'. It uses chip RTL8153 and works with
driver drivers/net/usb/r8152.c
Signed-off-by: Ran Wang
---
drivers/net/usb/cdc_ether.c | 8
drivers/net/usb/r8152.c | 2 ++
2 files changed, 10
On 2017.10.23 at 11:48 +0300, Dan Carpenter wrote:
> This business of moving the error code to the bottom of the function
> just makes the code less readable. I know you never listen to anyone,
> but you should stop doing it.
How long have we to put up with this?
He just keeps sending these crap
Hi Bjorn,
On Saturday 21 October 2017 04:39 AM, Bjorn Helgaas wrote:
> On Thu, Oct 19, 2017 at 06:13:29PM +0530, Faiz Abbas wrote:
>> Enable support for printing the LTSSM link state for debugging PCI
>> when link is down.
>>
>> Signed-off-by: Faiz Abbas
>> ---
>> v2:
>> 1. Changed dev_err() to
> On Fri, Oct 20, 2017 at 02:07:53PM +0300, Elena Reshetova wrote:
> > Note: our previous thread didn't finish in any conclusion, so
> > I am resending this now (rebased at latest linux-next) to revive
> > the discussion. refcount_t is slowly becoming a standard for
> > refcounters and we would
701 - 800 of 1330 matches
Mail list logo
