From: Kan Liang
Extend sample-parsing test cases to support new sample type
PERF_SAMPLE_DATA_PAGE_SIZE.
Acked-by: Namhyung Kim
Signed-off-by: Kan Liang
---
tools/perf/tests/sample-parsing.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
From: Kan Liang
To get the changes in:
commit 8d97e71811aa ("perf/core: Add PERF_SAMPLE_DATA_PAGE_SIZE")
commit 995f088efebe ("perf/core: Add support for PERF_SAMPLE_CODE_PAGE_SIZE")
This silences this perf tools build warning:
Warning: Kernel ABI header at
On Mon, Nov 30, 2020 at 10:54 PM Joe Perches wrote:
>
> On Mon, 2020-11-30 at 22:33 +0530, Dwaipayan Ray wrote:
> > On Mon, Nov 30, 2020 at 10:13 PM Joe Perches wrote:
> > >
> > > On Mon, 2020-11-30 at 20:15 +0530, Dwaipayan Ray wrote:
> > > > checkpatch reports a false TYPO_SPELLING warning for
From: Kan Liang
Add option --data-page-size in "perf mem" to record/report data page
size.
Here are some examples.
perf mem --phys-data --data-page-size report -D
# PID, TID, IP, ADDR, PHYS ADDR, DATA PAGE SIZE, LOCAL WEIGHT, DSRC,
# SYMBOL
20134 20134 0xb5bd2fd0
From: Kan Liang
Now, "--phys-data" is the only option which impacts the output format.
A simple "if else" is enough to handle the option. But there will be
more options added, e.g. "--data-page-size", which also impact the
output format. The code will become too complex to be maintained.
Divide
From: Kan Liang
Now, "--phys-data" is the only option which impacts the sort order.
A simple "if else" is enough to handle the option. But there will be
more options added, e.g. "--data-page-size", which also impact the sort
order. The code will become too complex to be maintained.
Divide the
From: Kan Liang
Add a new sort option "data_page_size" for --mem-mode sort. With this
option applied, perf can sort and report by sample's data page size.
Here is an example.
perf report --stdio --mem-mode
--sort=comm,symbol,phys_daddr,data_page_size
# To display the perf.data header info,
Randy Dunlap wrote:
> On 11/27/20 10:43 AM, Randy Dunlap wrote:
>
> > on parisc, _SA_SIGGFAULT is undefined and causing build errors.
> >
> > commit 23acdc76f1798b090bb9dcc90671cd29d929834e
> > Author: Peter Collingbourne
> > Date: Thu Nov 12 18:53:34 2020 -0800
> >
> > signal: clear
On 27/11/2020 15:39, Alexandre Truong wrote:
Previously, this command returns no help message on aarch64:
-> ./perf record --user-regs=?
available registers:
Usage: perf record [] []
or: perf record [] -- []
With this change, the registers are listed.
-> ./perf record
On Mon, Nov 30, 2020 at 01:31:14PM +, Daniel Scally wrote:
> The software_node_get_next_child() function currently does not hold
> references to the child software_node that it finds or put the ref that
> is held against the old child - fix that.
Fixes tag and make it first in the series?
In
From: Kan Liang
Support new sample type PERF_SAMPLE_DATA_PAGE_SIZE for page size.
Add new option --data-page-size to record sample data page size.
Acked-by: Namhyung Kim
Signed-off-by: Kan Liang
---
tools/perf/Documentation/perf-record.txt | 3 +++
tools/perf/builtin-record.c
From: Kan Liang
Changes since V1:
- Fix the compile warning with GCC 10
- Add Acked-by from Namhyung Kim
Current perf can report both virtual addresses and physical addresses,
but not the page size. Without the page size information of the utilized
page, users cannot decide whether to
[+cc Lukas, pciehp power control question]
On Mon, Nov 23, 2020 at 02:45:13PM +0800, Jianjun Wang wrote:
> On Thu, 2020-11-19 at 14:28 -0600, Bjorn Helgaas wrote:
> > "Add new generation" really contains no information. And "mediatek"
> > is already used for the pcie-mediatek.c driver, so we
On 11/27/20 9:49 AM, Brian King wrote:
> On 11/25/20 7:48 PM, Tyrel Datwyler wrote:
>> --- a/drivers/scsi/ibmvscsi/ibmvfc.c
>> +++ b/drivers/scsi/ibmvscsi/ibmvfc.c
>
>> @@ -4462,6 +4464,118 @@ static void ibmvfc_discover_targets(struct
>> ibmvfc_host *vhost)
>>
On Mon, Nov 30, 2020 at 07:29:00PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 30, 2020 at 01:31:13PM +, Daniel Scally wrote:
> > This function is used to find fwnode endpoints against a device. In
> > some instances those endpoints are software nodes which are children of
> >
On Mon, Nov 30, 2020 at 01:31:13PM +, Daniel Scally wrote:
> This function is used to find fwnode endpoints against a device. In
> some instances those endpoints are software nodes which are children of
> fwnode->secondary. Add support to fwnode_graph_get_endpoint_by_id() to
> find those
On 11/27/20 9:47 AM, Brian King wrote:
> On 11/25/20 7:48 PM, Tyrel Datwyler wrote:
>> The logic for iterating over the Sub-CRQ responses is similiar to that
>> of the primary CRQ. Add the necessary handlers for processing those
>> responses.
>>
>> Signed-off-by: Tyrel Datwyler
>> ---
>>
On Sun, Nov 29, 2020 at 11:55 PM Stanimir Varbanov
wrote:
>
> Hi Fritz,
>
> On 11/29/20 9:17 PM, Fritz Koenig wrote:
> > Since this patchset adds support for V4L2_ENC_CMD_STOP and
> > VENUS_ENC_STATE_ENCODING it should also add support for
> > VIDIOC_TRY_ENCODER_CMD so that those commands are
Hi Linus,
On Fri, Nov 27, 2020 at 3:02 PM Linus Torvalds
wrote:
>
> On Fri, Nov 27, 2020 at 12:51 PM Arnd Bergmann wrote:
> >
> > - Some DT patches for the Rockchip RK3399 platform,
> >in particular fixing the MMC device ordering that
> >recently became nondeterministic with async
On 11/27/20 9:46 AM, Brian King wrote:
> On 11/25/20 7:48 PM, Tyrel Datwyler wrote:
>> Allocate a set of Sub-CRQs in advance. During channel setup the client
>> and VIOS negotiate the number of queues the VIOS supports and the number
>> that the client desires to request. Its possible that the
On 11/30/20 11:00 AM, Bjorn Andersson wrote:
> The "pins" property takes an array of pin _names_, not pin numbers. Fix
> this.
>
> Fixes: 44acee207844 ("arm64: dts: qcom: Add Lenovo Yoga C630")
> Signed-off-by: Bjorn Andersson
> ---
> arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 8
On 11/30/20 10:59 AM, Bjorn Andersson wrote:
> The numbering of the i2c busses differs from ACPI and a number of typos
> was made in the original patch. Further more the irq flags for the
> various resources was not correct and i2c3 only has one of the two
> client devices active in any one
On Mon, Nov 30, 2020 at 03:28:51PM +0800, chenle...@gmail.com wrote:
> From: Lei Chen
>
> iomap_add_to_ioend append page on wpc->ioend->io_bio. If io_bio is full,
> iomap_chain_bio will allocate a new bio. So when bio_add_page is called,
> pages is guaranteed to be appended into
On Mon, 2020-11-30 at 22:33 +0530, Dwaipayan Ray wrote:
> On Mon, Nov 30, 2020 at 10:13 PM Joe Perches wrote:
> >
> > On Mon, 2020-11-30 at 20:15 +0530, Dwaipayan Ray wrote:
> > > checkpatch reports a false TYPO_SPELLING warning for some words
> > > containing an apostrophe.
> > >
> > > A false
On Mon, Nov 30, 2020 at 12:20:04PM -0500, Alan Stern wrote:
> > https://lore.kernel.org/linux-usb/fde7e11f-5dfc-8348-c134-a21cb1116...@redhat.com/T/#t
>
> It's hard to go wrong with reverting, so it's okay with me.
>
> Still, Hans, have you checked out the difference between the
>
On Thu, 26 Nov 2020 14:06:28 -0700, Mathieu Poirier wrote:
> This patch adds a binding to guide the remoteproc core on how to deal with
> remote processors in two cases:
>
> 1) When an application holding a reference to a remote processor character
>device interface crashes.
>
> 2) when the
On Mon, Nov 30, 2020, at 18:56, Thomas Gleixner wrote:
> Laurentiu,
>
> On Fri, Nov 27 2020 at 10:03, Laurențiu Nicola wrote:
> > On Fri, Nov 27, 2020, at 02:12, Thomas Gleixner wrote:
> >> On Thu, Nov 26 2020 at 09:47, Laurențiu Nicola wrote:
> >> > These messages are described as warnings in
On 11/28/20 5:40 PM, Alexei Starovoitov wrote:
On Fri, Nov 27, 2020 at 09:53:05PM -0800, Yonghong Song wrote:
On 11/27/20 9:57 AM, Brendan Jackman wrote:
Status of the patches
=
Thanks for the reviews! Differences from v1->v2 [1]:
* Fixed mistakes in the netronome
On Thu, 26 Nov 2020 19:45:57 +0100, AngeloGioacchino Del Regno wrote:
> Convert the qcom-cpufreq-hw documentation to YAML binding as
> qcom,cpufreq-hw.yaml.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> .../bindings/cpufreq/cpufreq-qcom-hw.txt | 173 +---
>
On Thu, 26 Nov 2020 19:45:56 +0100, AngeloGioacchino Del Regno wrote:
> Add the bindings for the CPR3 driver to the documentation.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> .../bindings/soc/qcom/qcom,cpr3.yaml | 226 ++
> 1 file changed, 226 insertions(+)
On 11/27/20 9:45 AM, Brian King wrote:
> On 11/25/20 7:48 PM, Tyrel Datwyler wrote:
>> diff --git a/drivers/scsi/ibmvscsi/ibmvfc.h b/drivers/scsi/ibmvscsi/ibmvfc.h
>> index 9d58cfd774d3..8225bdbb127e 100644
>> --- a/drivers/scsi/ibmvscsi/ibmvfc.h
>> +++ b/drivers/scsi/ibmvscsi/ibmvfc.h
>> @@ -41,6
On Mon, Nov 30, 2020 at 01:31:12PM +, Daniel Scally wrote:
> Some types of fwnode_handle do not implement the device_is_available()
> check, such as those created by software_nodes. There isn't really a
> meaningful way to check for the availability of a device that doesn't
> actually exist,
On Mon, 30 Nov 2020 14:44:42 +0100
Borislav Petkov wrote:
> On Sun, Nov 29, 2020 at 05:50:05PM +0900, Masami Hiramatsu wrote:
> > Good point. I think we can return, e.g. -EFAULT if we failed in
> > get_next(). Then, we can read out next page, for example.
>
> Why -EFAULT?
Because it overruns
Hello,
On Mon, Nov 30, 2020 at 04:29:04PM +, Kieran Bingham wrote:
> On 30/11/2020 13:31, Daniel Scally wrote:
> > On platforms where ACPI is designed for use with Windows, resources
> > that are intended to be consumed by sensor devices are sometimes in
> > the _CRS of a dummy INT3472 device
On 11/28/20 5:36 PM, Alexei Starovoitov wrote:
On Fri, Nov 27, 2020 at 09:39:10PM -0800, Yonghong Song wrote:
On 11/27/20 9:57 AM, Brendan Jackman wrote:
This adds instructions for
atomic[64]_[fetch_]and
atomic[64]_[fetch_]or
atomic[64]_[fetch_]xor
All these operations are isomorphic
> +static int am65_cpsw_port_stp_state_set(struct am65_cpsw_port *port,
> + struct switchdev_trans *trans, u8 state)
> +{
> + struct am65_cpsw_common *cpsw = port->common;
> + u8 cpsw_state;
> + int ret = 0;
> +
> + if
On 11/30/20 4:08 PM, Ulf Hansson wrote:
On Sun, 29 Nov 2020 at 19:20, Martin DEVERA wrote:
Hello,
on STM32MP1 with almost vanilla 5.7.7 in single CPU mode. Pair of
modprobe armmmci ; rmmod armmmci
causes rmmod and kworker to hang. I should note that no MMC is detected
on the board (SDIO
Hi Daniel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on driver-core/driver-core-testing pm/linux-next
v5.10-rc6 next-20201130]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On Mon, Nov 30, 2020 at 02:36:38PM +0100, Hans de Goede wrote:
> Hi,
>
> On 11/30/20 2:30 PM, Greg KH wrote:
> > On Mon, Nov 30, 2020 at 02:23:48PM +0100, Hans de Goede wrote:
> >> Hi,
> >>
> >> On 11/30/20 1:58 PM, Tom Yan wrote:
> >>> It's merely a moving of comment moving for/and a
[Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value] On
30/11/2020 (Mon 11:20) Steven Rostedt wrote:
> On Thu, 26 Nov 2020 01:30:28 -0500
> Paul Gortmaker wrote:
>
> > +++ b/Documentation/admin-guide/clearing-warn-once.rst
> > @@ -7,3 +7,12 @@ echo 1 >
On Mon, Nov 30, 2020 at 11:19:21AM +0100, Daniel Wagner wrote:
> It's guaranteed that no request is in flight when a hctx is going
> offline. This warning is only triggered when the wq's CPU is hot
> plugged and the blk-mq is not synced up yet.
>
> As this state is temporary and the request is
On 11/28/20 5:34 PM, Alexei Starovoitov wrote:
On Fri, Nov 27, 2020 at 09:35:07PM -0800, Yonghong Song wrote:
On 11/27/20 9:57 AM, Brendan Jackman wrote:
Including only interpreter and x86 JIT support.
x86 doesn't provide an atomic exchange-and-subtract instruction that
could be used for
On Mon, 30 Nov 2020 at 16:51, Nicolas Pitre wrote:
>
> On Mon, 30 Nov 2020, Ard Biesheuvel wrote:
>
> > (+ Nico)
> >
> > On Mon, 30 Nov 2020 at 11:11, Ard Biesheuvel wrote:
> > >
> > > On Mon, 23 Nov 2020 at 08:39, Antony Yu wrote:
> > > >
> > > > __do_div64 clobbers the input register r0 in
On Mon, Nov 30, 2020 at 6:37 PM Bartosz Golaszewski
wrote:
>
> On Thu, Nov 19, 2020 at 4:04 PM Andy Shevchenko
> wrote:
> >
> > On Thu, Nov 19, 2020 at 4:17 PM Alexandru Ardelean
> > wrote:
> > >
> > > There is no matching spi_get_drvdata() call in the driver, so there is no
> > > need to do
On 11/30/20 4:48 PM, David Woodhouse wrote:
> On Mon, 2020-11-30 at 15:08 +, Joao Martins wrote:
>> On 11/30/20 12:55 PM, David Woodhouse wrote:
>>> On Mon, 2020-11-30 at 12:17 +, Joao Martins wrote:
On 11/30/20 9:41 AM, David Woodhouse wrote:
> On Wed, 2019-02-20 at 20:15 +,
On Mon, Nov 30, 2020 at 6:51 PM Bartosz Golaszewski
wrote:
>
> On Thu, Nov 19, 2020 at 7:46 PM Andy Shevchenko
> wrote:
> >
> > On Thu, Nov 19, 2020 at 7:08 PM Gustavo A. R. Silva
> > wrote:
> > >
> > > In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> > > by explicitly
On Mon, Nov 30, 2020 at 05:07:09PM +, Vincenzo Frascino wrote:
> UL in the definition of SYS_TFSR_EL1_TF1 was misspelled causing
> compilation issues when trying to implement in kernel MTE async
> mode.
>
> Fix the macro correcting the typo.
>
> Note: MTE async mode will be introduced with a
On Thu, 2020-11-26 at 11:34 +0100, Roberto Sassu wrote:
> Commit a408e4a86b36b ("ima: open a new file instance if no read
> permissions") already introduced a second open to measure a file when the
> original file descriptor does not allow it. However, it didn't remove the
> existing method of
Hi Daniel,
Thank you for the patch.
On Mon, Nov 30, 2020 at 01:31:26PM +, Daniel Scally wrote:
> Some places in the kernel allow users to map resources to a device
> using device name (for example, gpiod_lookup_table). Currently
> this involves waiting for the i2c_client to have been
Hi Daniel,
Thank you for the patch.
On Mon, Nov 30, 2020 at 01:31:27PM +, Daniel Scally wrote:
> From: Dan Scally
>
> To make sure the new i2c_acpi_dev_name() always reflects the name of i2c
> devices sourced from ACPI, use it in i2c_set_dev_name().
>
> Signed-off-by: Dan Scally
I'd
Hi Daniel,
Thank you for the patch.
On Mon, Nov 30, 2020 at 01:31:24PM +, Daniel Scally wrote:
> Currently on platforms designed for Windows, connections between CIO2 and
> sensors are not properly defined in DSDT. This patch extends the ipu3-cio2
> driver to compensate by building
Hi Derek,
Em Mon, 30 Nov 2020 08:04:31 -0800
VDRU VDRU escreveu:
> I have hardware that uses this driver and can conduct a test if it
> will help resolve any confusion/assumption. I'd also like to suggest
> that making changes to drivers with no means of testing those changes
> is bad. This has
>>> {
>>> - int cpu, hk_flags;
>>> + static DEFINE_SPINLOCK(spread_lock);
>>> + static bool used[MAX_NUMNODES];
>>
>> I thought I mentioned this last time. How large is this array? How
>> large would it be if it were a nodemask_t? Would this be less code if
>
> Apologies that I forgot
UL in the definition of SYS_TFSR_EL1_TF1 was misspelled causing
compilation issues when trying to implement in kernel MTE async
mode.
Fix the macro correcting the typo.
Note: MTE async mode will be introduced with a future series.
Fixes: c058b1c4a5ea ("arm64: mte: system register definitions")
On 11/27/20 13:32, Qais Yousef wrote:
> On 11/24/20 15:50, Will Deacon wrote:
> > If the scheduler cannot find an allowed CPU for a task,
> > cpuset_cpus_allowed_fallback() will widen the affinity to cpu_possible_mask
> > if cgroup v1 is in use.
> >
> > In preparation for allowing architectures
Hi,
On Fri, Nov 27, 2020 at 2:56 PM Linus Torvalds
wrote:
>
> On Fri, Nov 27, 2020 at 12:51 PM Arnd Bergmann wrote:
> >
> > - Some DT patches for the Rockchip RK3399 platform,
> >in particular fixing the MMC device ordering that
> >recently became nondeterministic with async probe.
>
>
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on driver-core/driver-core-testing pm/linux-next
v5.10-rc6 next-20201130]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On Mon, Nov 30, 2020 at 10:13 PM Joe Perches wrote:
>
> On Mon, 2020-11-30 at 20:15 +0530, Dwaipayan Ray wrote:
> > checkpatch reports a false TYPO_SPELLING warning for some words
> > containing an apostrophe.
> >
> > A false positive is "doesn't". Occurrence of the word causes
> > checkpatch to
Hi Peter,
every patch needs a proper commit message.
> Signed-off-by: Peter Tsao
> ---
> drivers/bluetooth/btmtk_buffer_mode.c | 263 +
> drivers/bluetooth/btmtk_main.c| 5517 +
> drivers/bluetooth/include/btmtk_buffer_mode.h | 78 +
>
On Fri, Nov 27, 2020 at 06:19:44PM +0530, Akhil P Oommen wrote:
> So far a530v2 gpu has support for detecting its supported opps
> based on a fuse value called speed-bin. This patch makes this
> support generic across gpu families. This is in preparation to
> extend speed-bin support to a6x
On Thu, 26 Nov 2020 19:45:53 +0100, AngeloGioacchino Del Regno wrote:
> Convert the qcom,cpr.txt document to YAML schema and place it in the
> appropriate directory, since commit a7305e684fc moves this driver
> from power/avs to soc/qcom, but forgets to move the documentation.
>
> Signed-off-by:
On 30/11/20 16:58, Maxim Levitsky wrote:
This is mostly useful for userspace that doesn't disable the quirk, right?
Isn't this the opposite? If I understand the original proposal correctly,
the reason that we include the TSC_ADJUST in the new ioctl, is that
we would like to disable the special
The "pins" property takes an array of pin _names_, not pin numbers. Fix
this.
Fixes: 44acee207844 ("arm64: dts: qcom: Add Lenovo Yoga C630")
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 8
1 file changed, 4 insertions(+), 4 deletions(-)
On 30/11/20 17:54, Andy Lutomirski wrote:
I*do think* however that we should redefine KVM_CLOCK_TSC_STABLE
in the documentation to state that it only guarantees invariance if the guest
doesn't mess with its own TSC.
Also I think we should consider enabling the X86_FEATURE_TSC_RELIABLE
in the
Add ability to probe device and validate configuration, then apply a regmap
configuration for a single or dual buck device accordingly.
Signed-off-by: Adam Ward
---
drivers/regulator/Kconfig| 14 +-
drivers/regulator/da9121-regulator.c | 244 ---
Adds get/set for mode, and mapping from REGULATOR_MODE_* to select
PFM/PWM/Auto operation.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 74
1 file changed, 74 insertions(+)
diff --git a/drivers/regulator/da9121-regulator.c
Descriptors for bucks in all variants, ready for of_regulator_match
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 110 +++
1 file changed, 110 insertions(+)
diff --git a/drivers/regulator/da9121-regulator.c
This commit adds support for getting/setting current for all supported
variants. Limits are adjusted per variant to match HW implementation.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 113 +++
1 file changed, 113 insertions(+)
diff --git
Adds interrupt handler for variants, and notifications for events; over
temperature/voltage/current. Because the IRQs are triggered by persisting
status, they must be masked and the status polled until clear, before the
IRQ can be enabled again.
Signed-off-by: Adam Ward
---
Add function which iterates the regulator descriptors for the confirmed
variant ID and registers each buck.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 44 +---
1 file changed, 31 insertions(+), 13 deletions(-)
diff --git
UL in the definition of SYS_TFSR_EL1_TF1 was misspelled causing
compilation issues when trying to implement in kernel MTE async
mode.
Fix the macro correcting the typo.
Note: MTE async mode will be introduced with a future series.
Fixes: c058b1c4a5ea ("arm64: mte: system register definitions")
Add devicetree configuration and device variant parameters. Use the latter
to enable the check and use of parameters specific to dual buck variants.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 119 +++
include/linux/regulator/da9121.h
On Wed, 25 Nov 2020 18:48:25 +0100, Ansuel Smith wrote:
> Document the use of bindings used for msm8960 tsens based devices.
> msm8960 use the same gcc regs and is set as a child of the qcom gcc.
>
> Signed-off-by: Ansuel Smith
> ---
> .../bindings/thermal/qcom-tsens.yaml | 103
Add basic support for configuration to reference variants of this device,
and track the selected variant within the driver.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 46 +---
1 file changed, 43 insertions(+), 3 deletions(-)
diff --git
Add header file for Dialog Semiconductor DA9121 regulator and related
devices, mostly autogenerated from the chip design databases, and update
driver to replace local defines with those from header.
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 15 +-
The numbering of the i2c busses differs from ACPI and a number of typos
was made in the original patch. Further more the irq flags for the
various resources was not correct and i2c3 only has one of the two
client devices active in any one device.
Also label the various devices, for easier
Update bindings for the Dialog Semiconductor DA9121 voltage regulator to
add device variants.
Because several variants have multiple regulators, and to regard potential
to add GPIO support in future, the 'regulators' sub-node is added,
following the precedent set by other multi-regulator devices,
On Fri, 27 Nov 2020 16:29:47 +0100, Rasmus Villemoes wrote:
> Commit 0f0581b24bd0 ("spi: fsl: Convert to use CS GPIO descriptors")
> broke the use of the SPISEL_BOOT signal as a chip select on the
> MPC8309.
>
> pdata->max_chipselect, which becomes master->num_chipselect, must be
> initialized to
Andrew
On 11/19/20 7:49 PM, Andrew Lunn wrote:
+static int dp83td510_config_init(struct phy_device *phydev)
+{
+ struct dp83td510_private *dp83td510 = phydev->priv;
+ int ret = 0;
+
+ if (phy_interface_is_rgmii(phydev)) {
+ if (dp83td510->rgmii_delay) {
+
This series extends the DA9121 driver to add support for related products:
DA9130, 10A, Dual-Phase (Automotive Grade)
DA9122, 5A + 5A
DA9131, 5A + 5A (Automotive Grade)
DA9220, 3A + 3A
DA9132, 3A + 3A (Automotive Grade)
DA9217, 6A, Dual-Phase
It also extends support to cover DT
On Mon 30 Nov 04:34 CST 2020, Stanimir Varbanov wrote:
> Bjorn, could you take this for v5.11.
>
I did apply it a few weeks back, but seems I forgot to reply (and it was
before I asked patchwork-bot to do so for me).
Regards,
Bjorn
> On 11/2/20 2:07 PM, Georgi Djakov wrote:
> > Hi Stan,
> >
Laurentiu,
On Fri, Nov 27 2020 at 10:03, Laurențiu Nicola wrote:
> On Fri, Nov 27, 2020, at 02:12, Thomas Gleixner wrote:
>> On Thu, Nov 26 2020 at 09:47, Laurențiu Nicola wrote:
>> > These messages are described as warnings in the MSI code.
>>
>> Where and what has MSI to do with these
On Mon, 30 Nov 2020 16:53:28 +0530, Jagan Teki wrote:
> Add NXP PF8100/PF8121A/PF8200 regulators bindings.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
for-next
Thanks!
[1/2] regulator: Add pf8x00 regulator bindings
commit:
On Mon, 30 Nov 2020 11:11:15 +0800, Lumi Lee wrote:
> Fix tx/rx stream assign in write.
> Write should use tx instead of rx.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: mediatek: btcvsd fix tx stream assign
commit:
Hi Rahul,
On Tue, Nov 24, 2020 at 03:03:40PM +, Rahul Gopakumar wrote:
> Hi Baoquan,
>
> We applied the new patch to 5.10 rc3 and tested it. We are still
> observing the same page corruption issue which we saw with the
> old patch. This is causing 3 secs delay in boot time.
>
> Attached
On Fri, 27 Nov 2020 13:30:29 +0100, Alexandre Belloni wrote:
> Add device tree binding documentation for Analog Devices ADAU1372.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: adau1372: Add bindings documentation
commit:
On Mon, 30 Nov 2020 21:00:27 +0900 Bongsu jeon wrote:
> From: Bongsu Jeon
>
> Since S3FWRN82 NFC Chip, The UART interface can be used.
> S3FWRN82 supports I2C and UART interface.
>
> Signed-off-by: Bongsu Jeon
All patches in the series should have the same version.
If the patch was not
On Wed, 4 Nov 2020 21:12:08 +0100, Alexandre Belloni wrote:
> Add device tree binding documentation for Analog Devices ADAU1372.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: adau1372: Add bindings documentation
commit:
On Mon, Nov 30, 2020 at 04:15:23PM +0100, Jason A. Donenfeld wrote:
> I am willing to maintain random.c and have intentions to have a
> formally verified RNG. I've mentioned this to Ted before.
>
> But I think Ted's reluctance to not accept the recent patches sent to
> this list is mostly
On Mon, Nov 30, 2020 at 5:36 AM Maxim Levitsky wrote:
>
> Hi!
>
> This is the first version of the work to make TSC migration more accurate,
> as was defined by Paulo at:
> https://www.spinics.net/lists/kvm/msg225525.html
>
> I have a few thoughts about the kvm masterclock synchronization,
>
On Mon, 2020-11-30 at 17:27 +0100, Mike Galbraith wrote:
> On Mon, 2020-11-30 at 17:03 +0100, Sebastian Andrzej Siewior wrote:
> > On 2020-11-30 16:01:11 [+0100], Mike Galbraith wrote:
> > > On Mon, 2020-11-30 at 15:52 +0100, Sebastian Andrzej Siewior wrote:
> > > > How do you test this? I
On Wed 30 Sep 01:42 CDT 2020, Srinivasa Rao Mandadapu wrote:
> These patches are device tree changes to support audio over DP.
> It includes changes of HDMI reg, interrupt and iommu and
> hdmi dai link.
> These patches depends on the lpass I2S patch series
> and DP dts node patch series:
> --
On Fri 18 Sep 09:51 CDT 2020, Srinivasa Rao Mandadapu wrote:
> From: Ajit Pandey
>
> Add dai link for supporting lpass I2S driver, which is used
> for audio capture and playback.
> Add lpass-cpu node with pin controls and i2s primary
> and secondary dai-links
>
> Signed-off-by: Srinivasa Rao
On Mon, Nov 30, 2020 at 10:44:14AM +, Surendrakumar Upadhyay, TejaskumarX
wrote:
> Hi All,
>
> Are we merging this patch in?
Does it fix something? If something is broken without this patch, can
we collect information about exactly what is broken and how it fails?
But I don't object if
On Thu, Nov 19, 2020 at 7:46 PM Andy Shevchenko
wrote:
>
> On Thu, Nov 19, 2020 at 7:08 PM Gustavo A. R. Silva
> wrote:
> >
> > In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> > by explicitly adding a break statement instead of letting the code fall
> > through to the
On Mon, 2020-11-30 at 15:08 +, Joao Martins wrote:
> On 11/30/20 12:55 PM, David Woodhouse wrote:
> > On Mon, 2020-11-30 at 12:17 +, Joao Martins wrote:
> > > On 11/30/20 9:41 AM, David Woodhouse wrote:
> > > > On Wed, 2019-02-20 at 20:15 +, Joao Martins wrote:
> > > One thing I didn't
From: Bartosz Golaszewski
20 characters limit for item name is relatively small. Let's increase it
to 32 to fit '04-committable-children' - a name we'll use in the sample
code for committable items.
Signed-off-by: Bartosz Golaszewski
---
include/linux/configfs.h | 2 +-
1 file changed, 1
From: Bartosz Golaszewski
Add an example of using committable items to configfs samples. Each
config item has two attributes: read-write 'storeme' which works
similarly to other examples in this file and a read-only 'committed'
attribute which changes its value between false and true depending
From: Bartosz Golaszewski
This implements configfs committable items. We mostly follow the
documentation except that we extend config_group_ops with uncommit_item()
callback for reverting the changes made by commit_item().
Each committable group has two sub-directories: pending and live. New
From: Bartosz Golaszewski
For better readability and maintenance: use the BIT() macro for flag
definitions.
Signed-off-by: Bartosz Golaszewski
---
fs/configfs/configfs_internal.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
901 - 1000 of 1677 matches
Mail list logo
