* changhuaixin wrote:
> Hi, Ingo
>
> Another way to write SHT_PROGBITS is using elf_create_section to write
> orc_lookup table headers, when orc_unwind_ip table and orc_unwind table are
> written. Is this a better solution?
>
> diff --git a/tools/objtool/orc_gen.c b/tools/objtool/orc_gen.c
On Wed, Jun 17, 2020 at 06:29:44AM +0300, Jason Wang wrote:
> This patch introduce a config op to get valid iova range from the vDPA
> device.
>
> Signed-off-by: Jason Wang
> ---
> include/linux/vdpa.h | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff --git a/include/linux/vdpa.h
On Thursday, 2020-07-16 at 16:52:49 +03, Jarkko Sakkinen wrote:
> From: Sean Christopherson
>
> Add vm_ops()->mprotect() for additional constraints for a VMA.
>
> Intel Software Guard eXtensions (SGX) will use this callback to add two
> constraints:
>
> 1. Verify that the address range does not ha
My Dear in the lord
My name is Mrs. Mina A. Brunel I am a Norway Citizen who is living in Burkina
Faso, I am married to Mr. Brunel Patrice, a politicians who owns a small gold
company in Burkina Faso; He died of Leprosy and Radesyge, in year February
2010, During his lifetime he deposited t
From: Andrei Botila
A hardware limitation exists for CAAM until Era 9 which restricts
the accelerator to IVs with only 8 bytes. When CAAM has a lower era
a fallback is necessary to process 16 bytes IV.
Fixes: c6415a6016bf ("crypto: caam - add support for acipher xts(aes)")
Cc: # v4.4+
Signed-of
From: Andrei Botila
Newer CAAM versions (Era 9+) support 16B IVs. Since for these devices
the HW limitation is no longer present newer version should process the
requests containing 16B IVs directly in hardware without using a fallback.
Signed-off-by: Andrei Botila
---
drivers/crypto/caam/caam
* pet...@infradead.org [2020-08-06 15:15:47]:
> > But my understanding is most LPARs don't get migrated back and forth,
> > they'll start life on a P8 and only get migrated to a P9 once when the
> > customer gets a P9. They might then run for a long time (months to
> > years) on the P9 in P8 comp
From: Andrei Botila
A hardware limitation exists for CAAM until Era 9 which restricts
the accelerator to IVs with only 8 bytes. When CAAM has a lower era
a fallback is necessary to process 16 bytes IV.
Fixes: b189817cf789 ("crypto: caam/qi - add ablkcipher and authenc algorithms")
Cc: # v4.12+
From: Andrei Botila
CAAM accelerator only supports XTS-AES-128 and XTS-AES-256 since
it adheres strictly to the standard. All the other key lengths
are accepted and processed through a fallback as long as they pass
the xts_verify_key() checks.
Fixes: b189817cf789 ("crypto: caam/qi - add ablkciph
From: Andrei Botila
Newer CAAM versions (Era 9+) support 16B IVs. Since for these devices
the HW limitation is no longer present newer version should process the
requests containing 16B IVs directly in hardware without using a fallback.
Signed-off-by: Andrei Botila
---
drivers/crypto/caam/caam
A recent commit introduced a late error path in phy_device_create()
which fails to release the device name allocated by dev_set_name().
Fixes: 13d0ab6750b2 ("net: phy: check return code when requesting PHY driver
module")
Cc: Heiner Kallweit
Signed-off-by: Johan Hovold
---
drivers/net/phy/phy_
Hyper-V currently may be notified of a panic for any die event. But
this results in false panic notifications for various user space traps
that are die events. Fix this by ignoring die events that aren't oops.
Fixes: 510f7aef65bb ("Drivers: hv: vmbus: prefer 'die' notification chain to
'panic'")
On 06/08/20 15:07, Ingo Molnar wrote:
> * Valentin Schneider wrote:
>
>> +#ifndef SD_FLAG
>> +#define SD_FLAG(x, y, z)
>> +#endif
>
> AFAICS there's not a single use of sd_flags.h that doesn't come with
> its own SD_FLAG definition, so I suppose this should be:
>
> #ifndef SD_FLAG
> # error "Sho
* pet...@infradead.org [2020-08-06 10:54:29]:
> On Thu, Aug 06, 2020 at 03:32:25PM +1000, Michael Ellerman wrote:
>
> > That brings with it a bunch of problems, such as existing software that
> > has been developed/configured for Power8 and expects to see SMT8.
> >
> > We also allow LPARs to be
On 8/6/20 9:42 AM, Sowjanya Komatineni wrote:
On 8/6/20 9:37 AM, Dmitry Osipenko wrote:
06.08.2020 19:13, Dmitry Osipenko пишет:
06.08.2020 18:59, Sowjanya Komatineni пишет:
..
We cant use active status check for specific pads under calibration.
This is common bit for all pads.
I'm not sur
On Thu, Aug 6, 2020 at 7:46 AM wrote:
>
> On 2020-08-05 21:18, Rob Clark wrote:
> > On Wed, Aug 5, 2020 at 6:34 AM Kalyan Thota
> > wrote:
> >>
> >> In TEST_ONLY commit, rm global_state will duplicate the
> >> object and request for new reservations, once they pass
> >> then the new state will be
On Thu, 06 Aug 2020 12:51:34 +0200,
Colin King wrote:
>
> From: Colin Ian King
>
> There is a spelling mistake in a usb_audio_dbg debug message. Also
> replace "param" with "parameter". Fix these.
>
> Signed-off-by: Colin Ian King
Applied, thanks.
Takashi
Hi Mark-PK,
On Thu, 6 Aug 2020 at 23:08, Mark-PK Tsai wrote:
> > Do you know if it would be possible to confirm if they are
> > the
> > same thing? MediaTek bought MStar a few years ago so it seems likely
> > but I have no hard information.
> >
>
> Yes, it's for the same interrupt controller IP.
On 8/6/20 5:39 PM, Matthew Wilcox wrote:
>> >> +++ b/mm/huge_memory.c
>> >> @@ -2125,7 +2125,7 @@ static void __split_huge_pmd_locked(struct
>> >> vm_area_struct *vma, pmd_t *pmd,
>> >>* Set PG_double_map before dropping compound_mapcount to avoid
>> >>* false-negative page_mapped().
>> >>
From: Andrei Botila
This patch series fixes some problems in CAAM's implementation of xts(aes):
- CAAM until Era 9 can't process XTS with 16B IV
- CAAM can only process in hardware XTS key lengths of 16B and 32B
- These hardware limitations are resolved through a fallback
This patch series al
* Valentin Schneider wrote:
> This does sound sensible; I can shuffle this around for v5.
Thanks!
> FWIW the reason I had this very patch before the instrumentation is that
> IMO it really wants to be propagated and could thus directly be tagged with
> SDF_SHARED_PARENT when the instrumentati
06.08.2020 19:41, Sowjanya Komatineni пишет:
...
>> What about to add 72us delay to the end of start_calibration() in order
>> to ensure that FSM is finished before LP-11?
>
> Why we should add 72uS in start_calibration() when can use same
> finish_calibration() for both pass/fail cases?
>
> Only
On Wed, 05 Aug 2020 18:05:18 +0200, Sebastian Reichel wrote:
> This adds support for EXC80H60 and EXCH84 controllers, which
> use a different event type id and have two extra bits for the
> resolution (so the maximum is 16K instead of 4K).
>
> Signed-off-by: Sebastian Reichel
> ---
> .../input/t
From: Colin Ian King
There are several variables that are being initialized with values
that are never read and the variables are being re-assigned later
on. Remove the redundant initializations.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
drivers/thermal/mtk_thermal
On Thu, Aug 6, 2020 at 9:09 AM Jann Horn wrote:
>
> On Thu, Aug 6, 2020 at 1:19 PM syzbot
> wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit 4b836a1426cb0f1ef2a6e211d7e553221594f8fc
> > Author: Jann Horn
> > Date: Mon Jul 27 12:04:24 2020 +
> >
> > binder: Prev
It will be used later for BPF structure display support
Signed-off-by: Alan Maguire
---
include/linux/bpf.h | 2 ++
kernel/bpf/verifier.c | 18 --
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/include/linux/bpf.h b/include/linux/bpf.h
index cef4ef0..55eb67d 1
On 8/6/20 9:37 AM, Dmitry Osipenko wrote:
06.08.2020 19:13, Dmitry Osipenko пишет:
06.08.2020 18:59, Sowjanya Komatineni пишет:
..
We cant use active status check for specific pads under calibration.
This is common bit for all pads.
I'm not sure why this is a problem.
IIUC, the start_calib
Hi Linus,
Please pull dlm updates from tag:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-5.9
This set includes a some improvements to the dlm networking layer:
improving the ability to trace dlm messages for debugging, and improved
handling of bad messages or disrupte
>
> I don't get this. If the platform driver already stated 240 and 960 samples
> why
> would 432 be chosen? Doesn't this mean the constraint is not applied?
Hi Pierre,
Sorry for late reply. I used following constraints in V3 patch so any period
which
aligns 1ms would be accepted.
+ /*
This allows the driver to move bigger data block when the backend allows
it.
Add a backend buffer_size for this purpose. For the moment only
virtio-rng defines it.
Using bigger buffer with virtio-rng improves performance from:
# dd if=/dev/hwrng of=/dev/null bs=1024 count=1024000
1048576000
On Wed, 5 Aug 2020, Roman Gushchin wrote:
> On Wed, Aug 05, 2020 at 08:01:33PM -0700, Hugh Dickins wrote:
> >
> > I shall certainly want to reintroduce those stats to checking for
> > negatives, even if it's in a patch that never earns your approval,
> > and just ends up kept internal for debuggin
On Sun, Jul 26, 2020 at 09:19:28PM +0530, Manivannan Sadhasivam wrote:
> Hi,
>
> Sorry for the late reply!
No worries at all.
> On Wed, Jul 01, 2020 at 12:34:33PM +0200, Johan Hovold wrote:
> > On Sun, Jun 07, 2020 at 09:53:48PM +0530, Manivannan Sadhasivam wrote:
> > > Add support for MaxLinear
On Tue, Aug 04, 2020 at 11:20:21AM +0200, Pavel Machek wrote:
> On Tue 2020-08-04 11:18:17, Pavel Machek wrote:
> > Hi!
> >
> > > The commit text again to make checkpatch happy.
> >
> > ?
> >
> >
> > > +oneOf:
> > > + - items:
> > > + - const: ctu,ctucanfd
> > > + - c
On Wed, Aug 05, 2020 at 12:15:54PM -0700, Nick Desaulniers wrote:
> On Wed, Aug 5, 2020 at 11:19 AM Sami Tolvanen wrote:
> >
> > Commit 7c78f67e9bd9 ("arm64: enable tlbi range instructions") breaks
> > LLVM's integrated assembler, because -Wa,-march is only passed to
> > external assemblers and th
On 31/07/2020 13:54, Valentin Schneider wrote:
> Hi,
>
> I've repeatedly stared at an SD flag and asked myself "how should that be
> set up in the domain hierarchy anyway?". I figured that if we formalize our
> flags zoology a bit, we could also do some runtime assertions on them -
> this is what
On 06/08/20 15:20, Ingo Molnar wrote:
> * Valentin Schneider wrote:
>
>> We currently set this flag *only* on domains whose topology level exactly
>> match the level where we detect asymmetry (as returned by
>> asym_cpu_capacity_level()). This is rather problematic.
>>
>> Say there are two clust
- On Aug 6, 2020, at 8:13 AM, Will Deacon w...@kernel.org wrote:
> On Wed, Aug 05, 2020 at 11:22:36AM -0400, Mathieu Desnoyers wrote:
>> - On Aug 5, 2020, at 6:59 AM, Peter Zijlstra pet...@infradead.org wrote:
>> > On Tue, Aug 04, 2020 at 07:01:53PM +0200, pet...@infradead.org wrote:
>> >>
On Thursday, 2020-07-16 at 16:52:53 +03, Jarkko Sakkinen wrote:
> Add an ioctl that performs ENCLS[EINIT], which locks down the measurement
> and initializes the enclave for entrance. After this, new pages can no
> longer be added.
>
> Acked-by: Jethro Beekman
> Tested-by: Jethro Beekman
> Tested
Hi,
On Thu 06 Aug 20, 12:12, Ezequiel Garcia wrote:
> From: Jernej Skrabec
>
> When dealing with with interlaced frames, reference lists must tell if
> each particular reference is meant for top or bottom field. This info
> is currently not provided at all in the H264 related controls.
>
> Make
On Sun, Jul 26, 2020 at 09:22:23PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Jul 01, 2020 at 03:02:06PM +0200, Johan Hovold wrote:
> > On Sun, Jun 07, 2020 at 09:53:49PM +0530, Manivannan Sadhasivam wrote:
> > > Add gpiochip support for Maxlinear/Exar USB to serial converter
> > > for controlli
On 8/6/20 9:10 AM, Dmitry Osipenko wrote:
06.08.2020 18:59, Sowjanya Komatineni пишет:
...
Confirmed from HW designer, calibration FSM to finish takes worst case
72uS so by the time it gets to sensor stream it will be done its
sequence and will be waiting for DONE bit.
So disabling MIPI CAL c
Since commit c5cd2b47b203 ("platform/chrome: cros_ec_proto: Report command
not supported") we can no longer assume that cros_ec_cmd_xfer_status()
reports -EPROTO for all errors returned by the EC itself. A follow-up
patch will change cros_ec_cmd_xfer_status() to report additional errors
reported by
The EC reports a variety of error codes. Most of those, with the exception
of EC_RES_INVALID_VERSION, are converted to -EPROTO. As result, the actual
EC error code gets lost. Introduce cros_ec_map_error() to map EC error
codes to Linux error codes, and use it in cros_ec_cmd_xfer_status() to
report
On 8/6/20 6:58 AM, Qian Cai wrote:
> linux-next failed to compile using this .config,
> https://gitlab.com/cailca/linux-mm/-/blob/master/arm64.config
>
> arch/arm64/kernel/kaslr.c: In function 'kaslr_early_init':
> arch/arm64/kernel/kaslr.c:128:6: error: implicit declaration of function
> '__early
On 8/6/20 9:45 AM, Dmitry Osipenko wrote:
06.08.2020 19:41, Sowjanya Komatineni пишет:
...
What about to add 72us delay to the end of start_calibration() in order
to ensure that FSM is finished before LP-11?
Why we should add 72uS in start_calibration() when can use same
finish_calibration()
Make use of SCCB APIs for regmap operations.
Remove i2c_check_functionality as devm_regmap_init_sccb
does it for us.
Signed-off-by: Raag Jadav
---
Changes since v1:
- Changed commit message.
- Added SCCB config for ov7740.
drivers/media/i2c/Kconfig | 2 +-
drivers/media/i2c/ov7740.c | 10 +---
* Dan Williams wrote:
> On Thu, Aug 6, 2020 at 6:35 AM Ingo Molnar wrote:
> >
> >
> > * kernel test robot wrote:
> >
> > > Greeting,
> > >
> > > FYI, we noticed a -43.3% regression of fio.read_iops due to commit:
> > >
> > >
> > > commit: a0ac629ebe7b3d248cb93807782a00d9142fdb98 ("x86/copy_mc
On Thu, Aug 06, 2020 at 08:04:07PM +0800, 姜迎 wrote:
>
>
>
> Hi all,
> This patch is used to fix checkpatch error on kernel stable rc 4.9.
> I have built pass and tested pass, thanks!
Now queued up, thanks!
greg k-h
On Wed, 05 Aug 2020 18:05:19 +0200, Sebastian Reichel wrote:
> Add basic support for an optional reset gpio.
>
> Reviewed-by: Enric Balletbo i Serra
> Signed-off-by: Sebastian Reichel
> ---
> .../input/touchscreen/eeti,exc3000.yaml | 2 ++
> drivers/input/touchscreen/exc3000.c
Dan,
I just fixed the Author tag in this patch to match your email address
but seems like the author email address gets mangled when sent through
some mailing lists. Any ideas how to avoid this.
On Thu, Aug 6, 2020 at 1:45 AM Stephen Rothwell wrote:
>
> Hi all,
>
> Commit
>
> 2676d210d2f4 ("ci
On Thu, Aug 06, 2020 at 07:56:20PM +0800, Jiaxun Yang wrote:
> Our current problem is Loongson's writecombine implementation seems buggy.
> This is our platform issue rather than target hardware issue.
ok, so simply clear cpu_data[0].writecombine for the fauly parts
> And we don't even know which
All the drivers have long since been upgraded, and all the important
information here is also included in the "Implementing I2C device
drivers" guide.
Signed-off-by: Stephen Kitt
---
Documentation/i2c/index.rst | 1 -
Documentation/i2c/upgrading-clients.rst | 285 --
* Kristen Carlson Accardi wrote:
> Function Granular Kernel Address Space Layout Randomization (fgkaslr)
> -
>
> This patch set is an implementation of finer grained kernel address space
> randomization. It rearranges your ker
The EC reports a variety of error codes. Most of those, with the exception
of EC_RES_INVALID_VERSION, are converted to -EPROTO. As result, the actual
error code gets lost. In cros_ec_cmd_xfer_status(), convert all EC errors
to Linux error codes to report a more meaningful error to the caller to aid
06.08.2020 18:59, Sowjanya Komatineni пишет:
..
> We cant use active status check for specific pads under calibration.
> This is common bit for all pads.
I'm not sure why this is a problem.
On 8/5/20 11:21 PM, Stephen Rothwell wrote:
> Hi all,
>
on x86_64:
when CONFIG_MMU_NOTIFIER is not set/enabled:
../mm/migrate.c: In function 'migrate_vma_collect':
../mm/migrate.c:2481:7: error: 'struct mmu_notifier_range' has no member named
'migrate_pgmap_owner'
range.migrate_pgmap_owner =
Hi,
On Thu 06 Aug 20, 12:13, Ezequiel Garcia wrote:
> Currently, the SLICE_BASED and FRAME_BASED modes documentation
> is misleading and not matching the intended use-cases.
>
> Drop non-required fields SLICE_PARAMS 'start_byte_offset' and
> DECODE_PARAMS 'num_slices' and clarify the decoding mod
Grant
On 8/6/20 1:21 AM, Grant Feng wrote:
generate a 5ms low pulse on sdb pin when startup, then the chip
becomes more stable in the complex EM environment.
Signed-off-by: Grant Feng
---
drivers/leds/leds-is31fl319x.c | 12
1 file changed, 12 insertions(+)
diff --git a/driver
-ENOTSUPP is not a SUSV4 error code and should not be used. Use
-ENOPROTOOPT instead to report EC_RES_INVALID_VERSION responses
from the EC. This matches match the NFS response for unsupported
protocol versions.
Cc: Gwendal Grignou
Cc: Yu-Hsuan Hsu
Cc: Prashant Malani
Cc: Brian Norris
Acked-by
On Mon, Aug 03, 2020 at 08:34:50PM +0200, p...@cmp.felk.cvut.cz wrote:
> From: Pavel Pisa
>
> The device-tree bindings for open-source CAN FD IP core
> which design started at Department of Measurement
> at Faculty of Electrical Engineering
> of Czech Technical University in Prague.
> The IP core
A follow-up patch will extend the number of errors reported by
cros_ec_cmd_xfer_status(). Specifically, the function will return
-EOPNOTSUPP if a command is not supported by the EC. Prepare for it.
Cc: Gwendal Grignou
Cc: Yu-Hsuan Hsu
Cc: Prashant Malani
Cc: Brian Norris
Acked-by: Jonathan Cam
With enhanced error reporting from cros_ec_cmd_xfer_status() in place,
we can fully use it and no longer rely on EC error codes.
Signed-off-by: Guenter Roeck
---
drivers/pwm/pwm-cros-ec.c | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff --git a/drivers/pwm/
On 7/27/20 10:08 AM, Tyler Hicks wrote:
The ima_keyrings buffer was used as a work buffer for strsep()-based
parsing of the "keyrings=" option of an IMA policy rule. This parsing
was re-performed each time an asymmetric key was added to a kernel
keyring for each loaded policy rule that containe
On Thu, Aug 06, 2020 at 08:29:22AM -0400, Michael S. Tsirkin wrote:
> On Thu, Aug 06, 2020 at 03:03:55PM +0300, Eli Cohen wrote:
> > On Wed, Aug 05, 2020 at 08:51:56AM -0400, Michael S. Tsirkin wrote:
> > > On Wed, Jun 17, 2020 at 11:29:44AM +0800, Jason Wang wrote:
> > > > This patch introduce a c
On 8/6/20 3:48 PM, Matthew Wilcox wrote:
> On Thu, Aug 06, 2020 at 01:45:11PM +0200, Vlastimil Babka wrote:
>> How about this additional patch now that we have head_mapcoun()? (I wouldn't
>> go for squashing as the goal and scope is too different).
>
> I like it. It bothers me that the compiler d
Since commit c5cd2b47b203 ("platform/chrome: cros_ec_proto: Report command
not supported") we can no longer assume that cros_ec_cmd_xfer_status()
reports -EPROTO for all errors returned by the EC itself. A follow-up
patch will change cros_ec_cmd_xfer_status() to report additional errors
reported by
The EC reports a variety of error codes. Most of those, with the exception
of EC_RES_INVALID_VERSION, are converted to -EPROTO. As result, the actual
error code gets lost. In cros_ec_cmd_xfer_status(), convert all EC errors
to Linux error codes to report a more meaningful error to the caller to aid
While binder transactions with the same binder_proc as sender and recipient
are forbidden, transactions with the same task_struct as sender and
recipient are possible (even though currently there is a weird check in
binder_transaction() that rejects them in the target==0 case).
Therefore, task_stru
From: Yuti Amonkar
Document the bindings used for the Cadence MHDP DPI/DP bridge in
yaml format.
Signed-off-by: Yuti Amonkar
Signed-off-by: Swapnil Jakhade
Reviewed-by: Rob Herring
Reviewed-by: Laurent Pinchart
---
.../bindings/display/bridge/cdns,mhdp.yaml| 139 ++
1 fi
Hi Rob,
On Thu, 6 Aug 2020 at 23:15, Rob Herring wrote:
> Why are you sending another version? You ignored the errors and my
> questions on the RFC.
Sorry I didn't think I got any responses RFC but after searching it looks
like the email from your bot and your question about the two custom
prop
* Qi Zheng wrote:
> 1. The group_has_capacity() function is only called in
>group_classify().
> 2. Before calling the group_has_capacity() function,
>group_is_overloaded() will first judge the following
>formula, if it holds, the group_classify() will directly
>return the group_
06.08.2020 10:30, Rajesh Gumasta пишет:
> +static struct dma_async_tx_descriptor *tegra_dma_prep_dma_memset(
> + struct dma_chan *dc, dma_addr_t dest, int value, size_t len,
> + unsigned long flags)
> +{
This looks and reads okay, although the following style of code's
formatting is a bit
Hi Prabhakar,
On Mon, Aug 03, 2020 at 12:39:11PM +0100, Lad Prabhakar wrote:
> Document endpoint properties required for parallel interface
>
> Signed-off-by: Lad Prabhakar
> ---
> .../devicetree/bindings/media/i2c/ov772x.txt | 16
> 1 file changed, 16 insertions(+)
>
> diff
Since commit c5cd2b47b203 ("platform/chrome: cros_ec_proto: Report command
not supported") we can no longer assume that cros_ec_cmd_xfer_status()
reports -EPROTO for all errors returned by the EC itself. A follow-up
patch will change cros_ec_cmd_xfer_status() to report additional errors
reported by
Headphone detection is triggered by GPIO, then driver can
switch between speaker and headphone.
Signed-off-by: Shengjiu Wang
---
arch/arm/boot/dts/imx6sl-evk.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sl-evk.dts b/arch/arm/boot/dts/imx6sl-evk.dts
index bc86cf
On Wed, 05 Aug 2020 18:05:17 +0200, Sebastian Reichel wrote:
> Convert the EETI EXC3000 binding to DT schema format using json-schema
>
> Signed-off-by: Sebastian Reichel
> ---
> .../input/touchscreen/eeti,exc3000.yaml | 53 +++
> .../bindings/input/touchscreen/exc3000.txt
Headphone detection is triggered by GPIO, then driver can
switch between speaker and headphone.
Signed-off-by: Shengjiu Wang
---
arch/arm/boot/dts/imx6sx-sdb.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sdb.dtsi
b/arch/arm/boot/dts/imx6sx-sdb.dts
On Mon, Aug 03, 2020 at 12:01:21PM +0800, Cheng-Yi Chiang wrote:
> Add devicetree bindings documentation file for sc7180 sound card.
>
> Signed-off-by: Cheng-Yi Chiang
> ---
> .../bindings/sound/qcom,sc7180.yaml | 113 ++
> 1 file changed, 113 insertions(+)
> create mo
On Tue, 04 Aug 2020 23:01:48 +0800, Anson Huang wrote:
> Convert the vf610 gpio binding to DT schema format using json-schema.
>
> Signed-off-by: Anson Huang
> ---
> .../devicetree/bindings/gpio/gpio-vf610.txt| 63 -
> .../devicetree/bindings/gpio/gpio-vf610.yaml |
06.08.2020 10:30, Rajesh Gumasta пишет:
> +static int tegra_dma_program_sid(struct tegra_dma_channel *tdc,
> + int chan, int stream_id)
> +{
> + unsigned int reg_val = tdc_read(tdc, TEGRA_GPCDMA_CHAN_MCSEQ);
> +
> + reg_val &= ~(TEGRA_GPCDMA_MCSEQ_STREAM_ID_MAS
On Thu, Aug 06, 2020 at 01:55:47PM +0200, Patrick Riphagen wrote:
> From: Patrick Riphagen
>
> The device added has an FTDI chip inside.
> The device is used to connect Xsens USB Motion Trackers.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Patrick Riphagen
> ---
Thanks for the update. I've
On Thursday, 2020-07-16 at 16:52:48 +03, Jarkko Sakkinen wrote:
> Add __sgx_alloc_epc_page(), which iterates through EPC sections and borrows
> a page structure that is not used by anyone else. When a page is no longer
> needed it must be released with sgx_free_epc_page(). This function
> implicitl
On Wed, 05 Aug 2020 15:11:59 +0200, Ansuel Smith wrote:
> Document dedicated Krait CPU Cache Scaling driver.
>
> Signed-off-by: Ansuel Smith
> ---
> .../bindings/cpufreq/krait-cache-scale.yaml | 89 +++
> 1 file changed, 89 insertions(+)
> create mode 100644
> Documentation/d
On Thu, Aug 06, 2020 at 01:39:09PM +0200, Vitaly Kuznetsov wrote:
> "Michael S. Tsirkin" writes:
>
> > About the feature bit, I am not sure why it's really needed. A single
> > mmio access is cheaper than two io accesses anyway, right? So it makes
> > sense for a kvm guest whether host has this f
In the .set_rate callback for some PLLs there is a loop polling state
of the PLL lock bit and it may become an endless loop when something
goes wrong with the PLL. For some PLLs there is already (duplicated)
code for polling with a timeout. This patch refactors that code a bit
and moves it to a com
From: "Steven Rostedt (VMware)"
As trace_array_printk() used with not global instances will not add noise to
the main buffer, they are OK to have in the kernel (unlike trace_printk()).
This require the subsystem to create their own tracing instance, and the
trace_array_printk() only writes into t
On Tue, 04 Aug 2020 13:37:28 +0530, Rohit kumar wrote:
> Add dt-bindings to support "qcom,lpass-cpu-sc7180" node.
>
> Signed-off-by: Rohit kumar
> ---
> .../devicetree/bindings/sound/qcom,lpass-cpu.txt | 55
> +-
> 1 file changed, 53 insertions(+), 2 deletions(-)
>
Revie
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: fffe3ae0ee84e25d2befe2ae59bc32aa2b6bc77b
commit: f9c00e2cf258d215a1ed2a7b2ae5b91ac2f29582 ionic: clean tx queue of
unfinished requests
date: 4 months ago
:: branch date: 5 hours ago
:: commit date:
Hi Sylwester,
2020年8月6日(木) 18:06 Sylwester Nawrocki :
>
> In the .set_rate callback for some PLLs there is a loop polling state
> of the PLL lock bit and it may become an endless loop when something
> goes wrong with the PLL. For some PLLs there is already (duplicated)
> code for polling with a ti
From: Thierry Reding
Iterate over child devices in reverse when unpopulating a platform
device to make this step symmetrical with the population step. This
fixes an issue in the Tegra DRM driver where upon module unload the
DPAUX controller tries to unregister an I2C controller but will end
up wa
06.08.2020 18:59, Sowjanya Komatineni пишет:
...
>>> Confirmed from HW designer, calibration FSM to finish takes worst case
>>> 72uS so by the time it gets to sensor stream it will be done its
>>> sequence and will be waiting for DONE bit.
>>>
>>> So disabling MIPI CAL clock on sensor stream fails
Hi Jacopo,
Thank you for the review.
On Thu, Aug 6, 2020 at 5:27 PM Jacopo Mondi wrote:
>
> Hi Prabhakar,
>
> On Mon, Aug 03, 2020 at 03:31:45PM +0100, Lad Prabhakar wrote:
> > During testing this sensor on iW-RainboW-G21D-Qseven platform in 8-bit DVP
> > mode with rcar-vin bridge noticed the ca
On Thu, Aug 6, 2020 at 10:51 AM peter enderborg
wrote:
>
> On 8/6/20 3:49 PM, Stephen Smalley wrote:
> > On Thu, Aug 6, 2020 at 9:45 AM Stephen Smalley
> > wrote:
> >> On 8/6/20 8:32 AM, Stephen Smalley wrote:
> >>
> >>> On 8/6/20 8:24 AM, peter enderborg wrote:
> >>>
> On 8/6/20 2:11 PM, St
Hi,
On Thu 06 Aug 20, 12:13, Ezequiel Garcia wrote:
> The SLICE_PARAMS control is intended for slice-based
> devices. In this mode, the OUTPUT buffer contains
> a single slice, and so the buffer's plane payload size
> can be used to query the slice size.
If we later extend the API for supporting
On Thu, Aug 06, 2020 at 05:13:05PM +0200, Vlastimil Babka wrote:
> On 8/6/20 3:48 PM, Matthew Wilcox wrote:
> > On Thu, Aug 06, 2020 at 01:45:11PM +0200, Vlastimil Babka wrote:
> >> How about this additional patch now that we have head_mapcoun()? (I
> >> wouldn't
> >> go for squashing as the goal
From: Jiang Biao
If a se is on_rq when reweighting entity, all we need should be
updating the load of cfs_rq, other dequeue/enqueue work could be
redundant, such as,
* nr_running--/nr_running++
Even though the following dequeue/enqueue path would never be reached
* account_numa_dequeue/account_n
syzbot suspects this issue was fixed by commit:
commit 4b836a1426cb0f1ef2a6e211d7e553221594f8fc
Author: Jann Horn
Date: Mon Jul 27 12:04:24 2020 +
binder: Prevent context manager from incrementing ref 0
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10c84dec90
start
On Thu, Aug 6, 2020 at 9:54 AM Jann Horn wrote:
>
> While binder transactions with the same binder_proc as sender and recipient
> are forbidden, transactions with the same task_struct as sender and
> recipient are possible (even though currently there is a weird check in
> binder_transaction() tha
On Wed, Apr 22, 2020 at 08:32:43PM +, John Stultz wrote:
> This patch addresses a regression in 5.7-rc1+
>
> In commit c8c43cee29f6 ("driver core: Fix
> driver_deferred_probe_check_state() logic"), we both cleaned up
> the logic and also set the default driver_deferred_probe_timeout
> value to
On Thu, Aug 06, 2020 at 09:47:23AM +0200, Marco Elver wrote:
> Testing my hypothesis that raw then nested non-raw
> local_irq_save/restore() breaks IRQ state tracking -- see the reproducer
> below. This is at least 1 case I can think of that we're bound to hit.
Aaargh!
> diff --git a/init/main.c
201 - 300 of 1099 matches
Mail list logo
