Add to SMP stop common code a best-effort retry logic, re-issuing a stop
request when any CPU is detected to be still online after the first
stop request cycle has completed.
Address the case in which some CPUs could be still starting up when the
stop process is started, remaining so undetected
crash_smp_send_stop() logic was fairly similar to smp_send_stop():
a lot of logic and code was duplicated between the two code paths and
across a few different architectures.
Unify this underlying common logic into the existing SMP common stop
code: use a common workhorse function for both paths
On Fri, Aug 23, 2019 at 3:08 PM Srinivas Kandagatla
wrote:
>
> memory returned as part of nvmem_read via qfprom_read should be
> freed by the consumer once done.
> Existing code is not doing it so fix it.
>
> Below memory leak detected by kmemleak
>[] kmemleak_alloc+0x50/0x84
> []
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On Fri, Aug 23, 2019 at 04:13:46PM +0530, Ganapatrao Kulkarni wrote:
> We are seeing regression with our uncore perf
> Gesendet: Freitag, 23. August 2019 um 12:04 Uhr
> Von: "Mark Brown"
> Can you run a git bisect to try to identify the commit that
> caused things to fail?
i have not figured out, how to rebase linux-next on my current (working)
codebase :) (failes on file untouched by me at Patch 3/7000+)
>
On Fri, Aug 23, 2019 at 5:09 PM Graf (AWS), Alexander wrote:
>
>
>
> > Am 23.08.2019 um 13:18 schrieb Anup Patel :
> >
> >> On Fri, Aug 23, 2019 at 1:34 PM Alexander Graf wrote:
> >>
> >>> On 22.08.19 10:46, Anup Patel wrote:
> >>> From: Atish Patra
> >>>
> >>> The KVM host kernel running in
Hi Josh,
On 8/22/19 8:56 PM, Josh Poimboeuf wrote:
On Fri, Aug 16, 2019 at 01:23:45PM +0100, Raphael Gault wrote:
Hi,
Changes since RFC V3:
* Rebased on tip/master: Switch/jump table had been refactored
* Take Catalin Marinas comments into account regarding the asm macro for
marking
On Fri, Aug 23, 2019 at 01:23:45PM +1000, Dave Chinner wrote:
> > But the fact that RDMA, and potentially others, can "pass the
> > pins" to other processes is something I spent a lot of time trying to work
> > out.
>
> There's nothing in file layout lease architecture that says you
> can't
On 20/08/2019 10:49, Bibby Hsieh wrote:
> The order of gce instructions is [subsys offset value]
> so reorder the parameter of cmdq_pkt_write_mask
> and cmdq_pkt_write function.
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: CK Hu
applied to v5.3-next/soc
Thanks!
> ---
>
Hi Mark,
On Fri, 23 Aug 2019 at 13:59, Mark Brown wrote:
>
> On Fri, Aug 23, 2019 at 11:50:44AM +0100, Mark Brown wrote:
> > On Fri, Aug 23, 2019 at 01:30:27PM +0300, Vladimir Oltean wrote:
>
> > > Did you see this?
> > > https://lkml.org/lkml/2019/8/22/1542
>
> > I'm not online enough to
On 20/08/2019 10:49, Bibby Hsieh wrote:
> According to the cmdq hardware design, the subsys is u8,
> the offset is u16 and the event id is u16.
> This patch changes the type of subsys, offset and event id
> to the correct type.
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: CK Hu
Applied,
On 22 Aug 2019, at 19:12, Ilya Maximets wrote:
Tx code doesn't clear the descriptors' status after cleaning.
So, if the budget is larger than number of used elems in a ring, some
descriptors will be accounted twice and xsk_umem_complete_tx will move
prod_tail far beyond the prod_head
On 23/08/19 13:44, Graf (AWS), Alexander wrote:
>> Overall, I'm quite happy with the code. It's a very clean implementation
>> of a KVM target.
Yup, I said the same even for v1 (I prefer recursive implementation of
page table walking but that's all I can say).
>> I will send v6 next week. I will
On Fri, Aug 23, 2019 at 5:19 PM Alexander Graf wrote:
>
>
>
> On 23.08.19 13:46, Anup Patel wrote:
> > On Fri, Aug 23, 2019 at 5:03 PM Graf (AWS), Alexander
> > wrote:
> >>
> >>
> >>
> >>> Am 23.08.2019 um 13:05 schrieb Anup Patel :
> >>>
> On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf
On Fri, Aug 23, 2019 at 10:34:01AM +0200, Daniel Vetter wrote:
> On Fri, Aug 23, 2019 at 1:14 AM Andrew Morton
> wrote:
> >
> > On Tue, 20 Aug 2019 22:24:40 +0200 Daniel Vetter wrote:
> >
> > > Hi Peter,
> > >
> > > Iirc you've been involved at least somewhat in discussing this. -mm folks
> > >
Hi,
this commit breaks mt6323 pmic on BananaPi-R2
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a4872e80ce7d2a1844328176dbf279d0a2b89bdb
resulting in this message in dmesg:
mt6397 1000d000.pwrap:mt6323: unsupported chip: 0x0
and multiple
mtk-cpufreq
Fixes gcc '-Wunused-but-set-variable' warning:
fs/cifs/file.c: In function cifs_lock:
fs/cifs/file.c:1696:24: warning: variable cinode set but not used
[-Wunused-but-set-variable]
fs/cifs/file.c: In function cifs_write:
fs/cifs/file.c:1765:23: warning: variable cifs_sb set but not used
Add device tree bindings for the On Chip Memory (OCMEM) that is present
on some Qualcomm Snapdragon SoCs.
Signed-off-by: Brian Masney
Reviewed-by: Rob Herring
---
Changes since v6:
- None
Changes since v5:
- None
Changes since v4:
- remove qcom from path in $id
Changes since v3:
- add ranges
From: Rob Clark
Add support to restore the secure configuration for qcm_scm-32.c. This
is needed by the On Chip MEMory (OCMEM) that is present on some
Snapdragon devices.
Signed-off-by: Rob Clark
[masn...@onstation.org: ported to latest kernel; set ctx_bank_num to
spare parameter.]
This patch series adds support for Qualcomm's On Chip MEMory (OCMEM)
that is needed in order to support some a3xx and a4xx-based GPUs
upstream. This is based on Rob Clark's patch series that he submitted
in October 2015 and I am resubmitting updated patches with his
permission. See the individual
From: Rob Clark
Add support for the OCMEM lock/unlock interface that is needed by the
On Chip MEMory (OCMEM) that is present on some Snapdragon devices.
Signed-off-by: Rob Clark
[masn...@onstation.org: ported to latest kernel; minor reformatting.]
Signed-off-by: Brian Masney
Reviewed-by:
The OCMEM driver handles allocation and configuration of the On Chip
MEMory that is present on some Snapdragon SoCs. Devices which have
OCMEM do not have GMEM inside the GPU core, so the GPU must instead
use OCMEM to be functional. Since the GPU is currently the only OCMEM
user with an upstream
Some A3xx and A4xx Adreno GPUs do not have GMEM inside the GPU core and
must use the On Chip MEMory (OCMEM) in order to be functional. Add the
optional ocmem property to the Adreno Graphics Management Unit bindings.
Signed-off-by: Brian Masney
---
Changes since v6:
- link to gmu-sram in example
The files a3xx_gpu.c and a4xx_gpu.c have ifdefs for the OCMEM support
that was missing upstream. Add two new functions (adreno_gpu_ocmem_init
and adreno_gpu_ocmem_cleanup) that removes some duplicated code.
Signed-off-by: Brian Masney
---
Changes since v6:
- None
Changes since v5:
- None
Add ocmem driver that's needed for some a3xx and a4xx based systems.
Signed-off-by: Brian Masney
---
Changes since v6:
- None
Changes since v5:
- None
This patch was introduced in v5.
arch/arm/configs/qcom_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
IIO_ST_SENSORS_CORE select IIO_ST_SENSORS_I2C
unconditionally, if REGMAP_I2C is not set, build fails
drivers/iio/common/st_sensors/st_sensors_i2c.o: In function
`st_sensors_i2c_configure':
st_sensors_i2c.c:(.text+0x58): undefined reference to `__devm_regmap_init_i2c'
This patch selects
On Fri, Aug 23, 2019 at 5:40 PM Paolo Bonzini wrote:
>
> On 23/08/19 13:44, Graf (AWS), Alexander wrote:
> >> Overall, I'm quite happy with the code. It's a very clean implementation
> >> of a KVM target.
>
> Yup, I said the same even for v1 (I prefer recursive implementation of
> page table
On 23.08.19 14:00, Anup Patel wrote:
On Fri, Aug 23, 2019 at 5:09 PM Graf (AWS), Alexander wrote:
Am 23.08.2019 um 13:18 schrieb Anup Patel :
On Fri, Aug 23, 2019 at 1:34 PM Alexander Graf wrote:
On 22.08.19 10:46, Anup Patel wrote:
From: Atish Patra
The KVM host kernel running
The following commit has been merged into the perf/core branch of tip:
Commit-ID: db9a5fd02a06113848fd3eabe302f56059d27366
Gitweb:
https://git.kernel.org/tip/db9a5fd02a06113848fd3eabe302f56059d27366
Author:Jiri Olsa
AuthorDate:Thu, 22 Aug 2019 13:11:37 +02:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 7646602401e6f45e4013ddb7c41f6bc211032d02
Gitweb:
https://git.kernel.org/tip/7646602401e6f45e4013ddb7c41f6bc211032d02
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 11:30:29
The following commit has been merged into the perf/core branch of tip:
Commit-ID: b4df75de3b3930703415aa053a269ae07c78d9b2
Gitweb:
https://git.kernel.org/tip/b4df75de3b3930703415aa053a269ae07c78d9b2
Author:Jiri Olsa
AuthorDate:Thu, 22 Aug 2019 13:11:40 +02:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 315c0a1f0ccdd44c65f80ccbc62202fed8a23050
Gitweb:
https://git.kernel.org/tip/315c0a1f0ccdd44c65f80ccbc62202fed8a23050
Author:Jiri Olsa
AuthorDate:Thu, 22 Aug 2019 13:11:39 +02:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: e740ca86f354038f55978c8ac7bec69b57f0c8e0
Gitweb:
https://git.kernel.org/tip/e740ca86f354038f55978c8ac7bec69b57f0c8e0
Author:Arnaldo Carvalho de Melo
AuthorDate:Thu, 22 Aug 2019 17:15:42
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 6549cd8f2cc2cdf7e107fbbc3a68ecefb774bb2f
Gitweb:
https://git.kernel.org/tip/6549cd8f2cc2cdf7e107fbbc3a68ecefb774bb2f
Author:Jiri Olsa
AuthorDate:Thu, 22 Aug 2019 13:11:38 +02:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 45a2c0ccf6b96b046ad167a8c90ceaa5e59d07cb
Gitweb:
https://git.kernel.org/tip/45a2c0ccf6b96b046ad167a8c90ceaa5e59d07cb
Author:Arnaldo Carvalho de Melo
AuthorDate:Thu, 22 Aug 2019 15:03:37
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 0b8026e8fb0ea3893caa2f1924a2c15fcf6760b3
Gitweb:
https://git.kernel.org/tip/0b8026e8fb0ea3893caa2f1924a2c15fcf6760b3
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 10:54:14
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 964f384989585bc265fd929b2a7977b83fbe4c3b
Gitweb:
https://git.kernel.org/tip/964f384989585bc265fd929b2a7977b83fbe4c3b
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 11:57:50
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 2d64ae9b85614dc0fcca68aad5da305dec44a9b1
Gitweb:
https://git.kernel.org/tip/2d64ae9b85614dc0fcca68aad5da305dec44a9b1
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 11:56:13
On Fri, Aug 23, 2019 at 09:12:34AM -0300, Jason Gunthorpe wrote:
> I still haven't heard a satisfactory answer why a whole new scheme is
> needed and a simple:
>
>if (IS_ENABLED(CONFIG_DEBUG_ATOMIC_SLEEP))
> preempt_disable()
>
> isn't sufficient to catch the problematic cases
The following commit has been merged into the perf/core branch of tip:
Commit-ID: e14e5497d5253712e1545f79ad93309499ffb544
Gitweb:
https://git.kernel.org/tip/e14e5497d5253712e1545f79ad93309499ffb544
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 13:58:12
The following commit has been merged into the perf/core branch of tip:
Commit-ID: bfc49182c64e9dbdea494a577894194701b61e72
Gitweb:
https://git.kernel.org/tip/bfc49182c64e9dbdea494a577894194701b61e72
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:02:05
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 430482c2e34ea8c164240ce295b5f57f16ab5621
Gitweb:
https://git.kernel.org/tip/430482c2e34ea8c164240ce295b5f57f16ab5621
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:02:35
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 69714a4e3959eb051e685c6dce06c6d5a8f27c3c
Gitweb:
https://git.kernel.org/tip/69714a4e3959eb051e685c6dce06c6d5a8f27c3c
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:09:54
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 0f31c0195c14cc37b2f2a08e3f4219d69faa1b34
Gitweb:
https://git.kernel.org/tip/0f31c0195c14cc37b2f2a08e3f4219d69faa1b34
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:00:17
The following commit has been merged into the perf/core branch of tip:
Commit-ID: a06b7f422d6a759b085ab2988d878b70e2dd0064
Gitweb:
https://git.kernel.org/tip/a06b7f422d6a759b085ab2988d878b70e2dd0064
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:24:10
The following commit has been merged into the perf/core branch of tip:
Commit-ID: e4aec1b1bdad744f3afc3ebf2b337ac1bcfa9be0
Gitweb:
https://git.kernel.org/tip/e4aec1b1bdad744f3afc3ebf2b337ac1bcfa9be0
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:01:24
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 43cc5d5ecbd194a730f3045547afc1fa8e694389
Gitweb:
https://git.kernel.org/tip/43cc5d5ecbd194a730f3045547afc1fa8e694389
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:44:25
The following commit has been merged into the perf/core branch of tip:
Commit-ID: ddee688a83073a9beebc5c86b67c712de5861411
Gitweb:
https://git.kernel.org/tip/ddee688a83073a9beebc5c86b67c712de5861411
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:20:54
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 1028f96226b1f4419bd5b56c3d234a83329d4f5b
Gitweb:
https://git.kernel.org/tip/1028f96226b1f4419bd5b56c3d234a83329d4f5b
Author:Arnaldo Carvalho de Melo
AuthorDate:Wed, 21 Aug 2019 14:48:57
Hi Linus,
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.3-rc6
for you to fetch changes up to
On Fri, Aug 23, 2019 at 12:28 AM Dilip Kota wrote:
>
> Add YAML schemas for the reset controller on Intel
> Lightening Mountain (LGM) SoC.
>
> Signed-off-by: Dilip Kota
> ---
> Changes on v2:
> Address review comments
> Update the compatible property definition
> Add description
On Fri, 23 Aug 2019, Russell King - ARM Linux admin wrote:
> On Fri, Aug 23, 2019 at 11:40:50AM +0100, Will Deacon wrote:
> > On Fri, Aug 23, 2019 at 11:36:54AM +0100, Russell King - ARM Linux admin
> > wrote:
> > > To everyone on the long Cc list...
> > >
> > > What's happening with this? I
From: Maxime Ripard
The sun4i_csi_formats array is only used in sun4i_v4l2.c, so it doesn't
make any sense to have it !static.
Reported-by: Hans Verkuil
Signed-off-by: Maxime Ripard
---
drivers/media/platform/sunxi/sun4i-csi/sun4i_v4l2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 23.08.19 14:11, Anup Patel wrote:
On Fri, Aug 23, 2019 at 5:19 PM Alexander Graf wrote:
On 23.08.19 13:46, Anup Patel wrote:
On Fri, Aug 23, 2019 at 5:03 PM Graf (AWS), Alexander wrote:
Am 23.08.2019 um 13:05 schrieb Anup Patel :
On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf
The 08/23/2019 01:26, Nikolay Aleksandrov wrote:
> External E-Mail
>
>
> On 8/23/19 1:09 AM, Nikolay Aleksandrov wrote:
> > On 22/08/2019 22:07, Horatiu Vultur wrote:
> >> Current implementation of the SW bridge is setting the interfaces in
> >> promisc mode when they are added to bridge if
On Fri, 23 Aug 2019, Russell King - ARM Linux admin wrote:
> On Fri, Aug 23, 2019 at 11:43:32AM +0100, Vincenzo Frascino wrote:
> > Hi Russell,
> >
> > On 8/23/19 11:36 AM, Russell King - ARM Linux admin wrote:
> > > Hi,
> > >
> > > To everyone on the long Cc list...
> > >
> > > What's
Sean Christopherson writes:
> Immediately inject a #GP when VMware emulation fails and return
> EMULATE_DONE instead of propagating EMULATE_FAIL up the stack. This
> helps pave the way for removing EMULATE_FAIL altogether.
>
> Rename EMULTYPE_VMWARE to EMULTYPE_VMWARE_GP to help document why a
On 23.08.19 14:19, Anup Patel wrote:
On Fri, Aug 23, 2019 at 5:40 PM Paolo Bonzini wrote:
On 23/08/19 13:44, Graf (AWS), Alexander wrote:
Overall, I'm quite happy with the code. It's a very clean implementation
of a KVM target.
Yup, I said the same even for v1 (I prefer recursive
On Thu, 22 Aug 2019 21:24:45 +0200,
Scott Branden wrote:
>
> Add kernel_pread_file* support to kernel to allow for partial read
> of files with an offset into the file. Existing kernel_read_file
> functions call new kernel_pread_file functions with offset=0 and
> flags=KERNEL_PREAD_FLAG_WHOLE.
On Fri, Aug 23, 2019 at 5:50 PM Alexander Graf wrote:
>
>
>
> On 23.08.19 14:00, Anup Patel wrote:
> > On Fri, Aug 23, 2019 at 5:09 PM Graf (AWS), Alexander
> > wrote:
> >>
> >>
> >>
> >>> Am 23.08.2019 um 13:18 schrieb Anup Patel :
> >>>
> On Fri, Aug 23, 2019 at 1:34 PM Alexander Graf
The older generation i.MX6 processors send a powerdown request interrupt if
the powerkey is released before a hard shutdown (5 second press). This should
allow software to bring down the SoC safely.
For this driver to work as a regular powerkey with the older SoCs, we need to
send a keypress AND
The following commit has been merged into the perf/core branch of tip:
Commit-ID: d9c5c083416500e95da098c01be092b937def7fa
Gitweb:
https://git.kernel.org/tip/d9c5c083416500e95da098c01be092b937def7fa
Author:Gerald BAEZA
AuthorDate:Thu, 22 Aug 2019 09:07:01
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 1ea770f6c1971bc101b3741f4d88b0b4ea5c4181
Gitweb:
https://git.kernel.org/tip/1ea770f6c1971bc101b3741f4d88b0b4ea5c4181
Author:Ravi Bangoria
AuthorDate:Thu, 22 Aug 2019 14:20:45 +05:30
The following commit has been merged into the perf/core branch of tip:
Commit-ID: a2f354e3abb853f9a40048829e1f839e8f7fada5
Gitweb:
https://git.kernel.org/tip/a2f354e3abb853f9a40048829e1f839e8f7fada5
Author:Jiri Olsa
AuthorDate:Thu, 22 Aug 2019 13:11:41 +02:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 5e51b0bb245d963f5ce750256c504be95201e38c
Gitweb:
https://git.kernel.org/tip/5e51b0bb245d963f5ce750256c504be95201e38c
Author:Arnaldo Carvalho de Melo
AuthorDate:Thu, 22 Aug 2019 10:48:31
Hi Steven,
Only one comment, at the bottom.
On 2019/8/21 23:36, Steven Price wrote:
Implement the service call for configuring a shared structure between a
VCPU and the hypervisor in which the hypervisor can write the time
stolen from the VCPU's execution time by other tasks on the host.
The
On Mon, Aug 19, 2019 at 5:12 AM Niklas Cassel wrote:
>
> Add qcom-opp bindings with properties needed for Core Power Reduction
> (CPR).
>
> CPR is included in a great variety of Qualcomm SoCs, e.g. msm8916 and
> msm8996. CPR was first introduced in msm8974.
>
> Co-developed-by: Jorge
This control returns the unit cell size in nanometres. The struct provides
the width and the height in separated fields to take into consideration
asymmetric pixels and/or hardware binning.
This control is required for automatic calibration of sensors/cameras.
Signed-off-by: Ricardo Ribalda
Adding a V4L2_CID_UNIT_CELL_SIZE control requires a lot of boilerplate,
try to minimize it by adding a new helper.
Suggested-by: Philipp Zabel
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 25 -
include/media/v4l2-ctrls.h |
New control to pass to userspace the width/height of a pixel. Which is
needed for calibration and lens selection.
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/uapi/v4l/ext-ctrls-image-source.rst | 8
1 file changed, 8 insertions(+)
diff --git
A struct v4l2_area containing the width and the height of a rectangular
area.
Signed-off-by: Ricardo Ribalda Delgado
Suggested-by: Hans Verkuil
---
Documentation/media/uapi/v4l/vidioc-queryctrl.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git
According to the product brief, the unit cell size is 1120 nanometers^2.
https://www.sony-semicon.co.jp/products_en/IS/sensor1/img/products/ProductBrief_IMX214_20150428.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/i2c/imx214.c | 23 +++
1 file changed, 23
Instead of creating manually the V4L2_CID_UNIT_CELL_SIZE control, lets
use the helper.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/i2c/imx214.c | 29 -
1 file changed, 8 insertions(+), 21 deletions(-)
diff --git a/drivers/media/i2c/imx214.c
Helper for creating area controls.
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/kapi/v4l2-controls.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/media/kapi/v4l2-controls.rst
b/Documentation/media/kapi/v4l2-controls.rst
index
The 08/22/2019 22:08, Andrew Lunn wrote:
> External E-Mail
>
>
> > +/* Determin if the SW bridge can be offloaded to HW. Return true if all
> > + * the interfaces of the bridge have the feature NETIF_F_HW_SWITCHDEV set
> > + * and have the same netdev_ops.
> > + */
>
> Hi Horatiu
>
> Why do
Some chromebook EC provides a counter to get all vsync coming from the back
camera.
This series introduces a patch coming from chromebook kernel 4.4 designed as an
IIO counter. As IIO counter will be deprecated in favor of counter, I rebase the
original patch and support the new counter API.
The
On 23/08/2019 17:57:38+0800, Biwen Li wrote:
> The patch supports flextimer for lx2160a
>
> Signed-off-by: Biwen Li
> ---
> drivers/rtc/rtc-fsl-ftm-alarm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c
> index
From: Gwendal Grignou
EC returns a counter when there is an event on camera vsync.
This patch comes from chromeos kernel 4.4
Signed-off-by: Gwendal Grignou
Signed-off-by: Fabien Lahoudere
CROS EC sync sensor was originally designed as an IIO device.
Now that the counter subsystem will
If WATCHDOG_CORE is not set, build fails:
drivers/rtc/rtc-pcf2127.o: In function `pcf2127_probe.isra.6':
drivers/rtc/rtc-pcf2127.c:478: undefined reference to
`devm_watchdog_register_device'
Add WATCHDOG_CORE Kconfig dependency to fix this.
Reported-by: Hulk Robot
Fixes: bbc597561ce1 ("rtc:
If no BAT is given to setbat(), select an available BAT.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s32/mmu.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/book3s32/mmu.c b/arch/powerpc/mm/book3s32/mmu.c
index
On mpc83xx with a QE, IMMR is 2Mbytes.
On mpc83xx without a QE, IMMR is 1Mbytes.
Each driver will map a part of it to access the registers it needs.
Some driver will map the same part of IMMR as other drivers.
In order to reduce TLB misses, map the full IMMR with a BAT.
Signed-off-by: Christophe
On Tue, May 7, 2019 at 7:36 AM Nicolin Chen wrote:
>
> The addresses within a single page are always contiguous, so it's
> not so necessary to always allocate one single page from CMA area.
> Since the CMA area has a limited predefined size of space, it may
> run out of space in heavy use cases,
Commit 8c3088f895a0 ("tcp: be more careful in tcp_fragment()")
triggers following stack trace:
[25244.848046] kernel BUG at ./include/linux/skbuff.h:1406!
[25244.859335] RIP: 0010:skb_queue_prev+0x9/0xc
[25244.888167] Call Trace:
[25244.889182]
[25244.890001] tcp_fragment+0x9c/0x2cf
Now, the ChromeOS EC core driver has nothing related to an MFD device, so
move that driver from the MFD subsystem to the platform/chrome subsystem.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Acked-by: Thierry Reding
Acked-by: Mark Brown
Acked-by: Wolfram Sang
Acked-by:
Hi,
Now that rc1 is released is time to send another patchset rebased on
top. This is an attempt to clean up a bit more the cros-ec driver
to have a better separation on what is part of the MFD subsystem and
what is part of platform/chrome.
The major changes introduced by this patchset are:
1.
With the purpose of remove the things that far extends the bounds of
what a MFD was designed to do, instantiate the new platform misc
cros-ec-chardev driver and get rid of all the unneeded code. After this
patch the misc chardev driver is a sub-device of the MFD, and all the
new file operations
An MFD is a device that contains several sub-devices (cells). For instance,
the ChromeOS EC fits in this description as usually contains a charger and
can have other devices with different functions like a Real-Time Clock,
an Audio codec, a Real-Time Clock, ...
If you look at the driver, though,
The cros-ec-dev is a multifunction device that now doesn't implement any
chardev communication interface. MFD_CROS_EC_CHARDEV doesn't look
a good name to describe that device and can cause confusion. Hence
rename it to CROS_EC_DEV.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
That's a driver to talk with the ChromeOS Embedded Controller via a
miscellaneous character device, it creates an entry in /dev for every
instance and implements basic file operations for communicating with the
Embedded Controller with an userspace application. The API is moved to
the uapi folder,
Recently we refactored the CrOS EC drivers moving part of the code from
the MFD subsystem to the platform chrome subsystem. During this change
we needed to rename some config options, so, update the defconfigs
accordingly.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Krzysztof Kozlowski
With the increasing use of dedicated CrOS EC MCUs, it takes a fair amount
of boiler plate code to add those devices, add a struct that can be used
to specify a dedicated CrOS EC MCU so we can just add a new item to it to
define a new dedicated MCU.
Signed-off-by: Enric Balletbo i Serra
Acked-by:
Use mfd_add_hotplug_devices() helper to register the subdevices. The
helper allows us to reduce the boiler plate and also registers the
subdevices in the same way as used in other functions used in this
files.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal
This patch makes use of cros_ec_cmd_xfer_status() instead of
cros_ec_cmd_xfer() so we can remove some redundant code. It also uses
kzalloc instead of kmalloc so we can remove more redundant code.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Reviewed-by: Gwendal Grignou
There is a bit of mess between cros-ec mfd includes and platform
includes. For example, we have a linux/mfd/cros_ec.h include that
exports the interface implemented in platform/chrome/cros_ec_proto.c. Or
we have a linux/mfd/cros_ec_commands.h file that is non related to the
multifunction device
The CrOS EC is gaining lots of subdevices that are autodetectable by
sending the EC_FEATURE_GET_CMD, it takes fair amount of boiler plate
code to add those devices. So, add a struct that can be used to quickly
add new subdevices without having to duplicate code.
Signed-off-by: Enric Balletbo i
On Fri, Aug 23, 2019 at 11:37:38AM +0800, Tanwar, Rahul wrote:
> On 22/8/2019 9:04 PM, Andy Shevchenko wrote:
> > On Thu, Aug 22, 2019 at 05:26:33PM +0800, Tanwar, Rahul wrote:
> > > On 22/8/2019 5:02 PM, Andy Shevchenko wrote:
> > > > On Thu, Aug 22, 2019 at 03:44:03PM +0800, Rahul Tanwar wrote:
Hi,
When other cores want to use EDMA for their use cases Linux was not playing
nicely.
By design EDMA is supporting shared use with shadow regions. Linux is using
region0, others can be used by other cores.
In order to not break multicore shared usage of EDMA:
- do not reset paRAM slots which
bitmap_set() is the standard way of setting an area in the bitfield.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/ti/edma.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/dma/ti/edma.c b/drivers/dma/ti/edma.c
index 87450431f336..ba7c4f07fcd6
Like paRAM slots, channels could be used by other cores and in this case
we need to make sure that the driver do not alter these channels.
Move the reserved slot/channel query from DT to a separate function for
cleaner implementation.
Signed-off-by: Peter Ujfalusi
---
drivers/dma/ti/edma.c |
Similarly to paRAM slots, channels can be used by other cores.
Add optional property to configure the reserved channel ranges.
Signed-off-by: Peter Ujfalusi
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 5 +
1 file changed, 5 insertions(+)
diff --git
701 - 800 of 850 matches
Mail list logo
