Add a pincontrol driver for BCM6368. BCM6368 allows muxing the first 32
GPIOs onto alternative functions. Not all are documented.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: no changes
v7: no changes
v6: no changes
v5: add changes
Add binding documentation for the GPIO sysctl found in BCM6368 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6368-gpio-sysctl.yaml | 246 ++
1 file changed, 246
Add binding documentation for the pincontrol core found in the BCM63268
family SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
v6: add changes
Add binding documentation for the pincontrol core found in BCM6368 SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
v6: add changes suggested by Rob
Add binding documentation for the GPIO sysctl found in BCM6362 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6362-gpio-sysctl.yaml | 236 ++
1 file changed, 236
Add a pincotrol driver for BCM6362. BCM6362 allows muxing individual
GPIO pins to the LED controller, to be available by the integrated
wifi, or other functions. It also supports overlay groups, of which
only NAND is documented.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Add binding documentation for the pincontrol core found in BCM6362 SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
v6: add changes suggested by Rob
Add a pincotrol driver for BCM6358. BCM6358 allow overlaying different
functions onto the GPIO pins. It does not support configuring individual
pins but only whole groups. These groups may overlap, and still require
the directions to be set correctly in the GPIO register. In addition the
functions
Add binding documentation for the GPIO sysctl found in BCM6358 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6358-gpio-sysctl.yaml | 130 ++
1 file changed, 130
Add binding documentation for the pincontrol core found in BCM6358 SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
v6: add changes suggested by Rob
On 03/17, Qianli Zhao wrote:
>
> From: Qianli Zhao
>
> When init sub-threads running on different CPUs exit at the same time,
> zap_pid_ns_processe()->BUG() may be happened.
and why do you think your patch can't prevent this?
Sorry, I must have missed something. But it seems to me that you are
Add a pincontrol driver for BCM6328. BCM6328 supports muxing 32 pins as
GPIOs, as LEDs for the integrated LED controller, or various other
functions. Its pincontrol mux registers also control other aspects, like
switching the second USB port between host and device mode.
Co-developed-by: Jonas
Add a helper for registering BCM63XX pin controllers.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: revert from fwnode to "of" and look for brcm,bcm63xx-gpio on the parent
v6: add changes
Add binding documentation for the GPIO sysctl found in BCM6328 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6328-gpio-sysctl.yaml | 162 ++
1 file changed, 162
Add binding documentation for the pincontrol core found in BCM6328 SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
v6: add changes suggested by Rob
Convert existing BCM6345 GPIO binding documentation to YAML and add binding
documentation for the GPIO controller found in BCM6318, BCM6328, BCM6358,
BCM6362, BCM6368 and BCM63268 SoCs.
Co-developed-by: Jonas Gorski
Signed-off-by: Jonas Gorski
Signed-off-by: Álvaro Fernández Rojas
---
v8:
This is needed for properly registering GPIO regmap as a child of a regmap
pin controller.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Michael Walle
Reviewed-by: Andy Shevchenko
---
v8: no changes
v7: add gpio-regmap.c comment
v6: add comment and simplify of_node assignment
v5:
The current code doesn't check if GPIOLIB_IRQCHIP is enabled, which results in
a compilation error when trying to build gpio-regmap if CONFIG_GPIOLIB_IRQCHIP
isn't enabled.
Fixes: 6a45b0e2589f ("gpiolib: Introduce gpiochip_irqchip_add_domain()")
Suggested-by: Michael Walle
Signed-off-by: Álvaro
Álvaro Fernández Rojas
lun, 15 mar 12:42 (hace 2 días)
para Linus, Bartosz, Rob, Florian, bcm-kernel-feedback-list, Lee, Michael, mí,
Jonas, Necip, Andy, linux-gpio, devicetree, linux-arm-kernel, linux-kernel
First of all, I've based this on the patches sent by Jonas Gorski back in
2016:
On Thu, Feb 25, 2021 at 12:20:56PM +0100, Arnd Bergmann wrote:
> diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S
> index bad2b9eaab22..926cdb597a45 100644
> --- a/arch/arm64/kernel/vmlinux.lds.S
> +++ b/arch/arm64/kernel/vmlinux.lds.S
> @@ -217,7 +217,7 @@ SECTIONS
>
On 2021-03-17 22:22, Avri Altman wrote:
On 2021-03-17 20:22, Avri Altman wrote:
>>
>> On 2021-03-17 19:23, Avri Altman wrote:
>> >>
>> >> On 2021-03-02 21:24, Avri Altman wrote:
>> >> > The spec does not define what is the host's recommended response
when
>> >> > the device send hpb dev reset
On 17.03.21 15:31, Michal Hocko wrote:
On Wed 17-03-21 12:12:51, Oscar Salvador wrote:
pfn_range_valid_contig() bails out when it finds an in-use page or a
hugetlb page, among other things.
We can drop the in-use page check since __alloc_contig_pages can migrate
away those pages, and the
On 17.03.21 15:08, Oscar Salvador wrote:
On Tue, Mar 16, 2021 at 06:45:17PM +0100, David Hildenbrand wrote:
I find that cross reference to vmemmap code a little hard to digest.
I would have assume that we don't have to care about PMDs in this
code here at all. The vmemmap population code should
On 3/17/21 10:10 AM, Waiman Long wrote:
On 3/17/21 9:55 AM, Peter Zijlstra wrote:
On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote:
Using gcc 8.4.1, the generated __mutex_lock function has the same
size (with
last instruction at offset +5179) with or without this patch. Well,
you
On Wed 17-03-21 12:12:51, Oscar Salvador wrote:
> pfn_range_valid_contig() bails out when it finds an in-use page or a
> hugetlb page, among other things.
> We can drop the in-use page check since __alloc_contig_pages can migrate
> away those pages, and the hugetlb page check can go too since
>
Hi Qi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.12-rc3 next-20210317]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented
MODULE_DEVICE_TABLE is defined in , which is not
included. Add the include to fix the build error its lack caused.
Cc: Sumit Garg
Signed-off-by: Ahmad Fatoum
---
security/keys/trusted-keys/trusted_tee.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi "Bence,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v5.12-rc3 next-20210317]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '-
* Sebastian Reichel [210317 13:50]:
> '< parameters parameters>' and '< parameters>,
> < parameters>' result in the same DTB, but second format has
> better source code readability. Also 'dtbs_check' currently uses
> this format to determine the amount of items specified, so using
> this syntax
On Wed 17-03-21 12:12:50, Oscar Salvador wrote:
> alloc_contig_range() will fail if it finds a HugeTLB page within the range,
> without a chance to handle them. Since HugeTLB pages can be migrated as any
> LRU or Movable page, it does not make sense to bail out without trying.
> Enable the
On 3/17/21 9:20 AM, Bhupesh Sharma wrote:
Hi Rob,
Thanks for your review.
On Wed, 17 Mar 2021 at 03:58, Rob Herring wrote:
On Wed, Mar 10, 2021 at 10:54:57AM +0530, Bhupesh Sharma wrote:
Newer qcom chips support newer versions of the qce IP, so add
new compatible strings for qcom-qce
On Wed, Mar 17, 2021 at 01:37:16PM +, David Woodhouse wrote:
> If we can get to the point where we don't even need to check
> amd_iommu_irq_remap in the ...select() function because the IRQ domain
> is never even registered in the case where the flag ends up false, all
> the better :)
This
On Wed, Mar 17, 2021 at 04:36:13PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rcu tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: modpost: "rcu_read_lock_longwait_held" [kernel/rcu/rcutorture.ko]
> undefined!
> ERROR: modpost:
On ARM64, cat /sys/kernel/debug/page_owner, all pages return the same
stack:
stack_trace_save+0x4c/0x78
register_early_stack+0x34/0x70
init_page_owner+0x34/0x230
page_ext_init+0x1bc/0x1dc
The reason is that:
check_recursive_alloc always return 1 because that
entries[0] is always equal to ip
On arm64, cat /sys/kernel/debug/page_owner
All pages return the same stack
stack_trace_save+0x4c/0x78
register_early_stack+0x34/0x70
init_page_owner+0x34/0x230
page_ext_init+0x1bc/0x1dc
The reason is arch_stack_walk save 2 more entries than before.
To fix it, add skip in arch_stack_walk
***
ARM64 need to modify the stacktrace_cookie->skip.
Signed-off-by: Chen Jun
---
include/linux/stacktrace.h | 7 +++
kernel/stacktrace.c| 7 ---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/include/linux/stacktrace.h b/include/linux/stacktrace.h
index
On Wed 17-03-21 12:12:49, Oscar Salvador wrote:
> alloc_contig_range will fail if it ever sees a HugeTLB page within the
> range we are trying to allocate, even when that page is free and can be
> easily reallocated.
> This has proved to be problematic for some users of alloc_contic_range,
> e.g:
>
> On 2021-03-17 20:22, Avri Altman wrote:
> >>
> >> On 2021-03-17 19:23, Avri Altman wrote:
> >> >>
> >> >> On 2021-03-02 21:24, Avri Altman wrote:
> >> >> > The spec does not define what is the host's recommended response
> when
> >> >> > the device send hpb dev reset response (oper 0x2).
>
We need the host to be in control of cacheability of its own mappings,
so let's disable FWB altogether in its stage 2.
Signed-off-by: Quentin Perret
---
Obviously this will have to be folded in the relevant patch for v6, but
I kept it separate for the sake of review.
---
On Wed, Mar 17, 2021 at 12:30:11PM +, Matthew Wilcox (Oracle) wrote:
> page_mapping_file() is only used by some architectures, and then it
> is usually only used in one place. Make it a static inline function
> so other architectures don't have to carry this dead code.
>
> Signed-off-by:
Hi folks,
This is an alternative solution to the KVM_PGTABLE_PROT_S2_NOFWB patch I
shared earlier (and which is a bit of a hack).
With this series we basically force FWB off for the host stage-2, even
when the CPUs support it. This is done by passing flags to the pgtable
init function, and
In order to further configure stage-2 page-tables, pass flags to the
init function using a new enum.
The first of these flags allows to disable FWB even if the hardware
supports it as we will need to do so for the host stage-2.
Signed-off-by: Quentin Perret
---
One question is, do we want to
On Wed, Mar 17, 2021 at 10:10:16AM -0400, Waiman Long wrote:
> On 3/17/21 9:55 AM, Peter Zijlstra wrote:
> > On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote:
> >
> > > Using gcc 8.4.1, the generated __mutex_lock function has the same size
> > > (with
> > > last instruction at offset
On Wed, Mar 17, 2021 at 9:53 PM Menglong Dong wrote:
>
...
>
> Seems that the inconsistent usages of 'msg_flags' is a lot, for example the
> 'recvmsg()' in 'struct proto' and 'recvmsg()' in 'struct proto_ops':
>
> int (*recvmsg)(struct sock *sk, struct msghdr *msg,
> size_t len, int
On 17 March 2021 13:32:35 GMT, Joerg Roedel wrote:
>On Wed, Mar 17, 2021 at 11:47:11AM +, David Woodhouse wrote:
>> If you've already moved the Stoney Ridge check out of the way,
>there's
>> no real reason why you can't just set
>init_state=IOMMU_CMDLINE_DISABLED
>> directly from
On Tue, Mar 16, 2021 at 05:35:43PM -0700, Florian Fainelli wrote:
> Hi Greg, Sasha, Jaakub and David,
>
> This patch series contains backports for a change that recently made it
> upstream as f9b3827ee66cfcf297d0acd6ecf33653a5f297ef ("net: dsa: b53:
> Support setting learning on port") however
On Wed, Mar 17, 2021 at 02:52:23PM +0100, Miroslav Benes wrote:
> > + if (!elf_symbol_add(elf, sym, SHN_XINDEX)) {
> > + WARN("elf_symbol_add");
> > + return NULL;
> > + }
>
> SHN_XINDEX means that the extended section index is used. Above you seem
> to use it in the
On Wed 17-03-21 12:12:48, Oscar Salvador wrote:
> Currently, isolate_migratepages_{range,block} and their callers use
> a pfn == 0 vs pfn != 0 scheme to let the caller know whether there was
> any error during isolation.
> This does not work as soon as we need to start reporting different error
>
The bit function callbacks, read_bit, write_bit, touch_bit and triplet
are an optional implementation in the master drivers. The ds1wm driver
for example does not implement them. If the generic touch_bit is called,
the w1_read_bit and w1_write_bit functions are used, which just call
the
On Wed, Mar 10, 2021 at 10:54:05AM +0800, dillon min wrote:
> Hi Sascha,
>
> Thanks for reviewing.
>
> On Tue, Mar 9, 2021 at 8:18 PM Sascha Hauer wrote:
> >
> > On Tue, Mar 09, 2021 at 02:15:19PM +0800, dillon.min...@gmail.com wrote:
> > > From: dillon min
> > >
> > > This patch intend to fix
On 3/17/21 9:55 AM, Peter Zijlstra wrote:
On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote:
Using gcc 8.4.1, the generated __mutex_lock function has the same size (with
last instruction at offset +5179) with or without this patch. Well, you can
say that this patch is an no-op wrt
On Tue, Mar 16, 2021 at 06:45:17PM +0100, David Hildenbrand wrote:
> > I find that cross reference to vmemmap code a little hard to digest.
> > I would have assume that we don't have to care about PMDs in this
> > code here at all. The vmemmap population code should handle that.
> >
> > I think I
On Wed, Mar 17 2021 at 15:00, Johan Hovold wrote:
> On Wed, Mar 17, 2021 at 02:24:04PM +0100, Thomas Gleixner wrote:
>> Something like the below.
>
> Looks good to me. Do you want to spin that into a patch or shall I do
> it after some testing?
I'll send one in a few
On Wed, Mar 17, 2021 at 02:59:39PM +0100, Boris Brezillon wrote:
> On Wed, 17 Mar 2021 19:22:49 +0530
> Manivannan Sadhasivam wrote:
>
> > On Wed, Mar 17, 2021 at 02:14:49PM +0100, Boris Brezillon wrote:
> > > On Wed, 17 Mar 2021 17:55:13 +0530
> > > Manivannan Sadhasivam wrote:
> > >
> > >
Hello Richard,
On 17.03.21 00:10, Richard Weinberger wrote:
> On Tue, Mar 16, 2021 at 6:24 PM Ahmad Fatoum wrote:
>> This series has been tested with dmcrypt[5] on an i.MX6DL.
>
> Do have this series also in a git repo to pull from?
> I'd like to give it a test on various systems.
Yes, please
On Wed 17-03-21 12:12:47, Oscar Salvador wrote:
> Currently, __alloc_contig_migrate_range can generate -EINTR, -ENOMEM or
> -EBUSY,
> and report them down the chain.
> The problem is that when migrate_pages() reports -ENOMEM, we keep going till
> we
> exhaust all the try-attempts (5 at the
Reading /proc/mdstat with a read buffer size that would not
fit the unused status line in the first read will skip this
line from the output.
So 'dd if=/proc/mdstat bs=64 2>/dev/null' will not print something
like: unused devices:
Don't return NULL immediately in start() for v=2 but call
show()
Hi Lorenzo,
Wed, 17 Mar 2021 10:07:19 +,
Lorenzo Pieralisi wrote:
>
> GIC CPU interfaces versions predating GIC v4.1 were not built to
> accommodate vINTID within the vSGI range; as reported in the GIC
> specifications (8.2 "Changes to the CPU interface"), it is
> CONSTRAINED UNPREDICTABLE
On Wed, Mar 17, 2021 at 4:51 AM Kefeng Wang wrote:
>
> mem_init_print_info() is called in mem_init() on each architecture,
> and pass NULL argument, so using void argument and move it into mm_init().
>
> Acked-by: Dave Hansen
> Signed-off-by: Kefeng Wang
> ---
> v2:
> - Cleanup 'str' line
On 3/17/21 9:31 AM, Peter Zijlstra wrote:
On Wed, Mar 17, 2021 at 02:12:41PM +0100, Peter Zijlstra wrote:
On Wed, Mar 17, 2021 at 12:38:21PM -, tip-bot2 for Waiman Long wrote:
+ /*
+* Treat as trylock for ww_mutex.
+*/
+ mutex_acquire_nest(>dep_map, subclass,
Hello Richard,
On 17.03.21 00:14, Richard Weinberger wrote:
> Ahmad,
>
> On Tue, Mar 16, 2021 at 6:24 PM Ahmad Fatoum wrote:
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +
>> +struct caam_blob_priv *blobifier;
>
> Who is using this pointer too?
> Otherwise I'd
On 3/17/21 6:08 AM, Brent Lu wrote:
This patch adds jsl_rt5682_rt1015p which supports the RT5682 headset
codec and ALC1015Q-VB speaker amplifier combination on JasperLake
platform.
This driver also supports ALC1015Q-CG if running in auto-mode.
Following table shows the audio interface
>
> From: Yue Hu
>
> There are similar code implemetentions for WB configurations in
> ufshcd_wb_{ctrl, toggle_flush_during_h8, toggle_flush}. We can
> extract the part to create a new helper with a flag parameter to
> reduce code duplication.
>
> Meanwhile, change ufshcd_wb_ctrl() ->
On Wed, 17 Mar 2021 09:48:09 +,
Maulik Shah wrote:
>
> Hi Marc,
>
> On 3/17/2021 2:47 PM, Marc Zyngier wrote:
> > On Wed, 17 Mar 2021 05:29:54 +,
> > Maulik Shah wrote:
> >> PDC interrupt controller driver do not use second reg. Remove it.
> > This is a DT file, not a driver. What the
On Wed, Mar 17, 2021 at 02:24:04PM +0100, Thomas Gleixner wrote:
> On Tue, Mar 16 2021 at 11:56, Johan Hovold wrote:
> > It seems to me that forced interrupt threading cannot generally work
> > without updating drivers that expose locks that can be taken by other
> > interrupt handlers, for
On Wed, 17 Mar 2021 19:22:49 +0530
Manivannan Sadhasivam wrote:
> On Wed, Mar 17, 2021 at 02:14:49PM +0100, Boris Brezillon wrote:
> > On Wed, 17 Mar 2021 17:55:13 +0530
> > Manivannan Sadhasivam wrote:
> >
> > > On a typical end product, a vendor may choose to secure some regions in
> > >
On Fri, Mar 12 2021 at 07:36, Ira Weiny wrote:
> On Fri, Mar 12, 2021 at 07:54:13AM +0100, Christoph Hellwig wrote:
>> So with the new kmap_local interface is it possible / advisable to
>> use local kmaps over code that might schedule(), e.g. to wait for I/O?
>
> It is possible yes. "Advisable" I
Hello Jarkko,
On 16.03.21 20:22, Jarkko Sakkinen wrote:
> On Tue, Mar 16, 2021 at 06:01:18PM +0100, Ahmad Fatoum wrote:
>> The Cryptographic Acceleration and Assurance Module (CAAM) is an IP core
>> built into many newer i.MX and QorIQ SoCs by NXP.
>>
>> The CAAM does crypto acceleration,
On Wed, Mar 17, 2021 at 06:47:18PM +0530, Amey Narkhede wrote:
> On 21/03/17 01:47PM, Leon Romanovsky wrote:
> > On Wed, Mar 17, 2021 at 04:53:09PM +0530, Amey Narkhede wrote:
> > > On 21/03/17 01:02PM, Leon Romanovsky wrote:
> > > > On Wed, Mar 17, 2021 at 03:54:47PM +0530, Amey Narkhede wrote:
>
Linux next 20210317 tag building s390 architecture failed.
- s390 (defconfig) with gcc-8 - Failed
- s390 (defconfig) with gcc-9 - Failed
- s390 (defconfig) with gcc-10 - Failed
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=s390
CROSS_COMPILE=s390x-linux
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/lp8727_charger.txt | 43 -
.../bindings/power/supply/ti,lp8727.yaml | 90 +++
2 files changed, 90 insertions(+), 43 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/lltc,lt3651-charger.yaml | 44 +++
.../bindings/power/supply/lt3651-charger.txt | 29
2 files changed, 44 insertions(+), 29 deletions(-)
create mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/da9150-charger.txt | 26 --
.../bindings/power/supply/da9150-fg.txt | 23
.../power/supply/dlg,da9150-charger.yaml | 52 +++
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/act8945a-charger.txt | 44 ---
.../supply/active-semi,act8945a-charger.yaml | 76 +++
2 files changed, 76 insertions(+), 44 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Cc: Chen-Yu Tsai
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/axp20x_ac_power.txt | 25 ---
.../bindings/power/supply/axp20x_battery.txt | 20 -
.../power/supply/axp20x_usb_power.txt | 41 ---
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/microchip,ucs1002.txt| 27 --
.../power/supply/microchip,ucs1002.yaml | 51 +++
2 files changed, 51 insertions(+), 27 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/lltc,ltc294x.yaml | 66 +++
.../bindings/power/supply/ltc2941.txt | 28
2 files changed, 66 insertions(+), 28 deletions(-)
create mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/qcom,pm8941-charger.yaml | 169 ++
.../bindings/power/supply/qcom_smbb.txt | 150
2 files changed, 169 insertions(+), 150 deletions(-)
create mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/richtek,rt9455.yaml | 90 +++
.../bindings/power/supply/rt9455_charger.txt | 46 --
2 files changed, 90 insertions(+), 46 deletions(-)
create mode 100644
On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote:
> Using gcc 8.4.1, the generated __mutex_lock function has the same size (with
> last instruction at offset +5179) with or without this patch. Well, you can
> say that this patch is an no-op wrt generated code.
OK, then GCC has gotten
On Wed, Mar 17, 2021 at 5:36 PM Andy Shevchenko
wrote:
>
...
>
> The problematic code is negation of the flags when it's done in
> operations like &.
> It maybe fixed by swapping positions of the arguments, i.e. ~(FOO |
> BAR) & flags.
>
> All this is a beast called "integer promotions" in the C
On Wed, Mar 17, 2021 at 02:14:49PM +0100, Boris Brezillon wrote:
> On Wed, 17 Mar 2021 17:55:13 +0530
> Manivannan Sadhasivam wrote:
>
> > On a typical end product, a vendor may choose to secure some regions in
> > the NAND memory which are supposed to stay intact between FW upgrades.
> > The
[ also correcting my e-mail address ]
On Fri, 12 Mar 2021, Peter Zijlstra wrote:
Just a remark regarding SHN_XINDEX...
> +static bool elf_symbol_add(struct elf *elf, struct symbol *sym, Elf32_Word
> shndx)
> +{
> + struct list_head *entry;
> + struct rb_node *pnode;
> +
> +
On 2021-03-17 20:22, Avri Altman wrote:
On 2021-03-17 19:23, Avri Altman wrote:
>>
>> On 2021-03-02 21:24, Avri Altman wrote:
>> > The spec does not define what is the host's recommended response when
>> > the device send hpb dev reset response (oper 0x2).
>> >
>> > We will update all active
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/qcom,coincell-charger.txt| 48
.../power/supply/qcom,pm8941-coincell.yaml| 57 +++
2 files changed, 57 insertions(+), 48 deletions(-)
delete mode 100644
Existing in-tree users make use of '"ti,bq20z45", "sbs,sbs-battery"', so
add it to the list of known compatible strings.
Also add missing support for the generic 'power-supplies' property by
importing power-supply.yaml and setting unevaluatedProperties instead
of additionalProperties.
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/max17040_battery.txt | 52 --
.../bindings/power/supply/maxim,max17040.yaml | 95 +++
2 files changed, 95 insertions(+), 52 deletions(-)
delete mode 100644
Signed-off-by: Sebastian Reichel
---
Documentation/devicetree/bindings/power/supply/battery.txt | 3 ---
Documentation/devicetree/bindings/power/supply/bq27xxx.yaml| 2 +-
.../devicetree/bindings/power/supply/rohm,bd99954.yaml | 2 +-
3 files changed, 2 insertions(+), 5
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/olpc-battery.yaml | 27 +++
.../bindings/power/supply/olpc_battery.txt| 5
2 files changed, 27 insertions(+), 5 deletions(-)
create mode 100644
The file has been replaced by power-supply.yaml and all links
have been updated to the new file.
Signed-off-by: Sebastian Reichel
---
Documentation/devicetree/bindings/power/supply/power_supply.txt | 2 --
1 file changed, 2 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Note: The battery node does not have a compatible value and needs
to be described from the binding file for the PMIC. That has not
yet been converted, so I kept the information in plaintext for now.
Signed-off-by: Sebastian Reichel
---
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/maxim,max14656.txt | 23 --
.../bindings/power/supply/maxim,max14656.yaml | 45 +++
2 files changed, 45 insertions(+), 23 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/tps65090-charger.yaml| 36 +++
.../bindings/power/supply/tps65090.txt| 17 -
2 files changed, 36 insertions(+), 17 deletions(-)
create mode 100644
Convert the binding to DT schema format.
Cc: Pali Rohár
Signed-off-by: Sebastian Reichel
---
.../power/supply/nokia,n900-battery.yaml | 49 +++
.../bindings/power/supply/rx51-battery.txt| 25 --
2 files changed, 49 insertions(+), 25 deletions(-)
create mode
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/maxim,ds2760.txt| 26 ---
.../bindings/power/supply/maxim,ds2760.yaml | 43 +++
2 files changed, 43 insertions(+), 26 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/sbs,sbs-manager.txt | 66 ---
.../power/supply/sbs,sbs-manager.yaml | 107 ++
2 files changed, 107 insertions(+), 66 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/max8903-charger.txt | 24 ---
.../bindings/power/supply/maxim,max8903.yaml | 67 +++
2 files changed, 67 insertions(+), 24 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../power/supply/max17042_battery.txt | 35 -
.../bindings/power/supply/maxim,max17042.yaml | 78 +++
2 files changed, 78 insertions(+), 35 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/twl-charger.txt | 30
.../power/supply/twl4030-charger.yaml | 68 +++
2 files changed, 68 insertions(+), 30 deletions(-)
delete mode 100644
Convert the binding to DT schema format.
Signed-off-by: Sebastian Reichel
---
.../bindings/power/supply/sc27xx-fg.txt | 59 ---
.../bindings/power/supply/sc27xx-fg.yaml | 98 +++
2 files changed, 98 insertions(+), 59 deletions(-)
delete mode 100644
701 - 800 of 1440 matches
Mail list logo
