According to their datasheets, the AXP221, AXP223, AXP288, AXP803,
AXP809 and AXP813 PEK have different values for startup time bits from
the AXP20X PEK (which are currently used for all the aforementioned PMICs).
This patch series adds support for platform_device_id to axp20x-pek driver
to
On 17.07.17 11:26, Yang Zhang wrote:
On 2017/7/14 17:37, Alexander Graf wrote:
On 13.07.17 13:49, Yang Zhang wrote:
On 2017/7/4 22:13, Radim Krčmář wrote:
2017-07-03 17:28+0800, Yang Zhang:
The background is that we(Alibaba Cloud) do get more and more
complaints
from our customers in
Hi Geert
Thanks for your remarks.
Today only write_reg could be call with len=0 (spi-nor.c:
write_enable/disable, set_4byte, erase_chip)
But your remark make sense to prevent: gcc warning and framework
evolution ...
-In stm32-quadspi.c transfer data is enabled if tx_data is true (some
On Mon, Jul 17, 2017 at 12:49 PM, Hanjun Guo wrote:
> On 2017/7/8 23:50, Andy Shevchenko wrote:
>> Sparse complains about wrong address space used in __acpi_map_table()
>> and in __acpi_unmap_table().
>>
>> arch/x86/kernel/acpi/boot.c:127:29: warning: incorrect type in return
>> expression
On Wed, Jul 05, 2017 at 10:56:57AM +0200, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
> > *** Ingo, even if this misses 4.13, please apply the first patch before
> > *** the merge window.
>
> > Andy Lutomirski (10):
> > x86/mm: Don't reenter flush_tlb_func_common()
> > x86/mm: Delete
On Mon, 2017-07-17 at 12:57 +0300, Andy Shevchenko wrote:
> On Mon, Jul 17, 2017 at 12:49 PM, Hanjun Guo
> wrote:
> > On 2017/7/8 23:50, Andy Shevchenko wrote:
> > > Sparse complains about wrong address space used in
> > > __acpi_map_table()
> > > and in __acpi_unmap_table().
> > >
> > >
From: Sean Wang
Sean and Nelson work for MediaTek on maintaining the MediaTek ethernet
driver for the existing SoCs and adding support for the following SoCs.
In the past, Sean has been active at making most of the qualifications
, stress test and submitting a lot of patches for the driver while
From: Sean Wang
The patch adds the supplements in the dt-binding document for MediaTek
MT7622 SoC with extra SGMII system controller and relevant clock consumers
listed as the requirements for those SoCs equipped with the SGMII circuit.
Also, add the missing binding information for MT7623 SoC
From: Sean Wang
Changes since v1:
- add refinement for ethernet clock management
- take out the code block for ESW, add it until ESW driver is actually
introduced
The series adds the driver for ethernet controller found on MT7622 SoC.
There are additions against with previous MT7623 SoC such
From: Sean Wang
This patch is the preparation patch in order to adapt into various
hardware through adding platform data which holds specific characteristics
among MediaTek SoCs and introducing the unified clock handler for those
distinct clock requirements depending on different features such
From: Sean Wang
This patch adds the driver for ethernet controller on MT7622 SoC. It has
the similar handling logic as the previously MT7623 does, but there are
additions against with MT7623 SoC, the shared SGMII given for the dual
GMACs and including 5-ports 10/100 embedded switch support (ESW)
Hi Lee,
On 2017년 07월 17일 18:41, Enric Balletbo i Serra wrote:
> From: Benson Leung
>
> This is the driver for the USB Type C cable detection mechanism
> built into the ChromeOS Embedded Controller on systems that
> have USB Type-C ports.
>
> At present, this allows for the presence of display
Em Mon, 17 Jul 2017 06:33:03 -0300
Mauro Carvalho Chehab escreveu:
> Em Mon, 17 Jul 2017 10:15:26 +0200
> Markus Heiser escreveu:
>
> > > Am 17.07.2017 um 00:08 schrieb Mauro Carvalho Chehab
> > > :
> > >
> > > [1] There's an unrelated bug with the Kernel's sphinx extension
> > > kimage:
From: tiger-yu99
Prior to this patch RPC sleep was uninterruptible since msleep() is
uninterruptible. Change to use msleep_interruptible() instead.
Signed-off-by: Tiger Yu
Reviewed-by: Joakim Bech
Signed-off-by: Jerome Forissier
Signed-off-by: Jens Wiklander
---
drivers/tee/optee/rpc.c | 7
Hello,
Compliment of the day to you. I am Mrs. Elodie, I am sending this brief
letter to solicit your partnership to transfer $5.5 million US Dollars into
your account for investment in your country. I shall send you more information
and procedures when I receive positive response from you.
On Mon, Jul 17, 2017 at 5:14 PM, Maxime Ripard
wrote:
> Hi,
>
> On Fri, Jul 14, 2017 at 02:42:54PM +0800, Chen-Yu Tsai wrote:
>> The MMC2 clock supports a new timing mode. When the new mode is active,
>> the output clock rate is halved.
>>
>> This patch sets the feature flag for the new timing
Hi,
On Mon, Jul 17, 2017 at 02:29:04AM -0700, Tony Lindgren wrote:
> * Sebastian Reichel [170712 08:19]:
> > * Switch from simple-audio-card to audio-graph-card
>
> Gave this a quick try against v4.13-rc1 with SND_AUDIO_GRAPH_CARD
> enabled as a loadable module. However loading it oopses for
James Morse writes:
> compat_ptrace_request() lacks handlers for PTRACE_{G,S}ETSIGMASK,
> instead using those in ptrace_request(). The compat variant should
> read a compat_sigset_t from userspace instead of ptrace_request()s
> sigset_t.
>
> While compat_sigset_t is the same size as sigset_t, it
* Sebastian Reichel [170717 03:13]:
> Hi,
>
> On Mon, Jul 17, 2017 at 02:29:04AM -0700, Tony Lindgren wrote:
> > * Sebastian Reichel [170712 08:19]:
> > > * Switch from simple-audio-card to audio-graph-card
> >
> > Gave this a quick try against v4.13-rc1 with SND_AUDIO_GRAPH_CARD
> > enabled
* Sebastian Reichel [170717 02:52]:
> On Sun, Jul 16, 2017 at 10:59:42PM -0700, Tony Lindgren wrote:
> > Sebastian, for me droid 4 boots just fine with v4.13-rc1 +
> > 19d39a3810e if that helps. So that's with commit 422580c3cea7.
>
> v4.13-rc1 + 19d39a3810e was also broken for me. I just
Mirrors the TEE_DESC_PRIVILEGED bit of struct tee_desc:flags into struct
tee_ioctl_version_data:gen_caps as TEE_GEN_CAP_PRIVILEGED in
tee_ioctl_version()
Reviewed-by: Jerome Forissier
Signed-off-by: Jens Wiklander
---
drivers/tee/tee_core.c | 5 +
include/uapi/linux/tee.h | 1 +
2 files
Hi Ludovic,
On Mon, Jul 17, 2017 at 11:56 AM, Ludovic BARRE wrote:
> Today only write_reg could be call with len=0 (spi-nor.c:
> write_enable/disable, set_4byte, erase_chip)
>
> But your remark make sense to prevent: gcc warning and framework evolution
> ...
>
>
> -In stm32-quadspi.c transfer
Arnd,
sorry for the delayed response, I was away w/o internet connection for
the past weeks.
On 2017-07-10 14:18, Arnd Bergmann wrote:
> Passing uninitialized flags into device_prep_interleaved_dma is clearly
> a bad idea, and we get a compiler warning for it:
>
>
Some code in acpi_parse_x2apic() conditionally compiled, though parts of
it are being used in any case. This annoys gcc.
arch/x86/kernel/acpi/boot.c: In function ‘acpi_parse_x2apic’:
arch/x86/kernel/acpi/boot.c:203:5: warning: variable ‘enabled’ set but not used
[-Wunused-but-set-variable]
u8
Sometimes it's useful to have when mp_config_acpi_legacy_irqs() is called.
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/acpi/boot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index
Sparse complains about wrong address space used in __acpi_map_table()
and in __acpi_unmap_table().
arch/x86/kernel/acpi/boot.c:127:29: warning: incorrect type in return
expression (different address spaces)
arch/x86/kernel/acpi/boot.c:127:29:expected char *
WIP
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/acpi/boot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 71c0feae60a4..4413cc2f7c3c 100644
--- a/arch/x86/kernel/acpi/boot.c
+++
This series does few amendments to architectural ACPI code related to
boot, in particularly to arch/x86/kernel/acpi/boot.c.
First two patches are amendments to satisfy compiler and static analyzer
(the order is changed from first version which had been applied; in case
of partial update first
Some platform might take care of legacy devices on theirs own.
Let's allow them to do that by exporting a weak function.
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/acpi/boot.c | 2 +-
include/linux/acpi.h| 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git
Hi Gwendal,
2017-07-13 22:33 GMT+02:00 Gwendal Grignou :
> On Wed, Jul 12, 2017 at 3:13 AM, Enric Balletbo i Serra
> wrote:
>> The cros_ec_dev driver should be used only to expose the Chrome OS Embedded
>> Controller to user-space and should not be used to add MFD devices by
>> calling
> Am 17.07.2017 um 12:09 schrieb Mauro Carvalho Chehab
> :
>
>>
>> Anyway, I guess we should modify kfigure.py to check if PDF is
>> available, falling back to SVG, using ImageMagick to convert
>> from SVG to PDF.
>
> Ok, I discovered that, on Fedora, support for pdf, png and some other
>
Commit 801bc8193463 ("perf probe: Allow placing uprobes in
alternate namespaces.") is causing a build failure on powerpc:
error: incompatible type for argument 2 of 'get_target_map'
map = get_target_map(pev->target, pev->uprobes);
^~~
Fix it by changing
Add helper functions for mbus to/from mplane pixel format conversion.
Signed-off-by: Todor Tomov
---
include/media/v4l2-mediabus.h | 26 ++
1 file changed, 26 insertions(+)
diff --git a/include/media/v4l2-mediabus.h b/include/media/v4l2-mediabus.h
index 34cc99e..125afcd
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work
with const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1687 592 02279 8e7
These files implement the platform driver code.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss.c | 705 +
drivers/media/platform/qcom/camss-8x16/camss.h | 97
2 files changed, 802 insertions(+)
create mode 100644
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work
with const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
31521096 8425610a0
Update Qualcomm Camera Subsystem driver document for the PIX interface
and format conversion support.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 41 +++---
1 file changed, 31 insertions(+), 10 deletions(-)
diff --git
KMSAN reported use of uninitialized memory in skb_set_hash_from_sk(),
which originated from the TCP request socket created in
cookie_v6_check():
==
BUG: KMSAN: use of uninitialized memory in tcp_transmit_skb+0xf77/0x3ec0
CPU: 1
Add Makefile and update platform/Kconfig and platform/Makefile
to enable building of the QCom CAMSS driver.
Signed-off-by: Todor Tomov
---
drivers/media/platform/Kconfig | 7 +++
drivers/media/platform/Makefile | 2 ++
Extend selection ioctls to handle cropping configuration.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 191 -
drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 +
2 files changed, 150 insertions(+), 42 deletions(-)
diff --git
Use standard V4L2 control to get pixel clock rate from a sensor
linked in the media controller pipeline. Then calculate clock
rates on CSIPHY, CSID and VFE to use the lowest possible.
If the currnet pixel clock rate of the sensor cannot be read then
use the highest possible. This case covers also
Add crop module configuration support to be able to apply cropping.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 41 +-
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/qcom/camss-8x16/camss-vfe.c
Update the Qualcomm Camera Subsystem driver document for VFE scale
and crop modules support.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git
Update the Qualcomm Camera Subsystem driver document with a media
controller pipeline graph diagram.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 27 ++
.../media/v4l-drivers/qcom_camss_graph.dot | 41 ++
2 files
+stable
On 14 July 2017 at 08:42, Chen-Yu Tsai wrote:
> The register for the "new timing mode" also has bit fields for setting
> output and sample timing phases. According to comments in Allwinner's
> BSP kernel, the default values are good enough.
>
> Keep the default values already in the
Add compose selection ioctls to handle scaling configuration.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 189 -
drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 +
2 files changed, 188 insertions(+), 2 deletions(-)
diff --git
Add support for horizontal and vertical frame padding.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 86 +-
.../media/platform/qcom/camss-8x16/camss-video.c | 69 -
.../media/platform/qcom/camss-8x16/camss-video.h |
From: David Wang
In the latest changes of optee_os, the interrupts' names are
changed to "native" and "foreign" interrupts.
Signed-off-by: David Wang
Signed-off-by: Jerome Forissier
Signed-off-by: Jens Wiklander
---
drivers/tee/optee/optee_smc.h | 12 ++--
drivers/tee/optee/rpc.c
Add scaler module configuration support to be able to apply scaling.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 59 +-
1 file changed, 46 insertions(+), 13 deletions(-)
diff --git a/drivers/media/platform/qcom/camss-8x16/camss-vfe.c
These files handle the video device nodes of the camss driver.
Signed-off-by: Todor Tomov
---
.../media/platform/qcom/camss-8x16/camss-video.c | 627 +
.../media/platform/qcom/camss-8x16/camss-video.h | 66 +++
2 files changed, 693 insertions(+)
create mode 100644
These files control the VFE module. The VFE has different input interfaces.
The PIX input interface feeds the input data to an image processing pipeline.
Three RDI input interfaces bypass the image processing pipeline. The VFE also
contains the AXI bus interface which writes the output data to
Use VFE PIX input interface and do format conversion in VFE.
Supported input format is UYVY (single plane YUV 4:2:2) and
its different sample order variations.
Supported output formats are:
- NV12/NV21 (two plane YUV 4:2:0)
- NV16/NV61 (two plane YUV 4:2:2)
Signed-off-by: Todor Tomov
---
These files control the CSID modules which handle the protocol and application
layer of the CSI2 receivers.
Signed-off-by: Todor Tomov
---
.../media/platform/qcom/camss-8x16/camss-csid.c| 1073
.../media/platform/qcom/camss-8x16/camss-csid.h| 82 ++
2 files
These files control the ISPIF module which handles the routing of the data
streams from the CSIDs to the inputs of the VFE.
Signed-off-by: Todor Tomov
---
.../media/platform/qcom/camss-8x16/camss-ispif.c | 1127
.../media/platform/qcom/camss-8x16/camss-ispif.h | 85 ++
On Mon, 2017-07-17 at 16:04 +0530, Arvind Yadav wrote:
> attribute_groups are not supposed to change at runtime. All functions
> working with attribute_groups provided by work
> with const attribute_group. So mark the non-const structs as const.
>
I hope you did compile test it.
> File size
Add a document to describe Qualcomm Camera Subsystem driver.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 124 +
1 file changed, 124 insertions(+)
create mode 100644 Documentation/media/v4l-drivers/qcom_camss.rst
diff --git
On Thu, 22 Jun 2017, Chen-Yu Tsai wrote:
> The X-Powers AXP813 PMIC is normally used with Allwinner's A83T SoC.
> It has the same range of functions as other X-Powers PMICs, such as
> DC-DC buck converter and linear regulator outputs, AC-IN and VBUS
> power supplies, power button trigger, GPIOs,
On 15 July 2017 at 18:27, Julia Lawall wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so a
> break out the loop requires an of_node_put.
>
> The semantic patch that fixes this problem is as follows
> (http://coccinelle.lip6.fr):
>
> //
> @@
> local idexpression n;
>
On Thu, 22 Jun 2017, Chen-Yu Tsai wrote:
> The binding already lists compatibles and regulators for the AXP806,
> but it is missing from the list of supported chips at the beginning.
>
> Add it.
>
> Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC")
> Signed-off-by: Chen-Yu Tsai
These files control the CSIPHY modules which are responsible for the physical
layer of the CSI2 receivers.
Signed-off-by: Todor Tomov
---
.../media/platform/qcom/camss-8x16/camss-csiphy.c | 816 +
.../media/platform/qcom/camss-8x16/camss-csiphy.h | 77 ++
2 files changed,
The local pad parameter in media_entity_remote_pad() is not modified.
Make that explicit by adding a const modifier.
Signed-off-by: Todor Tomov
Acked-by: Sakari Ailus
---
drivers/media/media-entity.c | 2 +-
include/media/media-entity.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Add an entry for Qualcomm Camera subsystem driver.
Signed-off-by: Todor Tomov
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5a9f0f6..4cb978a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10887,6 +10887,14 @@ T: git
From: Sakari Ailus
These formats are compressed 12-bit raw bayer formats with four different
pixel orders. They are similar to 10-bit variants. The formats added by
this patch are
V4L2_PIX_FMT_SBGGR12P
V4L2_PIX_FMT_SGBRG12P
V4L2_PIX_FMT_SGRBG12P
Add DT binding document for Qualcomm Camera subsystem driver.
CC: Rob Herring
CC: devicet...@vger.kernel.org
Signed-off-by: Todor Tomov
---
.../devicetree/bindings/media/qcom,camss.txt | 191 +
1 file changed, 191 insertions(+)
create mode 100644
On Thu, 22 Jun 2017, Chen-Yu Tsai wrote:
> The X-Powers AXP813 is a PMIC designed to be paired with Allwinner's
> A83T SoC. There is also an AXP818, which is paired with the H8 SoC.
>
> The two models seem to be identical, apart from the external markings.
>
> This patch introduces the basic
This patchset adds basic support for the Qualcomm Camera Subsystem found
on Qualcomm MSM8916 and APQ8016 processors.
The driver implements V4L2, Media controller and V4L2 subdev interfaces.
Camera sensor using V4L2 subdev interface in the kernel is supported.
The driver is implemented using as a
On Mon, Jul 17, 2017 at 02:55:37PM +0530, Arvind Yadav wrote:
> attribute_groups are not supposed to change at runtime. All functions
> working with attribute_groups provided by work
> with const attribute_group. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
>
Changes in v3:
* SoB chain corrected
* minor corrections based on v2 feedback
* rebase on linux-next/master as of today
Changes in v2:
* dropped already merged patches
* rebase on top of linux-next/master
* Now by default refcount_t = atomic_t (*) and uses all atomic
standard operations
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
Please start the commit subject description with an uppercase char.
> From: Colin Ian King
This is odd. How are you sending this patch Colin?
> Don't populate the arrays depath and cd_mask on the stack but make
> them static const. Makes the object code smaller:
>
>textdata bss
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
Goldmont microarchitecture supports C1/C3/C6, PC2/PC3/PC6/PC10 state
residency counters, the patch enables them for Apollo Lake platform.
The MSR information is based on Intel Software Developers' Manual,
Vol. 4, Order No. 335592, Table 2-6 and 2-12.
Signed-off-by: Harry Pan
---
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
On Fri, 30 Jun 2017, Sebastian Reichel wrote:
> It is possible that under heavy system load, the counter in the completion
> struct, used for waiting for end of AD conversion, gets incremented twice.
> To make sure the driver recovers from this situation, the completion struct
> should be
On Fri, 30 Jun 2017, Sebastian Reichel wrote:
> DA9052 allows using the touchscreen input pins as general purpose
> analogue input pin by wiring analogue inputs to X+, X-, Y+ and Y-
> and providing a reference voltage at TSIREF pin.
>
> Signed-off-by: Sebastian Reichel
> ---
>
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Suggested-by: Kees Cook
Reviewed-by: David Windsor
Reviewed-by: Hans
On 17/07/17 11:46, Lee Jones wrote:
> Please start the commit subject description with an uppercase char.
>
>> From: Colin Ian King
>
> This is odd. How are you sending this patch Colin?
git send-patch. Hrm. I'll check it out for next time.
Colin
>
>> Don't populate the arrays depath and
On Wed, Jul 12, 2017 at 10:35:04AM -0300, Mauro Carvalho Chehab wrote:
> Each text file under Documentation follows a different format. Some
> doesn't even have titles!
>
> Change its representation to follow the adopted standard,
> using ReST markups for it to be parseable by Sphinx:
>
> -
Em Mon, 17 Jul 2017 07:09:46 -0300
Mauro Carvalho Chehab escreveu:
> Em Mon, 17 Jul 2017 06:33:03 -0300
> Mauro Carvalho Chehab escreveu:
>
> > Em Mon, 17 Jul 2017 10:15:26 +0200
> > Markus Heiser escreveu:
> >
> > > > Am 17.07.2017 um 00:08 schrieb Mauro Carvalho Chehab
> > > > :
> > > >
On Sat, 01 Jul 2017, Hans de Goede wrote:
> Both Bay and Cherry Trail devices may be used together with a Crystal Cove
> PMIC. Each platform has its own variant of the PMIC, which both use the
> same ACPI HID, but they are not 100% compatible.
>
> This commits makes the intel_soc_pmic_core code
On Sat, 01 Jul 2017, Hans de Goede wrote:
> Both Bay and Cherry Trail devices may be used together with a Crystal Cove
> PMIC. Each platform has its own variant of the PMIC, which both use the
> same ACPI HID, but they are not 100% compatible.
>
> Looking at the android x86 kernel sources where
Hi Andy,
On Monday 17 July 2017 04:11 PM, Andy Shevchenko wrote:
On Mon, 2017-07-17 at 16:04 +0530, Arvind Yadav wrote:
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work
with const attribute_group. So mark the non-const
On Thu, 04 May 2017, Julia Lawall wrote:
> Drop static on a local variable, when the variable is initialized before
> any use, on every possible execution path through the function. The static
> has no benefit, and dropping it reduces the code size.
>
> The semantic patch that fixes this
On Thu, 04 May 2017, Julia Lawall wrote:
> Drop static on a local variable, when the variable is initialized before
> any use, on every possible execution path through the function.
>
> The semantic patch that fixes this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @bad
Initially each pin was declared in "include/dt-bindings/stm32f429-pinfunc.h"
and each definition contained SOC names (ex: STM32F429_PA9_FUNC_USART1_TX).
Since this approach was approved, the number of supported MCU has
increased (STM32F429/STM32F469/STM32f746/STM32H743). To avoid to add a new
file
blabla
Signed-off-by: Alexandre TORGUE
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index a8113dc..4bb2b4f 100644
--- a/arch/arm/boot/dts/stm32f429.dtsi
+++ b/arch/arm/boot/dts/stm32f429.dtsi
@@ -47,7 +47,7 @@
#include "skeleton.dtsi"
#include
From: Jun Gao
The speed of sending i2c master code in high-speed mode depends on
source clock, clock-div and TIMING register. The source clock and
clock-div of different SoC are not all the same. In order to send
i2c master code at 400k in high-speed mode, a appropriate value
should be set to
Hi,
> No need of flag here. If vGPU driver is not loaded in the guest,
> there
> is no surface being managed by vGPU, in that case this size will be
> zero.
Ok, we certainly have the same situation with intel. When the guest
driver is not loaded (yet) there is no valid surface.
We should
On Fri, 23 Jun 2017, Hans de Goede wrote:
> The PMIC provides ACPI OpRegions which must be available for other
> drivers' PS0 / PS3 methods early-on as such it must be builtin as the
> Kconfig help text already states.
>
> Somehow its Kconfig option ended up being a tristate though, this fixes
>
1301 - 1400 of 2272 matches
Mail list logo
