Re: Please create the email alias do-not-apply-to-sta...@kernel.org -> /dev/null
Em Tue, 23 Apr 2024 00:04:01 +0200 Greg KH escreveu: > On Mon, Apr 22, 2024 at 10:46:37PM +0100, Mauro Carvalho Chehab wrote: > > Em Mon, 22 Apr 2024 15:25:18 -0400 > > Konstantin Ryabitsev escreveu: > > > > > On Mon, Apr 22, 2024 at 05:49:29PM +0200, Thorsten Leemhuis wrote: > > > > @Greg, BTW: should this be stable+noauto...@kernel.org or have a > > > > 'vger.' > > > > > > No vger, just stable+whate...@kernel.org. > > > > > > > in it, e.g. stable+noauto...@vger.kernel.org? I assume without 'vger.' > > > > is fine, just wanted to be sure, as > > > > Documentation/process/stable-kernel-rules.rst in all other cases > > > > specifies sta...@vger.kernel.org, so people are likely to get confused. > > > > :-/ #sigh > > > > > > These serve two different purposes: > > > > > > sta...@kernel.org (goes into devnull) > > > sta...@vger.kernel.org (actual mailing list) > > > > > > Confusion happens all the time, unfortunately. > > > > Yeah, I did already used sta...@kernel.org a few times in the > > past. > > > > IMO, the best would be either for stable to also accept it or for > > kernel.org mail server to return an error message (only to the > > submitter) warning about the invalid address, eventually with a > > hint message pointing to the correct value. > > sta...@kernel.org is there to route to /dev/null on purpose so that > developers/maintainers who only want their patches to get picked up when > they hit Linus's tree, will have happen and not notify anyone else. > This is especially good when dealing with security-related things as we > have had MANY people accidentally leak patches way too early by having > cc: sta...@vger.kernel.org in their signed-off-by areas, and forgetting > to tell git send-email to suppress cc: when sending them out for > internal review. Nice! didn't know about that. On a quick check, the only place at documentation mentioning it without vger is at checkpatch.rst. Perhaps it would make sense to document that as well. > Having that bounce would just be noisy for the developers involved. > > thanks, > > greg k-h
Re: Please create the email alias do-not-apply-to-sta...@kernel.org -> /dev/null
Em Mon, 22 Apr 2024 15:25:18 -0400 Konstantin Ryabitsev escreveu: > On Mon, Apr 22, 2024 at 05:49:29PM +0200, Thorsten Leemhuis wrote: > > @Greg, BTW: should this be stable+noauto...@kernel.org or have a > > 'vger.' > > No vger, just stable+whate...@kernel.org. > > > in it, e.g. stable+noauto...@vger.kernel.org? I assume without 'vger.' > > is fine, just wanted to be sure, as > > Documentation/process/stable-kernel-rules.rst in all other cases > > specifies sta...@vger.kernel.org, so people are likely to get confused. > > :-/ #sigh > > These serve two different purposes: > > sta...@kernel.org (goes into devnull) > sta...@vger.kernel.org (actual mailing list) > > Confusion happens all the time, unfortunately. Yeah, I did already used sta...@kernel.org a few times in the past. IMO, the best would be either for stable to also accept it or for kernel.org mail server to return an error message (only to the submitter) warning about the invalid address, eventually with a hint message pointing to the correct value. > > Notably, even if someone uses stable+noauto...@vger.kernel.org, it won't > do anything terrible (it won't bounce, it'll just quietly go into > nowhere because that's not a valid expansion command). > > -K >
Re: Please create the email alias do-not-apply-to-sta...@kernel.org -> /dev/null
Em Wed, 17 Apr 2024 10:16:26 +0200 Greg KH escreveu: > On Wed, Apr 17, 2024 at 09:09:26AM +0100, Mauro Carvalho Chehab wrote: > > Em Wed, 17 Apr 2024 09:48:18 +0200 > > Thorsten Leemhuis escreveu: > > > > > Hi kernel.org helpdesk! > > > > > > Could you please create the email alias > > > do-not-apply-to-sta...@kernel.org which redirects all mail to /dev/null, > > > just like sta...@kernel.org does? > > > > > > That's an idea GregKH brought up a few days ago here: > > > https://lore.kernel.org/all/2024041123-earthling-primarily-4656@gregkh/ > > > > > > To quote: > > > > > > > How about: > > > > cc: # Reason goes here, and > > > > must be present > > > > > > > > and we can make that address be routed to /dev/null just like > > > > is? > > > > > > There was some discussion about using something shorter, but in the end > > > there was no strong opposition and the thread ended a a few days ago. > > > > Heh, a shorter name would make it a lot easier to remember, specially > > since not wanting a patch to go to stable is an exception... I bet > > I'll never remember the right syntax, needing to look at the docs > > every time it would be used. > > > > IMO, something like: > > no-stable > > or > > nostable > > > > would do the trick and would be a lot easier to remember. > > > > Btw, IMO, it won't hurt accepting more than one variant that > > could be allowed, e. g. using a regular expression like: > > > > (do)?[-_]?(nt|not?).*stable > > That's not going to work at the mailing list server, or with my scripts, > sorry. A setting like that would likely be at exim (or similar). Most smtp servers allow some sort of wildcards, as those are used to pass or not e-mails to list servers and/or handle custom mail forward rules. At client level, one could use dovecot with pigeonhole to have sieve rules to filter e-mails. That's what I do here. > > at the scripts used by stable developers - and maybe at the ML server - to > > catch different variations won't hurt, as it sounds likely that people will > > end messing up with a big name like "do-not-apply-to-stable", typing > > instead things like: > > > > do_not_apply_to_stable > > dont-apply-to-stable > > > > and other variants. > > I want this very explicit that someone does not want this applied, and > that it has a reason to do so. And if getting the email right to do so > is the issue with that, that's fine. This is a very rare case that > almost no one should normally hit. Yeah, agreed: those are very rare exceptions. I remember just one or two cases where a media fix patch couldn't be queued to stable. The already-existing workflow worked for those. > And again, if maintainers don't want their tree to have Fixes: and > AUTOBOT run on them, we can easily add that to our lists. That's the > simpler and more explicit thing to do for those that do not want to have > anything backported they do not explicitly mark as such (some subsystems > do this already, like kvm and -mm and xfs, it's fine!). This all is > here because of maintainers who do NOT want to do that. From my side, I'm fine with whatever-explicit-long-filter-email. Regards, Mauro
Re: Please create the email alias do-not-apply-to-sta...@kernel.org -> /dev/null
Em Wed, 17 Apr 2024 09:48:18 +0200 Thorsten Leemhuis escreveu: > Hi kernel.org helpdesk! > > Could you please create the email alias > do-not-apply-to-sta...@kernel.org which redirects all mail to /dev/null, > just like sta...@kernel.org does? > > That's an idea GregKH brought up a few days ago here: > https://lore.kernel.org/all/2024041123-earthling-primarily-4656@gregkh/ > > To quote: > > > How about: > > cc: # Reason goes here, and must be > > present > > > > and we can make that address be routed to /dev/null just like > > is? > > There was some discussion about using something shorter, but in the end > there was no strong opposition and the thread ended a a few days ago. Heh, a shorter name would make it a lot easier to remember, specially since not wanting a patch to go to stable is an exception... I bet I'll never remember the right syntax, needing to look at the docs every time it would be used. IMO, something like: no-stable or nostable would do the trick and would be a lot easier to remember. Btw, IMO, it won't hurt accepting more than one variant that could be allowed, e. g. using a regular expression like: (do)?[-_]?(nt|not?).*stable at the scripts used by stable developers - and maybe at the ML server - to catch different variations won't hurt, as it sounds likely that people will end messing up with a big name like "do-not-apply-to-stable", typing instead things like: do_not_apply_to_stable dont-apply-to-stable and other variants. Just my 2 cents. Regards, Mauro
Re: [PATCH] media: atomisp: silence "dubious: !x | !y" warning
Em Sat, 17 Apr 2021 21:06:27 +0530 Ashish Kalra escreveu: > Upon running sparse, "warning: dubious: !x | !y" is brought to notice > for this file. Logical and bitwise OR are basically the same in this > context so it doesn't cause a runtime bug. But let's change it to > logical OR to make it cleaner and silence the Sparse warning. > > Signed-off-by: Ashish Kalra > --- > .../media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c| 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git > a/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c > b/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c > index 358cb7d2cd4c..3b850bb2d39d 100644 > --- a/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c > +++ b/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c > @@ -58,7 +58,7 @@ sh_css_vf_downscale_log2( > unsigned int ds_log2 = 0; > unsigned int out_width; > > - if ((!out_info) | (!vf_info)) > + if ((!out_info) || (!vf_info)) While here, please get rid of the unneeded parenthesis: if (!out_info || !vf_info) > return -EINVAL; > > out_width = out_info->res.width; Thanks, Mauro
Re: [PATCH] Documentation: syscalls: add a note about ABI-agnostic types
Em Tue, 13 Apr 2021 21:40:20 -0700
Yury Norov escreveu:
> Ping?
>
> On Fri, Apr 09, 2021 at 01:43:04PM -0700, Yury Norov wrote:
> > Recently added memfd_secret() syscall had a flags parameter passed
> > as unsigned long, which requires creation of compat entry for it.
> > It was possible to change the type of flags to unsigned int and so
> > avoid bothering with compat layer.
> >
> > https://www.spinics.net/lists/linux-mm/msg251550.html
> >
> > Documentation/process/adding-syscalls.rst doesn't point clearly about
> > preference of ABI-agnostic types. This patch adds such notification.
> >
> > Signed-off-by: Yury Norov
> > ---
> > Documentation/process/adding-syscalls.rst | 7 +++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Documentation/process/adding-syscalls.rst
> > b/Documentation/process/adding-syscalls.rst
> > index 9af35f4ec728..46add16edf14 100644
> > --- a/Documentation/process/adding-syscalls.rst
> > +++ b/Documentation/process/adding-syscalls.rst
> > @@ -172,6 +172,13 @@ arguments (i.e. parameter 1, 3, 5), to allow use of
> > contiguous pairs of 32-bit
> > registers. (This concern does not apply if the arguments are part of a
> > structure that's passed in by pointer.)
> >
> > +Whenever possible, try to use ABI-agnostic types for passing parameters to
> > +a syscall in order to avoid creating compat entry for it. Linux supports
> > two
> > +ABI models - ILP32 and LP64.
> > + The types like ``void *``, ``long``, ``size_t``,
> > +``off_t`` have different size in those ABIs;
In the case of pointers, the best is to use __u64. The pointer can then
be read on Kernelspace with something like this:
static inline void __user *media_get_uptr(__u64 arg)
{
return (void __user *)(uintptr_t)arg;
}
> > types like ``char`` and ``int``
> > +have the same size and don't require a compat layer support. For flags,
> > it's
> > +always better to use ``unsigned int``.
> > +
I don't think this is true for all compilers on userspace, as the C
standard doesn't define how many bits an int/unsigned int has.
So, even if this is today's reality, things may change in the future.
For instance, I remember we had to replace "int" and "enum" by "__u32"
and "long" by "__u64" at the media uAPI in the past, when we start
seeing x86_64 Kernels with 32-bits userspace and when cameras started
being supported on arm32.
We did have some real bugs with "enum", as, on that time, some
compilers (gcc, I guess) were optimizing them to have less than
32 bits on certain architectures, when it fits.
Thanks,
Mauro
[tip: locking/core] doc: Update rcu_dereference.rst reference
The following commit has been merged into the locking/core branch of tip:
Commit-ID: ba46b21bbdf8c1e8f054f44e7db7d6684720ef78
Gitweb:
https://git.kernel.org/tip/ba46b21bbdf8c1e8f054f44e7db7d6684720ef78
Author:Mauro Carvalho Chehab
AuthorDate:Wed, 13 Jan 2021 11:59:20 +01:00
Committer: Paul E. McKenney
CommitterDate: Mon, 08 Mar 2021 14:29:22 -08:00
doc: Update rcu_dereference.rst reference
Changeset b00aedf978aa ("doc: Convert to rcu_dereference.txt to
rcu_dereference.rst")
renamed: Documentation/RCU/rcu_dereference.txt
to: Documentation/RCU/rcu_dereference.rst.
Update its cross-reference accordingly.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Paul E. McKenney
---
tools/memory-model/Documentation/glossary.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/memory-model/Documentation/glossary.txt
b/tools/memory-model/Documentation/glossary.txt
index b2da636..6f3d16d 100644
--- a/tools/memory-model/Documentation/glossary.txt
+++ b/tools/memory-model/Documentation/glossary.txt
@@ -19,7 +19,7 @@ Address Dependency: When the address of a later memory
access is computed
from the value returned by the rcu_dereference() on line 2, the
address dependency extends from that rcu_dereference() to that
"p->a". In rare cases, optimizing compilers can destroy address
-dependencies. Please see Documentation/RCU/rcu_dereference.txt
+dependencies. Please see Documentation/RCU/rcu_dereference.rst
for more information.
See also "Control Dependency" and "Data Dependency".
[tip: core/rcu] rcu: Fix kfree_rcu() docbook errors
The following commit has been merged into the core/rcu branch of tip:
Commit-ID: e75956bd00cf4246067c6aee7751faf313233435
Gitweb:
https://git.kernel.org/tip/e75956bd00cf4246067c6aee7751faf313233435
Author:Mauro Carvalho Chehab
AuthorDate:Thu, 14 Jan 2021 08:22:02 +01:00
Committer: Paul E. McKenney
CommitterDate: Mon, 08 Mar 2021 14:17:35 -08:00
rcu: Fix kfree_rcu() docbook errors
After commit 5130b8fd0690 ("rcu: Introduce kfree_rcu() single-argument macro"),
kernel-doc now emits two warnings:
./include/linux/rcupdate.h:884: warning: Excess function parameter
'ptr' description in 'kfree_rcu'
./include/linux/rcupdate.h:884: warning: Excess function parameter
'rhf' description in 'kfree_rcu'
This commit added some macro magic in order to call two different versions
of kfree_rcu(), the first having just one argument and the second having
two arguments. That makes it difficult to document the kfree_rcu() arguments
in the docboook header.
In order to make clearer that this macro accepts optional arguments,
this commit uses macro concatenation so that this macro changes from:
#define kfree_rcu kvfree_rcu
to:
#define kfree_rcu(ptr, rhf...) kvfree_rcu(ptr, ## rhf)
That not only helps kernel-doc understand the macro arguments, but also
provides a better C definition that makes clearer that the first argument
is mandatory and the second one is optional.
Fixes: 5130b8fd0690 ("rcu: Introduce kfree_rcu() single-argument macro")
Tested-by: Uladzislau Rezki (Sony)
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Paul E. McKenney
---
include/linux/rcupdate.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
index bd04f72..5cc6dea 100644
--- a/include/linux/rcupdate.h
+++ b/include/linux/rcupdate.h
@@ -881,7 +881,7 @@ static inline notrace void
rcu_read_unlock_sched_notrace(void)
* The BUILD_BUG_ON check must not involve any function calls, hence the
* checks are done in macros here.
*/
-#define kfree_rcu kvfree_rcu
+#define kfree_rcu(ptr, rhf...) kvfree_rcu(ptr, ## rhf)
/**
* kvfree_rcu() - kvfree an object after a grace period.
[PATCH v3 3/8] dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference
Changeset 1ca9d1b1342d ("dt-bindings:iio:adc:motorola,cpcap-adc yaml
conversion")
renamed: Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt
to: Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml.
Update its cross-reference accordingly.
Fixes: 1ca9d1b1342d ("dt-bindings:iio:adc:motorola,cpcap-adc yaml conversion")
Acked-by: Jonathan Cameron
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/mfd/motorola-cpcap.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
index ebdccfb600b9..b52e7a33f0f9 100644
--- a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
+++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
@@ -23,7 +23,7 @@ which are described in the following files:
- Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
- Documentation/devicetree/bindings/rtc/cpcap-rtc.txt
- Documentation/devicetree/bindings/leds/leds-cpcap.txt
-- Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt
+- Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml
The only exception is the audio codec. Instead of a compatible value its
node must be named "audio-codec".
--
2.30.2
[PATCH v3 5/8] docs: vcpu-requests.rst: fix reference for atomic ops
Changeset f0400a77ebdc ("atomic: Delete obsolete documentation")
got rid of atomic_ops.rst, pointing that this was superseded by
Documentation/atomic_*.txt.
Update its reference accordingly.
Fixes: f0400a77ebdc ("atomic: Delete obsolete documentation")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/virt/kvm/vcpu-requests.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/vcpu-requests.rst
b/Documentation/virt/kvm/vcpu-requests.rst
index 5feb3706a7ae..5f8798e7fdf8 100644
--- a/Documentation/virt/kvm/vcpu-requests.rst
+++ b/Documentation/virt/kvm/vcpu-requests.rst
@@ -302,6 +302,6 @@ VCPU returns from the call.
References
==
-.. [atomic-ops] Documentation/core-api/atomic_ops.rst
+.. [atomic-ops] Documentation/atomic_bitops.txt and Documentation/atomic_t.txt
.. [memory-barriers] Documentation/memory-barriers.txt
.. [lwn-mb] https://lwn.net/Articles/573436/
--
2.30.2
[PATCH v3 2/8] dt-bindings: fix references for iio-bindings.txt
The iio-bindings.txt was converted into two files and merged
at the dt-schema git tree at:
https://github.com/devicetree-org/dt-schema
Yet, some documents still refer to the old file. Fix their
references, in order to point to the right URL.
Fixes: dba91f82d580 ("dt-bindings:iio:iio-binding.txt Drop file as content now
in dt-schema")
Acked-by: Jonathan Cameron
Acked-by: Guenter Roeck
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt | 2 +-
Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml | 5 +++--
Documentation/devicetree/bindings/input/adc-joystick.yaml| 4 +++-
.../bindings/input/touchscreen/resistive-adc-touch.txt | 5 -
Documentation/devicetree/bindings/mfd/ab8500.txt | 4 +++-
5 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
b/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
index 37f18d684f6a..4c5c3712970e 100644
--- a/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
+++ b/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
@@ -32,7 +32,7 @@ Optional node properties:
- "#thermal-sensor-cells" Used to expose itself to thermal fw.
Read more about iio bindings at
- Documentation/devicetree/bindings/iio/iio-bindings.txt
+ https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/
Example:
ncp15wb473@0 {
diff --git a/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
b/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
index 9f414dbdae86..433a3fb55a2e 100644
--- a/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
+++ b/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
@@ -14,8 +14,9 @@ description: >
Industrial I/O subsystem bindings for ADC controller found in
Ingenic JZ47xx SoCs.
- ADC clients must use the format described in iio-bindings.txt, giving
- a phandle and IIO specifier pair ("io-channels") to the ADC controller.
+ ADC clients must use the format described in
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml,
+ giving a phandle and IIO specifier pair ("io-channels") to the ADC
controller.
properties:
compatible:
diff --git a/Documentation/devicetree/bindings/input/adc-joystick.yaml
b/Documentation/devicetree/bindings/input/adc-joystick.yaml
index 054406bbd22b..721878d5b7af 100644
--- a/Documentation/devicetree/bindings/input/adc-joystick.yaml
+++ b/Documentation/devicetree/bindings/input/adc-joystick.yaml
@@ -24,7 +24,9 @@ properties:
description: >
List of phandle and IIO specifier pairs.
Each pair defines one ADC channel to which a joystick axis is connected.
- See Documentation/devicetree/bindings/iio/iio-bindings.txt for details.
+ See
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+ for details.
'#address-cells':
const: 1
diff --git
a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
index fee0da12474e..af5223bb5bdd 100644
---
a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
+++
b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
@@ -5,7 +5,10 @@ Required properties:
- compatible: must be "resistive-adc-touch"
The device must be connected to an ADC device that provides channels for
position measurement and optional pressure.
-Refer to Documentation/devicetree/bindings/iio/iio-bindings.txt for details
+Refer to
+https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+for details
+
- iio-channels: must have at least two channels connected to an ADC device.
These should correspond to the channels exposed by the ADC device and should
have the right index as the ADC device registers them. These channels
diff --git a/Documentation/devicetree/bindings/mfd/ab8500.txt
b/Documentation/devicetree/bindings/mfd/ab8500.txt
index d2a6e835c257..937b3e5505e0 100644
--- a/Documentation/devicetree/bindings/mfd/ab8500.txt
+++ b/Documentation/devicetree/bindings/mfd/ab8500.txt
@@ -72,7 +72,9 @@ Required child device properties:
pwm|regulator|rtc|sysctrl|usb]";
A few child devices require ADC channels from the GPADC node. Those follow
the
- standard bindings from iio/iio-bindings.txt and iio/adc/adc.txt
+ standard bindings from
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+ and Documentation/devicetree/bindings/iio/adc/adc.yaml
abx500-temp : io-channels "aux1" and "aux2" for measuring external
temperatures.
--
2.30.2
[PATCH v3 4/8] docs: update sysfs-platform_profile.rst reference
The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
Update its cross-reference accordingly.
Fixes: a2ff95e018f1 ("ACPI: platform: Add platform profile support")
Fixes: 8e0cbf356377 ("Documentation: Add documentation for new platform_profile
sysfs attribute")
Reviewed-by: Hans de Goede
Reviewed-by: Mark Pearson
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/platform_profile.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/platform_profile.h b/include/linux/platform_profile.h
index a6329003aee7..e5cbb6841f3a 100644
--- a/include/linux/platform_profile.h
+++ b/include/linux/platform_profile.h
@@ -2,7 +2,7 @@
/*
* Platform profile sysfs interface
*
- * See Documentation/ABI/testing/sysfs-platform_profile.rst for more
+ * See Documentation/userspace-api/sysfs-platform_profile.rst for more
* information.
*/
--
2.30.2
[PATCH v3 0/8] Fix broken documentation file references
Hi Jon, As files keep being moved around and DT bindings are converted and renamed to yaml, their doc references get outdated, pointing to an invalid places. This series address those. It is based on the top of docs-next tree, and most patches here are independent from the other ones. v3: - Dropped patches already applied at next-20210409 and changes that would cause conflicts there; - Added received acks. v2: - Dropped patches that were already applied, Most of those will be following via Jonathan Cameron's iio tree; - Dropped patches that don't apply on the top of docs next. - Added some new patches fixing other breakages. Mauro Carvalho Chehab (8): dt-bindings: don't use ../dir for doc references dt-bindings: fix references for iio-bindings.txt dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference docs: update sysfs-platform_profile.rst reference docs: vcpu-requests.rst: fix reference for atomic ops docs: replace transation references for reporting-bugs.rst docs: translations/zh_CN: fix a typo at 8.Conclusion.rst docs: sched-bwc.rst: fix a typo on a doc name .../devicetree/bindings/hwmon/ntc_thermistor.txt | 2 +- .../devicetree/bindings/iio/adc/ingenic,adc.yaml | 5 +++-- .../devicetree/bindings/input/adc-joystick.yaml | 4 +++- .../input/touchscreen/resistive-adc-touch.txt| 5 - Documentation/devicetree/bindings/mfd/ab8500.txt | 4 +++- .../devicetree/bindings/mfd/motorola-cpcap.txt | 16 Documentation/scheduler/sched-bwc.rst| 2 +- .../translations/it_IT/process/howto.rst | 2 +- Documentation/translations/ja_JP/howto.rst | 2 +- Documentation/translations/zh_CN/SecurityBugs| 2 +- .../zh_CN/admin-guide/reporting-issues.rst | 4 ++-- .../translations/zh_CN/process/8.Conclusion.rst | 2 +- .../translations/zh_CN/process/howto.rst | 2 +- Documentation/virt/kvm/vcpu-requests.rst | 2 +- include/linux/platform_profile.h | 2 +- 15 files changed, 32 insertions(+), 24 deletions(-) -- 2.30.2
[PATCH v3 7/8] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst
transaltions -> translations Acked-by: Wu XiangCheng Signed-off-by: Mauro Carvalho Chehab --- Documentation/translations/zh_CN/process/8.Conclusion.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/translations/zh_CN/process/8.Conclusion.rst b/Documentation/translations/zh_CN/process/8.Conclusion.rst index 71c3e30efc6f..4707f0101964 100644 --- a/Documentation/translations/zh_CN/process/8.Conclusion.rst +++ b/Documentation/translations/zh_CN/process/8.Conclusion.rst @@ -19,7 +19,7 @@ :ref:`Documentation/translations/zh_CN/process/howto.rst ` 文件是一个重要的起点； :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst ` -和 :ref:`Documentation/transaltions/zh_CN/process/submitting-drivers.rst ` +和 :ref:`Documentation/translations/zh_CN/process/submitting-drivers.rst ` 也是所有内核开发人员都应该阅读的内容。许多内部内核API都是使用kerneldoc机制 记录的；“make htmldocs”或“make pdfdocs”可用于以HTML或PDF格式生成这些文档 （尽管某些发行版提供的tex版本会遇到内部限制，无法正确处理文档）。 -- 2.30.2
[PATCH v3 6/8] docs: replace transation references for reporting-bugs.rst
Changeset d2ce285378b0 ("docs: make reporting-issues.rst official and delete
reporting-bugs.rst")
dropped reporting-bugs.rst, in favor of reporting-issues.rst, but
translations still need to be updated, in order to point to the
new file.
Fixes: d2ce285378b0 ("docs: make reporting-issues.rst official and delete
reporting-bugs.rst")
Acked-by: Wu XiangCheng
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/translations/it_IT/process/howto.rst| 2 +-
Documentation/translations/ja_JP/howto.rst| 2 +-
Documentation/translations/zh_CN/SecurityBugs | 2 +-
.../translations/zh_CN/admin-guide/reporting-issues.rst | 4 ++--
Documentation/translations/zh_CN/process/howto.rst| 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/translations/it_IT/process/howto.rst
b/Documentation/translations/it_IT/process/howto.rst
index 1db5a1082389..4962057f50fa 100644
--- a/Documentation/translations/it_IT/process/howto.rst
+++ b/Documentation/translations/it_IT/process/howto.rst
@@ -364,7 +364,7 @@ Per maggiori dettagli su come usare il bugzilla del kernel,
guardare:
https://bugzilla.kernel.org/page.cgi?id=faq.html
-Il file admin-guide/reporting-bugs.rst nella cartella principale del kernel
+Il file admin-guide/reporting-issues.rst nella cartella principale del kernel
fornisce un buon modello sul come segnalare un baco nel kernel, e spiega quali
informazioni sono necessarie agli sviluppatori per poter aiutare il
rintracciamento del problema.
diff --git a/Documentation/translations/ja_JP/howto.rst
b/Documentation/translations/ja_JP/howto.rst
index 73ebdab4ced7..3051ff787e69 100644
--- a/Documentation/translations/ja_JP/howto.rst
+++ b/Documentation/translations/ja_JP/howto.rst
@@ -367,7 +367,7 @@ kernel bugzilla を使うかの詳細は、以下を参照してください -
https://bugzilla.kernel.org/page.cgi?id=faq.html
メインカーネルソースディレクトリにあるファイル
-admin-guide/reporting-bugs.rstはカーネルバグらしいものについてどうレポー
+admin-guide/reporting-issues.rstはカーネルバグらしいものについてどうレポー
トするかの良いテンプレートであり、問題の追跡を助けるためにカーネル開発
者にとってどんな情報が必要なのかの詳細が書かれています。
diff --git a/Documentation/translations/zh_CN/SecurityBugs
b/Documentation/translations/zh_CN/SecurityBugs
index 2d0fffd122ce..980199d88eca 100644
--- a/Documentation/translations/zh_CN/SecurityBugs
+++ b/Documentation/translations/zh_CN/SecurityBugs
@@ -31,7 +31,7 @@ linux内核安全团队可以通过email来联系。这是
一组独立的安全工作人员，可以帮助改善漏洞报告并且公布和取消一个修复。安
全团队有可能会从部分的维护者那里引进额外的帮助来了解并且修复安全漏洞。
当遇到任何漏洞，所能提供的信息越多就越能诊断和修复。如果你不清楚什么
-是有帮助的信息，那就请重温一下admin-guide/reporting-bugs.rst文件中的概述过程。任
+是有帮助的信息，那就请重温一下admin-guide/reporting-issues.rst文件中的概述过程。任
何攻击性的代码都是非常有用的，未经报告者的同意不会被取消，除非它已经
被公布于众。
diff --git a/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
b/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
index 2805c1a03cd5..72c8e2db88c0 100644
--- a/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
+++ b/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
@@ -19,7 +19,7 @@
.. important::
- 本文档将取代“Documentation/admin-guide/reporting-bugs.rst”。主要的工作
+ 本文档将取代“Documentation/admin-guide/reporting-issues.rst”。主要的工作
已经完成，你可以自由地按照其指示来向Linux内核开发者报告问题。但请留意，
下面的文字还需要一些润色和校审。现阶段它被合并到Linux内核源代码中，以使
这个过程更容易，并增加文本的可见性。
@@ -726,7 +726,7 @@ tar 存档包。
.. note::
FIXME: 本节文字暂时是占位符，与目前
- “Documentation/admin-guide/reporting-bugs.rst”中的旧文字非常相似。它和它
+ “Documentation/admin-guide/reporting-issues.rst”中的旧文字非常相似。它和它
所引用的文档已经过时，因此需要重新审视。因此，请将此说明视为一个求助：如
果你熟悉这个主题，请写几行适合这里的文字。或者只需向本文件的主要作者（见
导言）大致概述一下当前的情况，因为他们也许能写出一些东西来。
diff --git a/Documentation/translations/zh_CN/process/howto.rst
b/Documentation/translations/zh_CN/process/howto.rst
index ee3dee476d57..c87cd529d769 100644
--- a/Documentation/translations/zh_CN/process/howto.rst
+++ b/Documentation/translations/zh_CN/process/howto.rst
@@ -280,7 +280,7 @@ bugzilla.kernel.org是Linux内核开发者们用来跟踪内核Bug的网站。
http://test.kernel.org/bugzilla/faq.html
-内核源码主目录中的:ref:`admin-guide/reporting-bugs.rst `
+内核源码主目录中的:ref:`admin-guide/reporting-issues.rst `
文件里有一个很好的模板。它指导用户如何报告可能的内核bug以及需要提供哪些信息
来帮助内核开发者们找到问题的根源。
--
2.30.2
[PATCH v3 1/8] dt-bindings: don't use ../dir for doc references
As documents have been renamed and moved around, their references will break, but this will be unnoticed, as the script which checks for it won't handle "../" references. So, replace them by the full patch. Signed-off-by: Mauro Carvalho Chehab --- .../input/touchscreen/resistive-adc-touch.txt| 2 +- .../devicetree/bindings/mfd/motorola-cpcap.txt | 16 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt index 51456c0e9a27..fee0da12474e 100644 --- a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt +++ b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt @@ -5,7 +5,7 @@ Required properties: - compatible: must be "resistive-adc-touch" The device must be connected to an ADC device that provides channels for position measurement and optional pressure. -Refer to ../iio/iio-bindings.txt for details +Refer to Documentation/devicetree/bindings/iio/iio-bindings.txt for details - iio-channels: must have at least two channels connected to an ADC device. These should correspond to the channels exposed by the ADC device and should have the right index as the ADC device registers them. These channels diff --git a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt index 5ddcc8f4febc..ebdccfb600b9 100644 --- a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt +++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt @@ -16,14 +16,14 @@ Optional subnodes: The sub-functions of CPCAP get their own node with their own compatible values, which are described in the following files: -- ../power/supply/cpcap-battery.txt -- ../power/supply/cpcap-charger.txt -- ../regulator/cpcap-regulator.txt -- ../phy/phy-cpcap-usb.txt -- ../input/cpcap-pwrbutton.txt -- ../rtc/cpcap-rtc.txt -- ../leds/leds-cpcap.txt -- ../iio/adc/cpcap-adc.txt +- Documentation/devicetree/bindings/power/supply/cpcap-battery.txt +- Documentation/devicetree/bindings/power/supply/cpcap-charger.txt +- Documentation/devicetree/bindings/regulator/cpcap-regulator.txt +- Documentation/devicetree/bindings/phy/phy-cpcap-usb.txt +- Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt +- Documentation/devicetree/bindings/rtc/cpcap-rtc.txt +- Documentation/devicetree/bindings/leds/leds-cpcap.txt +- Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt The only exception is the audio codec. Instead of a compatible value its node must be named "audio-codec". -- 2.30.2
[PATCH v3 8/8] docs: sched-bwc.rst: fix a typo on a doc name
cgroupv2.rst -> cgroup-v2.rst Signed-off-by: Mauro Carvalho Chehab --- Documentation/scheduler/sched-bwc.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst index 845eee659199..1fc73555f5c4 100644 --- a/Documentation/scheduler/sched-bwc.rst +++ b/Documentation/scheduler/sched-bwc.rst @@ -29,7 +29,7 @@ Quota and period are managed within the cpu subsystem via cgroupfs. .. note:: The cgroupfs files described in this section are only applicable to cgroup v1. For cgroup v2, see - :ref:`Documentation/admin-guide/cgroupv2.rst `. + :ref:`Documentation/admin-guide/cgroup-v2.rst `. - cpu.cfs_quota_us: the total available run-time within a period (in microseconds) -- 2.30.2
[PATCH 3/3] media: venus: don't de-reference NULL pointers at IRQ time
Smatch is warning that:
drivers/media/platform/qcom/venus/hfi_venus.c:1100 venus_isr() warn:
variable dereferenced before check 'hdev' (see line 1097)
The logic basically does:
hdev = to_hfi_priv(core);
with is translated to:
hdev = core->priv;
If the IRQ code can receive a NULL pointer for hdev, there's
a bug there, as it will first try to de-reference the pointer,
and then check if it is null.
After looking at the code, it seems that this indeed can happen:
Basically, the venus IRQ thread is started with:
devm_request_threaded_irq()
So, it will only be freed after the driver unbinds.
In order to prevent the IRQ code to work with freed data,
the logic at venus_hfi_destroy() sets core->priv to NULL,
which would make the IRQ code to ignore any pending IRQs.
There is, however a race condition, as core->priv is set
to NULL only after being freed. So, we need also to move the
core->priv = NULL to happen earlier.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/qcom/venus/hfi_venus.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/media/platform/qcom/venus/hfi_venus.c
b/drivers/media/platform/qcom/venus/hfi_venus.c
index cebb20cf371f..ce98c523b3c6 100644
--- a/drivers/media/platform/qcom/venus/hfi_venus.c
+++ b/drivers/media/platform/qcom/venus/hfi_venus.c
@@ -1094,12 +1094,15 @@ static irqreturn_t venus_isr(struct venus_core *core)
{
struct venus_hfi_device *hdev = to_hfi_priv(core);
u32 status;
- void __iomem *cpu_cs_base = hdev->core->cpu_cs_base;
- void __iomem *wrapper_base = hdev->core->wrapper_base;
+ void __iomem *cpu_cs_base;
+ void __iomem *wrapper_base;
if (!hdev)
return IRQ_NONE;
+ cpu_cs_base = hdev->core->cpu_cs_base;
+ wrapper_base = hdev->core->wrapper_base;
+
status = readl(wrapper_base + WRAPPER_INTR_STATUS);
if (IS_V6(core)) {
if (status & WRAPPER_INTR_STATUS_A2H_MASK ||
@@ -1650,10 +1653,10 @@ void venus_hfi_destroy(struct venus_core *core)
{
struct venus_hfi_device *hdev = to_hfi_priv(core);
+ core->priv = NULL;
venus_interface_queues_release(hdev);
mutex_destroy(>lock);
kfree(hdev);
- core->priv = NULL;
core->ops = NULL;
}
--
2.30.2
[PATCH 1/3] media: venus: use NULL instead of zero for pointers
As reported by sparse: drivers/media/platform/qcom/venus/core.c:227:41: warning: Using plain integer as NULL pointer drivers/media/platform/qcom/venus/core.c:228:34: warning: Using plain integer as NULL pointer Two vars are using zero instead of NULL for pointers. Not really an issue, but using NULL makes it clearer that the init data is expecting a pointer. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/platform/qcom/venus/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/media/platform/qcom/venus/core.c b/drivers/media/platform/qcom/venus/core.c index f5b88b96f5f7..4451e3c11bc0 100644 --- a/drivers/media/platform/qcom/venus/core.c +++ b/drivers/media/platform/qcom/venus/core.c @@ -224,8 +224,8 @@ static void venus_assign_register_offsets(struct venus_core *core) core->cpu_cs_base = core->base + CPU_CS_BASE; core->cpu_ic_base = core->base + CPU_IC_BASE; core->wrapper_base = core->base + WRAPPER_BASE; - core->wrapper_tz_base = 0; - core->aon_base = 0; + core->wrapper_tz_base = NULL; + core->aon_base = NULL; } } -- 2.30.2
[PATCH 2/3] media: rdacm21: describe better a truncation
As warned by sparse: drivers/media/i2c/rdacm21.c:348:62: warning: cast truncates bits from constant value (300a becomes a) the intention of the code is to get just the lowest 8 bits. So, instead of using a typecast, use a bit and logic. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/i2c/rdacm21.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/i2c/rdacm21.c b/drivers/media/i2c/rdacm21.c index dcc21515e5a4..179d107f494c 100644 --- a/drivers/media/i2c/rdacm21.c +++ b/drivers/media/i2c/rdacm21.c @@ -345,7 +345,7 @@ static int ov10640_initialize(struct rdacm21_device *dev) /* Read OV10640 ID to test communications. */ ov490_write_reg(dev, OV490_SCCB_SLAVE0_DIR, OV490_SCCB_SLAVE_READ); ov490_write_reg(dev, OV490_SCCB_SLAVE0_ADDR_HIGH, OV10640_CHIP_ID >> 8); - ov490_write_reg(dev, OV490_SCCB_SLAVE0_ADDR_LOW, (u8)OV10640_CHIP_ID); + ov490_write_reg(dev, OV490_SCCB_SLAVE0_ADDR_LOW, OV10640_CHIP_ID & 0xff); /* Trigger SCCB slave transaction and give it some time to complete. */ ov490_write_reg(dev, OV490_HOST_CMD, OV490_HOST_CMD_TRIGGER); -- 2.30.2
Re: [PATCH v2 17/19] docs: replace transation references for reporting-bugs.rst
Em Wed, 7 Apr 2021 10:52:14 +0200
Thorsten Leemhuis escreveu:
> On 07.04.21 10:20, Mauro Carvalho Chehab wrote:
> > Changeset d2ce285378b0 ("docs: make reporting-issues.rst official and
> > delete reporting-bugs.rst")
> > dropped reporting-bugs.rst, in favor of reporting-issues.rst, but
> > translations still need to be updated, in order to point to the
> > new file.
> >
> > Fixes: d2ce285378b0 ("docs: make reporting-issues.rst official and delete
> > reporting-bugs.rst")
> > Signed-off-by: Mauro Carvalho Chehab
>
> Well, yeah, might be the right thing to do. But FWIW: when I recently
> submitted the change that became d2ce285378b0 I actually pointed out
> that it breaks some of the translations. Back then I considered to do
> what you did with this patch, but among others got a reply from Jonathan
> who said "let the translators catch up on their own time". For details
> see this thread:
> https://lore.kernel.org/linux-doc/87h7krksvu@meer.lwn.net/
Hmm... at the e-mail you mentioned, Jon commented that:
"None of the broken references actually generate warnings"
That's actually not the case: they do generate warnings if
the Kernel is built with CONFIG_WARN_MISSING_DOCUMENTS:
Documentation/translations/zh_CN/admin-guide/reporting-issues.rst:
Documentation/admin-guide/reporting-bugs.rst
Documentation/translations/zh_CN/admin-guide/reporting-issues.rst:
Documentation/admin-guide/reporting-bugs.rst
As it will call the ./scripts/documentation-file-ref-check.
That's basically why I detected and submitted a fix ;-)
Thanks,
Mauro
[PATCH v2 15/19] docs: update rcu_dereference.rst reference
Changeset b00aedf978aa ("doc: Convert to rcu_dereference.txt to
rcu_dereference.rst")
renamed: Documentation/RCU/rcu_dereference.txt
to: Documentation/RCU/rcu_dereference.rst.
Update its cross-reference accordingly.
Fixes: b00aedf978aa ("doc: Convert to rcu_dereference.txt to
rcu_dereference.rst")
Signed-off-by: Mauro Carvalho Chehab
---
tools/memory-model/Documentation/glossary.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/memory-model/Documentation/glossary.txt
b/tools/memory-model/Documentation/glossary.txt
index b2da6365be63..6f3d16dbf467 100644
--- a/tools/memory-model/Documentation/glossary.txt
+++ b/tools/memory-model/Documentation/glossary.txt
@@ -19,7 +19,7 @@ Address Dependency: When the address of a later memory
access is computed
from the value returned by the rcu_dereference() on line 2, the
address dependency extends from that rcu_dereference() to that
"p->a". In rare cases, optimizing compilers can destroy address
-dependencies. Please see Documentation/RCU/rcu_dereference.txt
+dependencies. Please see Documentation/RCU/rcu_dereference.rst
for more information.
See also "Control Dependency" and "Data Dependency".
--
2.30.2
[PATCH v2 17/19] docs: replace transation references for reporting-bugs.rst
Changeset d2ce285378b0 ("docs: make reporting-issues.rst official and delete
reporting-bugs.rst")
dropped reporting-bugs.rst, in favor of reporting-issues.rst, but
translations still need to be updated, in order to point to the
new file.
Fixes: d2ce285378b0 ("docs: make reporting-issues.rst official and delete
reporting-bugs.rst")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/translations/it_IT/process/howto.rst| 2 +-
Documentation/translations/ja_JP/howto.rst| 2 +-
Documentation/translations/zh_CN/SecurityBugs | 2 +-
.../translations/zh_CN/admin-guide/reporting-issues.rst | 4 ++--
Documentation/translations/zh_CN/process/howto.rst| 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/translations/it_IT/process/howto.rst
b/Documentation/translations/it_IT/process/howto.rst
index 1db5a1082389..4962057f50fa 100644
--- a/Documentation/translations/it_IT/process/howto.rst
+++ b/Documentation/translations/it_IT/process/howto.rst
@@ -364,7 +364,7 @@ Per maggiori dettagli su come usare il bugzilla del kernel,
guardare:
https://bugzilla.kernel.org/page.cgi?id=faq.html
-Il file admin-guide/reporting-bugs.rst nella cartella principale del kernel
+Il file admin-guide/reporting-issues.rst nella cartella principale del kernel
fornisce un buon modello sul come segnalare un baco nel kernel, e spiega quali
informazioni sono necessarie agli sviluppatori per poter aiutare il
rintracciamento del problema.
diff --git a/Documentation/translations/ja_JP/howto.rst
b/Documentation/translations/ja_JP/howto.rst
index 73ebdab4ced7..3051ff787e69 100644
--- a/Documentation/translations/ja_JP/howto.rst
+++ b/Documentation/translations/ja_JP/howto.rst
@@ -367,7 +367,7 @@ kernel bugzilla を使うかの詳細は、以下を参照してください -
https://bugzilla.kernel.org/page.cgi?id=faq.html
メインカーネルソースディレクトリにあるファイル
-admin-guide/reporting-bugs.rstはカーネルバグらしいものについてどうレポー
+admin-guide/reporting-issues.rstはカーネルバグらしいものについてどうレポー
トするかの良いテンプレートであり、問題の追跡を助けるためにカーネル開発
者にとってどんな情報が必要なのかの詳細が書かれています。
diff --git a/Documentation/translations/zh_CN/SecurityBugs
b/Documentation/translations/zh_CN/SecurityBugs
index 2d0fffd122ce..980199d88eca 100644
--- a/Documentation/translations/zh_CN/SecurityBugs
+++ b/Documentation/translations/zh_CN/SecurityBugs
@@ -31,7 +31,7 @@ linux内核安全团队可以通过email来联系。这是
一组独立的安全工作人员，可以帮助改善漏洞报告并且公布和取消一个修复。安
全团队有可能会从部分的维护者那里引进额外的帮助来了解并且修复安全漏洞。
当遇到任何漏洞，所能提供的信息越多就越能诊断和修复。如果你不清楚什么
-是有帮助的信息，那就请重温一下admin-guide/reporting-bugs.rst文件中的概述过程。任
+是有帮助的信息，那就请重温一下admin-guide/reporting-issues.rst文件中的概述过程。任
何攻击性的代码都是非常有用的，未经报告者的同意不会被取消，除非它已经
被公布于众。
diff --git a/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
b/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
index 2805c1a03cd5..72c8e2db88c0 100644
--- a/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
+++ b/Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
@@ -19,7 +19,7 @@
.. important::
- 本文档将取代“Documentation/admin-guide/reporting-bugs.rst”。主要的工作
+ 本文档将取代“Documentation/admin-guide/reporting-issues.rst”。主要的工作
已经完成，你可以自由地按照其指示来向Linux内核开发者报告问题。但请留意，
下面的文字还需要一些润色和校审。现阶段它被合并到Linux内核源代码中，以使
这个过程更容易，并增加文本的可见性。
@@ -726,7 +726,7 @@ tar 存档包。
.. note::
FIXME: 本节文字暂时是占位符，与目前
- “Documentation/admin-guide/reporting-bugs.rst”中的旧文字非常相似。它和它
+ “Documentation/admin-guide/reporting-issues.rst”中的旧文字非常相似。它和它
所引用的文档已经过时，因此需要重新审视。因此，请将此说明视为一个求助：如
果你熟悉这个主题，请写几行适合这里的文字。或者只需向本文件的主要作者（见
导言）大致概述一下当前的情况，因为他们也许能写出一些东西来。
diff --git a/Documentation/translations/zh_CN/process/howto.rst
b/Documentation/translations/zh_CN/process/howto.rst
index ee3dee476d57..c87cd529d769 100644
--- a/Documentation/translations/zh_CN/process/howto.rst
+++ b/Documentation/translations/zh_CN/process/howto.rst
@@ -280,7 +280,7 @@ bugzilla.kernel.org是Linux内核开发者们用来跟踪内核Bug的网站。
http://test.kernel.org/bugzilla/faq.html
-内核源码主目录中的:ref:`admin-guide/reporting-bugs.rst `
+内核源码主目录中的:ref:`admin-guide/reporting-issues.rst `
文件里有一个很好的模板。它指导用户如何报告可能的内核bug以及需要提供哪些信息
来帮助内核开发者们找到问题的根源。
--
2.30.2
[PATCH v2 19/19] docs: sched-bwc.rst: fix a typo on a doc name
cgroupv2.rst -> cgroup-v2.rst Signed-off-by: Mauro Carvalho Chehab --- Documentation/scheduler/sched-bwc.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst index 845eee659199..1fc73555f5c4 100644 --- a/Documentation/scheduler/sched-bwc.rst +++ b/Documentation/scheduler/sched-bwc.rst @@ -29,7 +29,7 @@ Quota and period are managed within the cpu subsystem via cgroupfs. .. note:: The cgroupfs files described in this section are only applicable to cgroup v1. For cgroup v2, see - :ref:`Documentation/admin-guide/cgroupv2.rst `. + :ref:`Documentation/admin-guide/cgroup-v2.rst `. - cpu.cfs_quota_us: the total available run-time within a period (in microseconds) -- 2.30.2
[PATCH v2 16/19] docs: vcpu-requests.rst: fix reference for atomic ops
Changeset f0400a77ebdc ("atomic: Delete obsolete documentation")
got rid of atomic_ops.rst, pointing that this was superseded by
Documentation/atomic_*.txt.
Update its reference accordingly.
Fixes: f0400a77ebdc ("atomic: Delete obsolete documentation")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/virt/kvm/vcpu-requests.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/vcpu-requests.rst
b/Documentation/virt/kvm/vcpu-requests.rst
index 5feb3706a7ae..5f8798e7fdf8 100644
--- a/Documentation/virt/kvm/vcpu-requests.rst
+++ b/Documentation/virt/kvm/vcpu-requests.rst
@@ -302,6 +302,6 @@ VCPU returns from the call.
References
==
-.. [atomic-ops] Documentation/core-api/atomic_ops.rst
+.. [atomic-ops] Documentation/atomic_bitops.txt and Documentation/atomic_t.txt
.. [memory-barriers] Documentation/memory-barriers.txt
.. [lwn-mb] https://lwn.net/Articles/573436/
--
2.30.2
[PATCH v2 13/19] dt-bindings: power: supply: da9150: update da9150-fg.txt reference
Changeset f3332532463f ("power/supply: unify DT documentation")
renamed: Documentation/devicetree/bindings/power/da9150-fg.txt
to: Documentation/devicetree/bindings/power/supply/da9150-fg.txt.
Update its cross-reference accordingly.
Fixes: f3332532463f ("power/supply: unify DT documentation")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/mfd/da9150.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/da9150.txt
b/Documentation/devicetree/bindings/mfd/da9150.txt
index f4db2b520327..f488e23478cf 100644
--- a/Documentation/devicetree/bindings/mfd/da9150.txt
+++ b/Documentation/devicetree/bindings/mfd/da9150.txt
@@ -21,7 +21,7 @@ Required properties:
Sub-devices:
- da9150-gpadc: See
Documentation/devicetree/bindings/iio/adc/dlg,da9150-gpadc.yaml
- da9150-charger: See
Documentation/devicetree/bindings/power/supply/da9150-charger.txt
-- da9150-fg: See Documentation/devicetree/bindings/power/da9150-fg.txt
+- da9150-fg: See Documentation/devicetree/bindings/power/supply/da9150-fg.txt
Example:
--
2.30.2
[PATCH v2 07/19] dt-bindings: fix references for iio-bindings.txt
The iio-bindings.txt was converted into two files and merged
at the dt-schema git tree at:
https://github.com/devicetree-org/dt-schema
Yet, some documents still refer to the old file. Fix their
references, in order to point to the right URL.
Fixes: dba91f82d580 ("dt-bindings:iio:iio-binding.txt Drop file as content now
in dt-schema")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt | 2 +-
Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml | 5 +++--
Documentation/devicetree/bindings/input/adc-joystick.yaml| 4 +++-
.../bindings/input/touchscreen/resistive-adc-touch.txt | 5 -
Documentation/devicetree/bindings/mfd/ab8500.txt | 4 +++-
.../devicetree/bindings/power/supply/da9150-charger.txt | 2 +-
6 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
b/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
index 37f18d684f6a..4c5c3712970e 100644
--- a/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
+++ b/Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
@@ -32,7 +32,7 @@ Optional node properties:
- "#thermal-sensor-cells" Used to expose itself to thermal fw.
Read more about iio bindings at
- Documentation/devicetree/bindings/iio/iio-bindings.txt
+ https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/
Example:
ncp15wb473@0 {
diff --git a/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
b/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
index 9f414dbdae86..433a3fb55a2e 100644
--- a/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
+++ b/Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml
@@ -14,8 +14,9 @@ description: >
Industrial I/O subsystem bindings for ADC controller found in
Ingenic JZ47xx SoCs.
- ADC clients must use the format described in iio-bindings.txt, giving
- a phandle and IIO specifier pair ("io-channels") to the ADC controller.
+ ADC clients must use the format described in
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml,
+ giving a phandle and IIO specifier pair ("io-channels") to the ADC
controller.
properties:
compatible:
diff --git a/Documentation/devicetree/bindings/input/adc-joystick.yaml
b/Documentation/devicetree/bindings/input/adc-joystick.yaml
index 054406bbd22b..721878d5b7af 100644
--- a/Documentation/devicetree/bindings/input/adc-joystick.yaml
+++ b/Documentation/devicetree/bindings/input/adc-joystick.yaml
@@ -24,7 +24,9 @@ properties:
description: >
List of phandle and IIO specifier pairs.
Each pair defines one ADC channel to which a joystick axis is connected.
- See Documentation/devicetree/bindings/iio/iio-bindings.txt for details.
+ See
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+ for details.
'#address-cells':
const: 1
diff --git
a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
index fee0da12474e..af5223bb5bdd 100644
---
a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
+++
b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt
@@ -5,7 +5,10 @@ Required properties:
- compatible: must be "resistive-adc-touch"
The device must be connected to an ADC device that provides channels for
position measurement and optional pressure.
-Refer to Documentation/devicetree/bindings/iio/iio-bindings.txt for details
+Refer to
+https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+for details
+
- iio-channels: must have at least two channels connected to an ADC device.
These should correspond to the channels exposed by the ADC device and should
have the right index as the ADC device registers them. These channels
diff --git a/Documentation/devicetree/bindings/mfd/ab8500.txt
b/Documentation/devicetree/bindings/mfd/ab8500.txt
index d2a6e835c257..937b3e5505e0 100644
--- a/Documentation/devicetree/bindings/mfd/ab8500.txt
+++ b/Documentation/devicetree/bindings/mfd/ab8500.txt
@@ -72,7 +72,9 @@ Required child device properties:
pwm|regulator|rtc|sysctrl|usb]";
A few child devices require ADC channels from the GPADC node. Those follow
the
- standard bindings from iio/iio-bindings.txt and iio/adc/adc.txt
+ standard bindings from
+
https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
+ and Documentation/devicetree/bindings/iio/adc/adc.yaml
abx500-temp : io-channels "aux1" and "aux2" for measuring external
temperatures.
diff --git a/Documentation/devicetree/bi
[PATCH v2 18/19] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst
transaltions -> translations Signed-off-by: Mauro Carvalho Chehab --- Documentation/translations/zh_CN/process/8.Conclusion.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/translations/zh_CN/process/8.Conclusion.rst b/Documentation/translations/zh_CN/process/8.Conclusion.rst index 71c3e30efc6f..4707f0101964 100644 --- a/Documentation/translations/zh_CN/process/8.Conclusion.rst +++ b/Documentation/translations/zh_CN/process/8.Conclusion.rst @@ -19,7 +19,7 @@ :ref:`Documentation/translations/zh_CN/process/howto.rst ` 文件是一个重要的起点； :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst ` -和 :ref:`Documentation/transaltions/zh_CN/process/submitting-drivers.rst ` +和 :ref:`Documentation/translations/zh_CN/process/submitting-drivers.rst ` 也是所有内核开发人员都应该阅读的内容。许多内部内核API都是使用kerneldoc机制 记录的；“make htmldocs”或“make pdfdocs”可用于以HTML或PDF格式生成这些文档 （尽管某些发行版提供的tex版本会遇到内部限制，无法正确处理文档）。 -- 2.30.2
[PATCH v2 08/19] dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references
Changeset bca28426805d ("dt-bindings: iommu: mediatek: Convert IOMMU to DT
schema")
renamed: Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
to: Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml.
Update the cross-references accordingly.
Fixes: bca28426805d ("dt-bindings: iommu: mediatek: Convert IOMMU to DT schema")
Signed-off-by: Mauro Carvalho Chehab
---
.../devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +-
.../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +-
.../devicetree/bindings/media/mediatek-jpeg-encoder.txt | 2 +-
Documentation/devicetree/bindings/media/mediatek-mdp.txt| 2 +-
Documentation/devicetree/bindings/media/mediatek-vcodec.txt | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git
a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
index 93b160df3eec..fbb59c9ddda6 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
@@ -64,7 +64,7 @@ Required properties (DMA function blocks):
- larb: Should contain a phandle pointing to the local arbiter device as
defined
in
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
- iommus: Should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Optional properties (RDMA function blocks):
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
index cf60c5acc0e4..39c1028b2dfb 100644
--- a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
@@ -19,7 +19,7 @@ Required properties:
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
for details.
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Example:
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
index acfb50375b8a..5e53c6ab52d0 100644
--- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
@@ -17,7 +17,7 @@ Required properties:
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
for details.
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Example:
diff --git a/Documentation/devicetree/bindings/media/mediatek-mdp.txt
b/Documentation/devicetree/bindings/media/mediatek-mdp.txt
index f4798d04e925..caa24943da33 100644
--- a/Documentation/devicetree/bindings/media/mediatek-mdp.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-mdp.txt
@@ -25,7 +25,7 @@ Required properties (DMA function blocks, child node):
"mediatek,mt8173-mdp-wdma"
"mediatek,mt8173-mdp-wrot"
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
- mediatek,larb: must contain the local arbiters in the current Socs, see
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
diff --git a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
index 8217424fd4bd..a83ebc1a1c7f 100644
--- a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
@@ -18,7 +18,7 @@ Required properties:
"univpll_d2", "clk_cci400_sel", "vdec_sel", "vdecpll", "vencpll",
"venc_lt_sel", "vdec_bus_clk_src".
- iommus : should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
One of the two following nodes:
- mediatek,vpu : the node of the video processor unit, if using VPU.
--
2.30.2
[PATCH v2 00/19] Fix broken documentation file references
Hi Jon, As files keep being moved around and DT bindings are converted and renamed to yaml, their doc references get outdated, pointing to an invalid places. This series address those. It is based on the top of docs-next tree, and most patches here are independent from the other ones. v2: - Dropped patches that were already applied, Most of those will be following via Jonathan Cameron's iio tree; - Dropped patches that don't apply on the top of docs next. - Added some new patches fixing other breakages. PS.: I placed the dropped patches on a separate branch. I'll track them and re-submit any missing ones after -rc1. Mauro Carvalho Chehab (19): MAINTAINERS: update ste,mcde.yaml reference MAINTAINERS: update brcm,bcm-v3d.yaml reference MAINTAINERS: update fsl,dpaa2-console.yaml reference MAINTAINERS: update mtk-sd.yaml reference MAINTAINERS: update snps,dw-axi-dmac.yaml reference dt-bindings: don't use ../dir for doc references dt-bindings: fix references for iio-bindings.txt dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references dt-bindings: i3c: update i3c.yaml references dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference dt-bindings:iio:adc: update dlg,da9150-gpadc.yaml reference dt-bindings: power: supply: da9150: update da9150-charger.txt reference dt-bindings: power: supply: da9150: update da9150-fg.txt reference docs: update sysfs-platform_profile.rst reference docs: update rcu_dereference.rst reference docs: vcpu-requests.rst: fix reference for atomic ops docs: replace transation references for reporting-bugs.rst docs: translations/zh_CN: fix a typo at 8.Conclusion.rst docs: sched-bwc.rst: fix a typo on a doc name .../bindings/display/mediatek/mediatek,disp.txt | 2 +- .../devicetree/bindings/hwmon/ntc_thermistor.txt | 2 +- .../devicetree/bindings/i3c/cdns,i3c-master.txt | 6 +++--- .../bindings/i3c/snps,dw-i3c-master.txt | 6 +++--- .../devicetree/bindings/iio/adc/ingenic,adc.yaml | 5 +++-- .../devicetree/bindings/input/adc-joystick.yaml | 4 +++- .../input/touchscreen/resistive-adc-touch.txt| 5 - .../bindings/media/mediatek-jpeg-decoder.txt | 2 +- .../bindings/media/mediatek-jpeg-encoder.txt | 2 +- .../devicetree/bindings/media/mediatek-mdp.txt | 2 +- .../bindings/media/mediatek-vcodec.txt | 2 +- Documentation/devicetree/bindings/mfd/ab8500.txt | 4 +++- Documentation/devicetree/bindings/mfd/da9150.txt | 8 .../devicetree/bindings/mfd/motorola-cpcap.txt | 16 .../bindings/power/supply/da9150-charger.txt | 2 +- Documentation/scheduler/sched-bwc.rst| 2 +- .../translations/it_IT/process/howto.rst | 2 +- Documentation/translations/ja_JP/howto.rst | 2 +- Documentation/translations/zh_CN/SecurityBugs| 2 +- .../zh_CN/admin-guide/reporting-issues.rst | 4 ++-- .../translations/zh_CN/process/8.Conclusion.rst | 2 +- .../translations/zh_CN/process/howto.rst | 2 +- Documentation/virt/kvm/vcpu-requests.rst | 2 +- MAINTAINERS | 10 +- include/linux/platform_profile.h | 2 +- tools/memory-model/Documentation/glossary.txt| 2 +- 26 files changed, 54 insertions(+), 46 deletions(-) -- 2.30.2
[PATCH v2 14/19] docs: update sysfs-platform_profile.rst reference
The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
Update its cross-reference accordingly.
Fixes: a2ff95e018f1 ("ACPI: platform: Add platform profile support")
Fixes: 8e0cbf356377 ("Documentation: Add documentation for new platform_profile
sysfs attribute")
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/platform_profile.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/platform_profile.h b/include/linux/platform_profile.h
index a6329003aee7..e5cbb6841f3a 100644
--- a/include/linux/platform_profile.h
+++ b/include/linux/platform_profile.h
@@ -2,7 +2,7 @@
/*
* Platform profile sysfs interface
*
- * See Documentation/ABI/testing/sysfs-platform_profile.rst for more
+ * See Documentation/userspace-api/sysfs-platform_profile.rst for more
* information.
*/
--
2.30.2
[PATCH v2 12/19] dt-bindings: power: supply: da9150: update da9150-charger.txt reference
Changeset f3332532463f ("power/supply: unify DT documentation")
renamed: Documentation/devicetree/bindings/power/da9150-charger.txt
to: Documentation/devicetree/bindings/power/supply/da9150-charger.txt.
Update its cross-reference accordingly.
Fixes: f3332532463f ("power/supply: unify DT documentation")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/mfd/da9150.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/da9150.txt
b/Documentation/devicetree/bindings/mfd/da9150.txt
index b7afa39d6260..f4db2b520327 100644
--- a/Documentation/devicetree/bindings/mfd/da9150.txt
+++ b/Documentation/devicetree/bindings/mfd/da9150.txt
@@ -20,7 +20,7 @@ Required properties:
Sub-devices:
- da9150-gpadc: See
Documentation/devicetree/bindings/iio/adc/dlg,da9150-gpadc.yaml
-- da9150-charger: See
Documentation/devicetree/bindings/power/da9150-charger.txt
+- da9150-charger: See
Documentation/devicetree/bindings/power/supply/da9150-charger.txt
- da9150-fg: See Documentation/devicetree/bindings/power/da9150-fg.txt
Example:
--
2.30.2
[PATCH v2 06/19] dt-bindings: don't use ../dir for doc references
As documents have been renamed and moved around, their references will break, but this will be unnoticed, as the script which checks for it won't handle "../" references. So, replace them by the full patch. Signed-off-by: Mauro Carvalho Chehab --- .../input/touchscreen/resistive-adc-touch.txt| 2 +- Documentation/devicetree/bindings/mfd/da9150.txt | 8 .../devicetree/bindings/mfd/motorola-cpcap.txt | 16 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt index 51456c0e9a27..fee0da12474e 100644 --- a/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt +++ b/Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.txt @@ -5,7 +5,7 @@ Required properties: - compatible: must be "resistive-adc-touch" The device must be connected to an ADC device that provides channels for position measurement and optional pressure. -Refer to ../iio/iio-bindings.txt for details +Refer to Documentation/devicetree/bindings/iio/iio-bindings.txt for details - iio-channels: must have at least two channels connected to an ADC device. These should correspond to the channels exposed by the ADC device and should have the right index as the ADC device registers them. These channels diff --git a/Documentation/devicetree/bindings/mfd/da9150.txt b/Documentation/devicetree/bindings/mfd/da9150.txt index f09b41fbdf47..763e0b639a82 100644 --- a/Documentation/devicetree/bindings/mfd/da9150.txt +++ b/Documentation/devicetree/bindings/mfd/da9150.txt @@ -15,13 +15,13 @@ Required properties: - reg: Specifies the I2C slave address - interrupts: IRQ line info for da9150 chip. - interrupt-controller: da9150 has internal IRQs (own IRQ domain). - (See ../interrupt-controller/interrupts.txt for + (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for further information relating to interrupt properties) Sub-devices: -- da9150-gpadc: See ../iio/adc/da9150-gpadc.txt -- da9150-charger: See ../power/da9150-charger.txt -- da9150-fg: See ../power/da9150-fg.txt +- da9150-gpadc: See Documentation/devicetree/bindings/iio/adc/da9150-gpadc.txt +- da9150-charger: See Documentation/devicetree/bindings/power/da9150-charger.txt +- da9150-fg: See Documentation/devicetree/bindings/power/da9150-fg.txt Example: diff --git a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt index 5ddcc8f4febc..ebdccfb600b9 100644 --- a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt +++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt @@ -16,14 +16,14 @@ Optional subnodes: The sub-functions of CPCAP get their own node with their own compatible values, which are described in the following files: -- ../power/supply/cpcap-battery.txt -- ../power/supply/cpcap-charger.txt -- ../regulator/cpcap-regulator.txt -- ../phy/phy-cpcap-usb.txt -- ../input/cpcap-pwrbutton.txt -- ../rtc/cpcap-rtc.txt -- ../leds/leds-cpcap.txt -- ../iio/adc/cpcap-adc.txt +- Documentation/devicetree/bindings/power/supply/cpcap-battery.txt +- Documentation/devicetree/bindings/power/supply/cpcap-charger.txt +- Documentation/devicetree/bindings/regulator/cpcap-regulator.txt +- Documentation/devicetree/bindings/phy/phy-cpcap-usb.txt +- Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt +- Documentation/devicetree/bindings/rtc/cpcap-rtc.txt +- Documentation/devicetree/bindings/leds/leds-cpcap.txt +- Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt The only exception is the audio codec. Instead of a compatible value its node must be named "audio-codec". -- 2.30.2
[PATCH v2 11/19] dt-bindings:iio:adc: update dlg,da9150-gpadc.yaml reference
Changeset e13b686b18e3 ("dt-bindings:iio:adc:dlg,da9150-gpadc yaml conversion")
renamed: Documentation/devicetree/bindings/iio/adc/da9150-gpadc.txt
to: Documentation/devicetree/bindings/iio/adc/dlg,da9150-gpadc.yaml.
Update its cross-reference accordingly.
Fixes: e13b686b18e3 ("dt-bindings:iio:adc:dlg,da9150-gpadc yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/mfd/da9150.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/da9150.txt
b/Documentation/devicetree/bindings/mfd/da9150.txt
index 763e0b639a82..b7afa39d6260 100644
--- a/Documentation/devicetree/bindings/mfd/da9150.txt
+++ b/Documentation/devicetree/bindings/mfd/da9150.txt
@@ -19,7 +19,7 @@ Required properties:
further information relating to interrupt properties)
Sub-devices:
-- da9150-gpadc: See Documentation/devicetree/bindings/iio/adc/da9150-gpadc.txt
+- da9150-gpadc: See
Documentation/devicetree/bindings/iio/adc/dlg,da9150-gpadc.yaml
- da9150-charger: See
Documentation/devicetree/bindings/power/da9150-charger.txt
- da9150-fg: See Documentation/devicetree/bindings/power/da9150-fg.txt
--
2.30.2
[PATCH v2 09/19] dt-bindings: i3c: update i3c.yaml references
Changeset 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
renamed: Documentation/devicetree/bindings/i3c/i3c.txt
to: Documentation/devicetree/bindings/i3c/i3c.yaml.
Update the cross-references accordingly.
Fixes: 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
Acked-by: Rob Herring
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt | 6 +++---
.../devicetree/bindings/i3c/snps,dw-i3c-master.txt | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
b/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
index 1cf6182f888c..3716589d6999 100644
--- a/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
+++ b/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
@@ -10,19 +10,19 @@ Required properties:
- reg: I3C master registers
Mandatory properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- #address-cells: shall be set to 1
- #size-cells: shall be set to 0
Optional properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- i2c-scl-hz
- i3c-scl-hz
I3C device connected on the bus follow the generic description (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details).
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details).
Example:
diff --git a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
index 5020eb71eb8d..07f35f36085d 100644
--- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
+++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
@@ -9,19 +9,19 @@ Required properties:
- reg: Offset and length of I3C master registers
Mandatory properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- #address-cells: shall be set to 3
- #size-cells: shall be set to 0
Optional properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- i2c-scl-hz
- i3c-scl-hz
I3C device connected on the bus follow the generic description (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details).
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details).
Example:
--
2.30.2
[PATCH v2 10/19] dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference
Changeset 1ca9d1b1342d ("dt-bindings:iio:adc:motorola,cpcap-adc yaml
conversion")
renamed: Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt
to: Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml.
Update its cross-reference accordingly.
Fixes: 1ca9d1b1342d ("dt-bindings:iio:adc:motorola,cpcap-adc yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/mfd/motorola-cpcap.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
index ebdccfb600b9..b52e7a33f0f9 100644
--- a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
+++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
@@ -23,7 +23,7 @@ which are described in the following files:
- Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
- Documentation/devicetree/bindings/rtc/cpcap-rtc.txt
- Documentation/devicetree/bindings/leds/leds-cpcap.txt
-- Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt
+- Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml
The only exception is the audio codec. Instead of a compatible value its
node must be named "audio-codec".
--
2.30.2
[PATCH v2 03/19] MAINTAINERS: update fsl,dpaa2-console.yaml reference
Changeset 616fde2dd60f ("dt-bindings: misc: convert fsl,dpaa2-console from txt
to YAML")
renamed: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.txt
to: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.yaml.
Update its cross-reference accordingly.
Fixes: 616fde2dd60f ("dt-bindings: misc: convert fsl,dpaa2-console from txt to
YAML")
Reviewed-by: Laurentiu Tudor
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 16a9c89755f1..02e29e4461a5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7211,7 +7211,7 @@ M:Li Yang
L: linuxppc-...@lists.ozlabs.org
L: linux-arm-ker...@lists.infradead.org
S: Maintained
-F: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.txt
+F: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.yaml
F: Documentation/devicetree/bindings/soc/fsl/
F: drivers/soc/fsl/
F: include/linux/fsl/
--
2.30.2
[PATCH v2 04/19] MAINTAINERS: update mtk-sd.yaml reference
Changeset c626695ecd8b ("dt-bindings: mmc: Convert mtk-sd to json-schema")
renamed: Documentation/devicetree/bindings/mmc/mtk-sd.txt
to: Documentation/devicetree/bindings/mmc/mtk-sd.yaml.
Update its cross-reference accordingly.
Fixes: c626695ecd8b ("dt-bindings: mmc: Convert mtk-sd to json-schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 02e29e4461a5..735d48d18a57 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11293,7 +11293,7 @@ F: drivers/media/platform/mtk-vpu/
MEDIATEK MMC/SD/SDIO DRIVER
M: Chaotian Jing
S: Maintained
-F: Documentation/devicetree/bindings/mmc/mtk-sd.txt
+F: Documentation/devicetree/bindings/mmc/mtk-sd.yaml
F: drivers/mmc/host/mtk-sd.c
MEDIATEK MT76 WIRELESS LAN DRIVER
--
2.30.2
[PATCH v2 02/19] MAINTAINERS: update brcm,bcm-v3d.yaml reference
Changeset cb18a7979a35 ("dt-bindings: gpu: Convert v3d to json-schema")
renamed: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt
to: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml.
Update its cross-reference accordingly.
Fixes: cb18a7979a35 ("dt-bindings: gpu: Convert v3d to json-schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 92e5039b90ba..16a9c89755f1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6069,7 +6069,7 @@ DRM DRIVERS FOR V3D
M: Eric Anholt
S: Supported
T: git git://anongit.freedesktop.org/drm/drm-misc
-F: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt
+F: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
F: drivers/gpu/drm/v3d/
F: include/uapi/drm/v3d_drm.h
--
2.30.2
[PATCH v2 05/19] MAINTAINERS: update snps,dw-axi-dmac.yaml reference
Changeset 8c70fb7e0a0a ("dt-bindings: dma: Add YAML schemas for dw-axi-dmac")
renamed: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.txt
to: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml.
Update its cross-reference accordingly.
Fixes: 8c70fb7e0a0a ("dt-bindings: dma: Add YAML schemas for dw-axi-dmac")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 735d48d18a57..dbc123bde7dd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17285,7 +17285,7 @@ F: drivers/spi/spi-dw*
SYNOPSYS DESIGNWARE AXI DMAC DRIVER
M: Eugeniy Paltsev
S: Maintained
-F: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.txt
+F: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
F: drivers/dma/dw-axi-dmac/
SYNOPSYS DESIGNWARE DMAC DRIVER
--
2.30.2
[PATCH v2 01/19] MAINTAINERS: update ste,mcde.yaml reference
Changeset 2abb0b994db5 ("dt-bindings: display: mcde: Convert to YAML schema")
renamed: Documentation/devicetree/bindings/display/ste,mcde.txt
to: Documentation/devicetree/bindings/display/ste,mcde.yaml.
Update its cross-reference accordingly.
Fixes: 2abb0b994db5 ("dt-bindings: display: mcde: Convert to YAML schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 03b2096a5f8f..92e5039b90ba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5794,7 +5794,7 @@ DRM DRIVER FOR ST-ERICSSON MCDE
M: Linus Walleij
S: Maintained
T: git git://anongit.freedesktop.org/drm/drm-misc
-F: Documentation/devicetree/bindings/display/ste,mcde.txt
+F: Documentation/devicetree/bindings/display/ste,mcde.yaml
F: drivers/gpu/drm/mcde/
DRM DRIVER FOR TDFX VIDEO CARDS
--
2.30.2
Re: [PATCH 29/32] docs: dt: update writing-schema.rst references
Em Tue, 6 Apr 2021 10:04:57 -0500
Rob Herring escreveu:
> On Thu, Apr 1, 2021 at 7:17 AM Mauro Carvalho Chehab
> wrote:
> >
> > Changeset b83db5b84900 ("docs: dt: Group DT docs into relevant
> > sub-sections")
> > renamed: Documentation/devicetree/writing-schema.rst
> > to: Documentation/devicetree/bindings/writing-schema.rst.
> >
> > Update the cross-references accordingly.
> >
> > Fixes: b83db5b84900 ("docs: dt: Group DT docs into relevant sub-sections")
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
> > scripts/checkpatch.pl| 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/submitting-patches.rst
> > b/Documentation/devicetree/bindings/submitting-patches.rst
> > index ee4feb53f8d0..104fa8fb2c17 100644
> > --- a/Documentation/devicetree/bindings/submitting-patches.rst
> > +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> > @@ -25,7 +25,7 @@ I. For patch submitters
> >
> > make dt_binding_check
> >
> > - See Documentation/devicetree/writing-schema.rst for more details about
> > + See Documentation/devicetree/bindings/writing-schema.rst for more
> > details about
>
> We should make this a rSt link instead.
It shouldn't be needed, as Documentation/sphinx/automarkup.py has a rule
which converts Documentation/* into a cross reference using this
regex:
RE_doc = re.compile(r'(\bDocumentation/)?((\.\./)*[\w\-/]+)\.(rst|txt)')
Thanks,
Mauro
Re: [PATCH v2 1/5] iio: Documentation: update definitions for bufferY and scan_elements
Em Wed, 17 Feb 2021 10:34:34 +0200 Alexandru Ardelean escreveu: > Since the new change to the IIO buffer infrastructure, the buffer/ and > scan_elements/ directories have been merged into bufferY/ to have some > attributes available per-buffer. > > This change updates the ABI docs to reflect this change. > > The hwfifo attributes are not updated, as for now these should be used > via the legacy buffer/ directory until they are moved into core. > > Signed-off-by: Alexandru Ardelean > --- > Documentation/ABI/testing/sysfs-bus-iio | 85 + > 1 file changed, 85 insertions(+) > > diff --git a/Documentation/ABI/testing/sysfs-bus-iio > b/Documentation/ABI/testing/sysfs-bus-iio > index d957f5da5c04..f2a72d7fbacb 100644 > --- a/Documentation/ABI/testing/sysfs-bus-iio > +++ b/Documentation/ABI/testing/sysfs-bus-iio > @@ -1118,12 +1118,16 @@ Description: > > What:/sys/bus/iio/devices/iio:deviceX/buffer/length > KernelVersion: 2.6.35 > +What:/sys/bus/iio/devices/iio:deviceX/bufferY/length > +KernelVersion: 5.11 > Contact: linux-...@vger.kernel.org > Description: > Number of scans contained by the buffer. The ABI parser doesn't like things like this: $ ./scripts/get_abi.pl validate Warning: file Documentation/ABI/testing/sysfs-bus-iio#1167: What '/sys/bus/iio/devices/iio:deviceX/buffer/length' doesn't have a description The main reason is that all properties, including KernelVersion, Contact and Description are associated to a group of properties. To be frank, for me that don't work with IIO, the above ABI description doesn't sound clear. I mean, what's the difference between /sys/bus/iio/devices/iio:deviceX/buffer/length and /sys/bus/iio/devices/iio:deviceX/bufferY/length? If the intention is to tell that: /sys/bus/iio/devices/iio:deviceX/buffer/length was obsoleted by: /sys/bus/iio/devices/iio:deviceX/bufferY/length IMO, the right thing would be to move the deprecated definition to Documentation/ABI/obsolete/ If, on the other hand, both are completely identical and non-obsoleted, why to have both APIs? Or did you just missed adding a different description for the new ABI symbols, but this was dropped due to some merge conflict? Thanks, Mauro
Re: [PATCH v3 1/2] audit: document /proc/PID/loginuid
Em Thu, 18 Mar 2021 15:19:10 -0400
Richard Guy Briggs escreveu:
> Describe the /proc/PID/loginuid interface in Documentation/ABI/stable that
> was added 2005-02-01 by commit 1e2d1492e178 ("[PATCH] audit: handle
> loginuid through proc")
>
> Signed-off-by: Richard Guy Briggs
> ---
> Documentation/ABI/stable/procfs-audit_loginuid | 15 +++
> 1 file changed, 15 insertions(+)
> create mode 100644 Documentation/ABI/stable/procfs-audit_loginuid
>
> diff --git a/Documentation/ABI/stable/procfs-audit_loginuid
> b/Documentation/ABI/stable/procfs-audit_loginuid
> new file mode 100644
> index ..e7c100b9ab18
> --- /dev/null
> +++ b/Documentation/ABI/stable/procfs-audit_loginuid
> @@ -0,0 +1,15 @@
> +What:Audit Login UID
> +Date:2005-02-01
> +KernelVersion: 2.6.11-rc2 1e2d1492e178 ("[PATCH] audit: handle
> loginuid through proc")
> +Contact: linux-au...@redhat.com
> +Format: %u
The ABI definition doesn't include a "Format:" symbol. See:
Documentation/ABI/README
For the valid ones.
This change causes a warning at the ABI parser:
$ ./scripts/get_abi.pl validate
Warning: file Documentation/ABI/stable/procfs-audit_loginuid#5:
tag 'contact' is invalid. Line
Format: %u
Warning: file Documentation/ABI/stable/procfs-audit_loginuid#21:
tag 'contact' is invalid. Line
Format: %u
You should either drop it or add it to the parser and to the README
file, if the ABI maintainers are ok with such new field.
Thanks,
Mauro
[PATCH 06/32] MAINTAINERS: update dpot-dac.yaml reference
Changeset 06d2ff6fe11e ("dt-bindings:iio:dac:dpot-dac: yaml conversion.")
renamed: Documentation/devicetree/bindings/iio/dac/dpot-dac.txt
to: Documentation/devicetree/bindings/iio/dac/dpot-dac.yaml.
Update its cross-reference accordingly.
Fixes: 06d2ff6fe11e ("dt-bindings:iio:dac:dpot-dac: yaml conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1985d75d59c7..52ce258fab37 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8753,7 +8753,7 @@ M:Peter Rosin
L: linux-...@vger.kernel.org
S: Maintained
F: Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac
-F: Documentation/devicetree/bindings/iio/dac/dpot-dac.txt
+F: Documentation/devicetree/bindings/iio/dac/dpot-dac.yaml
F: drivers/iio/dac/dpot-dac.c
IIO ENVELOPE DETECTOR
--
2.30.2
[PATCH 12/32] MAINTAINERS: update lego,ev3-battery.yaml reference
Changeset 3004e581d92a ("dt-bindings: power: supply: lego-ev3-battery: Convert
to DT schema format")
renamed: Documentation/devicetree/bindings/power/supply/lego_ev3_battery.txt
to: Documentation/devicetree/bindings/power/supply/lego,ev3-battery.yaml.
Update its cross-reference accordingly.
Fixes: 3004e581d92a ("dt-bindings: power: supply: lego-ev3-battery: Convert to
DT schema format")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index ce675a0b3819..b16830f54226 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10173,7 +10173,7 @@ F: drivers/misc/eeprom/eeprom.c
LEGO MINDSTORMS EV3
R: David Lechner
S: Maintained
-F: Documentation/devicetree/bindings/power/supply/lego_ev3_battery.txt
+F: Documentation/devicetree/bindings/power/supply/lego,ev3-battery.yaml
F: arch/arm/boot/dts/da850-lego-ev3.dts
F: drivers/power/supply/lego_ev3_battery.c
--
2.30.2
[PATCH 02/32] MAINTAINERS: update ste,mcde.yaml reference
Changeset 2abb0b994db5 ("dt-bindings: display: mcde: Convert to YAML schema")
renamed: Documentation/devicetree/bindings/display/ste,mcde.txt
to: Documentation/devicetree/bindings/display/ste,mcde.yaml.
Update its cross-reference accordingly.
Fixes: 2abb0b994db5 ("dt-bindings: display: mcde: Convert to YAML schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4c8a926ef201..069cbf59da86 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5857,7 +5857,7 @@ DRM DRIVER FOR ST-ERICSSON MCDE
M: Linus Walleij
S: Maintained
T: git git://anongit.freedesktop.org/drm/drm-misc
-F: Documentation/devicetree/bindings/display/ste,mcde.txt
+F: Documentation/devicetree/bindings/display/ste,mcde.yaml
F: drivers/gpu/drm/mcde/
DRM DRIVER FOR TDFX VIDEO CARDS
--
2.30.2
[PATCH 03/32] MAINTAINERS: update brcm,bcm-v3d.yaml reference
Changeset cb18a7979a35 ("dt-bindings: gpu: Convert v3d to json-schema")
renamed: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt
to: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml.
Update its cross-reference accordingly.
Fixes: cb18a7979a35 ("dt-bindings: gpu: Convert v3d to json-schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 069cbf59da86..53c66a6908b7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6131,7 +6131,7 @@ DRM DRIVERS FOR V3D
M: Eric Anholt
S: Supported
T: git git://anongit.freedesktop.org/drm/drm-misc
-F: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt
+F: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
F: drivers/gpu/drm/v3d/
F: include/uapi/drm/v3d_drm.h
--
2.30.2
[PATCH 04/32] MAINTAINERS: update fsl,dpaa2-console.yaml reference
Changeset 616fde2dd60f ("dt-bindings: misc: convert fsl,dpaa2-console from txt
to YAML")
renamed: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.txt
to: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.yaml.
Update its cross-reference accordingly.
Fixes: 616fde2dd60f ("dt-bindings: misc: convert fsl,dpaa2-console from txt to
YAML")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 53c66a6908b7..de9637196526 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7274,7 +7274,7 @@ M:Li Yang
L: linuxppc-...@lists.ozlabs.org
L: linux-arm-ker...@lists.infradead.org
S: Maintained
-F: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.txt
+F: Documentation/devicetree/bindings/misc/fsl,dpaa2-console.yaml
F: Documentation/devicetree/bindings/soc/fsl/
F: drivers/soc/fsl/
F: include/linux/fsl/
--
2.30.2
[PATCH 05/32] MAINTAINERS: update st,hts221.yaml reference
Changeset 9a6ac3138258 ("dt-bindings:iio:humidity:st,hts221 yaml conversion.")
renamed: Documentation/devicetree/bindings/iio/humidity/hts221.txt
to: Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml.
Update its cross-reference accordingly.
Fixes: 9a6ac3138258 ("dt-bindings:iio:humidity:st,hts221 yaml conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index de9637196526..1985d75d59c7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8287,7 +8287,7 @@ M:Lorenzo Bianconi
L: linux-...@vger.kernel.org
S: Maintained
W: http://www.st.com/
-F: Documentation/devicetree/bindings/iio/humidity/hts221.txt
+F: Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
F: drivers/iio/humidity/hts221*
HUAWEI ETHERNET DRIVER
--
2.30.2
[PATCH 00/32] Fix broken documentation file references
Each patch on this series can be applied independently. They fix broken file references. Most of them are due to DT binding renames, but there are also other unrelated changes. This series is based on next-20210401. Mauro Carvalho Chehab (32): MAINTAINERS: update adi,ad5758.yaml reference MAINTAINERS: update ste,mcde.yaml reference MAINTAINERS: update brcm,bcm-v3d.yaml reference MAINTAINERS: update fsl,dpaa2-console.yaml reference MAINTAINERS: update st,hts221.yaml reference MAINTAINERS: update dpot-dac.yaml reference MAINTAINERS: update envelope-detector.yaml reference MAINTAINERS: update current-sense-amplifier.yaml reference MAINTAINERS: update current-sense-shunt.yaml reference MAINTAINERS: update voltage-divider.yaml reference MAINTAINERS: update invensense,mpu3050.yaml reference MAINTAINERS: update lego,ev3-battery.yaml reference MAINTAINERS: update marvell,armada-3700-utmi-phy.yaml reference MAINTAINERS: update mtk-sd.yaml reference MAINTAINERS: update atmel,sama5d2-adc.yaml reference MAINTAINERS: update pni,rm3100.yaml reference MAINTAINERS: update renesas,rcar-gyroadc.yaml reference MAINTAINERS: update st,lsm6dsx.yaml reference MAINTAINERS: update st,vl53l0x.yaml reference MAINTAINERS: update snps,dw-axi-dmac.yaml reference MAINTAINERS: update ti,dac7612.yaml reference MAINTAINERS: update nxp,imx8-jpeg.yaml reference MAINTAINERS: update ovti,ov2680.yaml reference MAINTAINERS: update imi,rdacm2x-gmsl.yaml reference dt-bindings:iio:dac: update microchip,mcp4725.yaml reference dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references dt-bindings: i3c: update i3c.yaml references dt-bindings: power: update battery.yaml reference docs: dt: update writing-schema.rst references Documentation: net: dsa: update configuration.rst reference Documentation: update sysfs-platform_profile.rst reference pinctrl: update pin-control.rst references .../display/mediatek/mediatek,disp.txt| 2 +- .../bindings/i3c/cdns,i3c-master.txt | 6 +-- .../bindings/i3c/snps,dw-i3c-master.txt | 6 +-- .../bindings/media/mediatek-jpeg-decoder.txt | 2 +- .../bindings/media/mediatek-jpeg-encoder.txt | 2 +- .../bindings/media/mediatek-mdp.txt | 2 +- .../bindings/media/mediatek-vcodec.txt| 2 +- .../bindings/submitting-patches.rst | 2 +- Documentation/filesystems/cifs/cifsd.rst | 2 +- Documentation/power/power_supply_class.rst| 2 +- MAINTAINERS | 48 +-- include/linux/device.h| 2 +- include/linux/iio/dac/mcp4725.h | 2 +- include/linux/mfd/madera/pdata.h | 2 +- include/linux/pinctrl/pinconf-generic.h | 2 +- include/linux/platform_profile.h | 2 +- scripts/checkpatch.pl | 2 +- 17 files changed, 44 insertions(+), 44 deletions(-) -- 2.30.2
[PATCH 18/32] MAINTAINERS: update st,lsm6dsx.yaml reference
Changeset 7a2cf8e91390 ("dt-bindings:iio:imu:st,lsm6dsx: txt to yaml
conversion")
renamed: Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt
to: Documentation/devicetree/bindings/iio/imu/st,lsm6dsx.yaml.
Update its cross-reference accordingly.
Fixes: 7a2cf8e91390 ("dt-bindings:iio:imu:st,lsm6dsx: txt to yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 97763e68b8e3..54c469933f66 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17142,7 +17142,7 @@ M: Lorenzo Bianconi
L: linux-...@vger.kernel.org
S: Maintained
W: http://www.st.com/
-F: Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt
+F: Documentation/devicetree/bindings/iio/imu/st,lsm6dsx.yaml
F: drivers/iio/imu/st_lsm6dsx/
ST MIPID02 CSI-2 TO PARALLEL BRIDGE DRIVER
--
2.30.2
[PATCH 24/32] MAINTAINERS: update imi,rdacm2x-gmsl.yaml reference
The file name: Documentation/devicetree/bindings/media/i2c/rdacm2x-gmsl.yaml
should be, instead:
Documentation/devicetree/bindings/media/i2c/imi,rdacm2x-gmsl.yaml.
Update its cross-reference accordingly.
Fixes: 34009bffc1c6 ("media: i2c: Add RDACM20 driver")
Fixes: e9f817689789 ("media: dt-bindings: media: i2c: Add bindings for IMI
RDACM2x")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1644b6e9697c..b405ee71f730 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15258,7 +15258,7 @@ M: Laurent Pinchart
M: Niklas Söderlund
L: linux-me...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/media/i2c/rdacm2x-gmsl.yaml
+F: Documentation/devicetree/bindings/media/i2c/imi,rdacm2x-gmsl.yaml
F: drivers/media/i2c/max9271.c
F: drivers/media/i2c/max9271.h
F: drivers/media/i2c/rdacm21.c
--
2.30.2
[PATCH 19/32] MAINTAINERS: update st,vl53l0x.yaml reference
Changeset b4be8bd1c6a2 ("dt-bindings:iio:proximity:st,vl53l0x yaml conversion")
renamed: Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
to: Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml.
Update its cross-reference accordingly.
Fixes: b4be8bd1c6a2 ("dt-bindings:iio:proximity:st,vl53l0x yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 54c469933f66..d6708b3fdbd9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17171,7 +17171,7 @@ ST VL53L0X ToF RANGER(I2C) IIO DRIVER
M: Song Qiang
L: linux-...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
+F: Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml
F: drivers/iio/proximity/vl53l0x-i2c.c
STABLE BRANCH
--
2.30.2
[PATCH 20/32] MAINTAINERS: update snps,dw-axi-dmac.yaml reference
Changeset 8c70fb7e0a0a ("dt-bindings: dma: Add YAML schemas for dw-axi-dmac")
renamed: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.txt
to: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml.
Update its cross-reference accordingly.
Fixes: 8c70fb7e0a0a ("dt-bindings: dma: Add YAML schemas for dw-axi-dmac")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d6708b3fdbd9..6b0a6f251e6b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17491,7 +17491,7 @@ F: drivers/spi/spi-dw*
SYNOPSYS DESIGNWARE AXI DMAC DRIVER
M: Eugeniy Paltsev
S: Maintained
-F: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.txt
+F: Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
F: drivers/dma/dw-axi-dmac/
SYNOPSYS DESIGNWARE DMAC DRIVER
--
2.30.2
[PATCH 21/32] MAINTAINERS: update ti,dac7612.yaml reference
Changeset 8b74e06b0f4d ("dt-bindings:iio:dac:ti,dac7612 yaml conversion")
renamed: Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt
to: Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml.
Update its cross-reference accordingly.
Fixes: 8b74e06b0f4d ("dt-bindings:iio:dac:ti,dac7612 yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6b0a6f251e6b..2f63ebd2cfc8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17907,7 +17907,7 @@ TEXAS INSTRUMENTS' DAC7612 DAC DRIVER
M: Ricardo Ribalda
L: linux-...@vger.kernel.org
S: Supported
-F: Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt
+F: Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml
F: drivers/iio/dac/ti-dac7612.c
TEXAS INSTRUMENTS DMA DRIVERS
--
2.30.2
[PATCH 27/32] dt-bindings: i3c: update i3c.yaml references
Changeset 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
renamed: Documentation/devicetree/bindings/i3c/i3c.txt
to: Documentation/devicetree/bindings/i3c/i3c.yaml.
Update the cross-references accordingly.
Fixes: 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt | 6 +++---
.../devicetree/bindings/i3c/snps,dw-i3c-master.txt | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
b/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
index 1cf6182f888c..3716589d6999 100644
--- a/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
+++ b/Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
@@ -10,19 +10,19 @@ Required properties:
- reg: I3C master registers
Mandatory properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- #address-cells: shall be set to 1
- #size-cells: shall be set to 0
Optional properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- i2c-scl-hz
- i3c-scl-hz
I3C device connected on the bus follow the generic description (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details).
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details).
Example:
diff --git a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
index 5020eb71eb8d..07f35f36085d 100644
--- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
+++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.txt
@@ -9,19 +9,19 @@ Required properties:
- reg: Offset and length of I3C master registers
Mandatory properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- #address-cells: shall be set to 3
- #size-cells: shall be set to 0
Optional properties defined by the generic binding (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details):
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details):
- i2c-scl-hz
- i3c-scl-hz
I3C device connected on the bus follow the generic description (see
-Documentation/devicetree/bindings/i3c/i3c.txt for more details).
+Documentation/devicetree/bindings/i3c/i3c.yaml for more details).
Example:
--
2.30.2
[PATCH 31/32] Documentation: update sysfs-platform_profile.rst reference
The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
Update its cross-reference accordingly.
Fixes: a2ff95e018f1 ("ACPI: platform: Add platform profile support")
Fixes: 8e0cbf356377 ("Documentation: Add documentation for new platform_profile
sysfs attribute")
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/platform_profile.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/platform_profile.h b/include/linux/platform_profile.h
index a6329003aee7..e5cbb6841f3a 100644
--- a/include/linux/platform_profile.h
+++ b/include/linux/platform_profile.h
@@ -2,7 +2,7 @@
/*
* Platform profile sysfs interface
*
- * See Documentation/ABI/testing/sysfs-platform_profile.rst for more
+ * See Documentation/userspace-api/sysfs-platform_profile.rst for more
* information.
*/
--
2.30.2
[PATCH 17/32] MAINTAINERS: update renesas,rcar-gyroadc.yaml reference
Changeset 8c41245872e2 ("dt-bindings:iio:adc:renesas,rcar-gyroadc: txt to yaml
conversion.")
renamed: Documentation/devicetree/bindings/iio/adc/renesas,gyroadc.txt
to: Documentation/devicetree/bindings/iio/adc/renesas,rcar-gyroadc.yaml.
Update its cross-reference accordingly.
Fixes: 8c41245872e2 ("dt-bindings:iio:adc:renesas,rcar-gyroadc: txt to yaml
conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 636b29fd2d4b..97763e68b8e3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15437,7 +15437,7 @@ RENESAS R-CAR GYROADC DRIVER
M: Marek Vasut
L: linux-...@vger.kernel.org
S: Supported
-F: Documentation/devicetree/bindings/iio/adc/renesas,gyroadc.txt
+F: Documentation/devicetree/bindings/iio/adc/renesas,rcar-gyroadc.yaml
F: drivers/iio/adc/rcar-gyroadc.c
RENESAS R-CAR I2C DRIVERS
--
2.30.2
[PATCH 26/32] dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references
Changeset bca28426805d ("dt-bindings: iommu: mediatek: Convert IOMMU to DT
schema")
renamed: Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
to: Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml.
Update the cross-references accordingly.
Fixes: bca28426805d ("dt-bindings: iommu: mediatek: Convert IOMMU to DT schema")
Signed-off-by: Mauro Carvalho Chehab
---
.../devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +-
.../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +-
.../devicetree/bindings/media/mediatek-jpeg-encoder.txt | 2 +-
Documentation/devicetree/bindings/media/mediatek-mdp.txt| 2 +-
Documentation/devicetree/bindings/media/mediatek-vcodec.txt | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git
a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
index 93b160df3eec..fbb59c9ddda6 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
@@ -64,7 +64,7 @@ Required properties (DMA function blocks):
- larb: Should contain a phandle pointing to the local arbiter device as
defined
in
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
- iommus: Should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Optional properties (RDMA function blocks):
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
index cf60c5acc0e4..39c1028b2dfb 100644
--- a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt
@@ -19,7 +19,7 @@ Required properties:
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
for details.
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Example:
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
index acfb50375b8a..5e53c6ab52d0 100644
--- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
@@ -17,7 +17,7 @@ Required properties:
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
for details.
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
Example:
diff --git a/Documentation/devicetree/bindings/media/mediatek-mdp.txt
b/Documentation/devicetree/bindings/media/mediatek-mdp.txt
index f4798d04e925..caa24943da33 100644
--- a/Documentation/devicetree/bindings/media/mediatek-mdp.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-mdp.txt
@@ -25,7 +25,7 @@ Required properties (DMA function blocks, child node):
"mediatek,mt8173-mdp-wdma"
"mediatek,mt8173-mdp-wrot"
- iommus: should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
- mediatek,larb: must contain the local arbiters in the current Socs, see
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
diff --git a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
index 8217424fd4bd..a83ebc1a1c7f 100644
--- a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
+++ b/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
@@ -18,7 +18,7 @@ Required properties:
"univpll_d2", "clk_cci400_sel", "vdec_sel", "vdecpll", "vencpll",
"venc_lt_sel", "vdec_bus_clk_src".
- iommus : should point to the respective IOMMU block with master port as
- argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
for details.
One of the two following nodes:
- mediatek,vpu : the node of the video processor unit, if using VPU.
--
2.30.2
[PATCH 32/32] pinctrl: update pin-control.rst references
Changeset 5513b411ea5b ("Documentation: rename pinctl to pin-control")
renamed: Documentation/driver-api/pinctl.rst
to: Documentation/driver-api/pin-control.rst.
Update the cross-references accordingly.
Fixes: 5513b411ea5b ("Documentation: rename pinctl to pin-control")
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/device.h | 2 +-
include/linux/mfd/madera/pdata.h| 2 +-
include/linux/pinctrl/pinconf-generic.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/device.h b/include/linux/device.h
index 38a2071cf776..d1183cfdc8fb 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -399,7 +399,7 @@ struct dev_links_info {
* along with subsystem-level and driver-level callbacks.
* @em_pd: device's energy model performance domain
* @pins: For device pin management.
- * See Documentation/driver-api/pinctl.rst for details.
+ * See Documentation/driver-api/pin-control.rst for details.
* @msi_list: Hosts MSI descriptors
* @msi_domain: The generic MSI domain this device is using.
* @numa_node: NUMA node this device is close to.
diff --git a/include/linux/mfd/madera/pdata.h b/include/linux/mfd/madera/pdata.h
index 601cbbc10370..32e3470708ed 100644
--- a/include/linux/mfd/madera/pdata.h
+++ b/include/linux/mfd/madera/pdata.h
@@ -31,7 +31,7 @@ struct pinctrl_map;
* @irq_flags: Mode for primary IRQ (defaults to active low)
* @gpio_base: Base GPIO number
* @gpio_configs: Array of GPIO configurations (See
- * Documentation/driver-api/pinctl.rst)
+ * Documentation/driver-api/pin-control.rst)
* @n_gpio_configs: Number of entries in gpio_configs
* @gpsw: General purpose switch mode setting. Depends on the external
* hardware connected to the switch. (See the SW1_MODE field
diff --git a/include/linux/pinctrl/pinconf-generic.h
b/include/linux/pinctrl/pinconf-generic.h
index 6aeb711f7cd1..fdcd773adba3 100644
--- a/include/linux/pinctrl/pinconf-generic.h
+++ b/include/linux/pinctrl/pinconf-generic.h
@@ -88,7 +88,7 @@ struct pinctrl_map;
* it.
* @PIN_CONFIG_OUTPUT: this will configure the pin as an output and drive a
* value on the line. Use argument 1 to indicate high level, argument 0 to
- * indicate low level. (Please see Documentation/driver-api/pinctl.rst,
+ * indicate low level. (Please see
Documentation/driver-api/pin-control.rst,
* section "GPIO mode pitfalls" for a discussion around this parameter.)
* @PIN_CONFIG_POWER_SOURCE: if the pin can select between different power
* supplies, the argument to this parameter (on a custom format) tells
--
2.30.2
[PATCH 13/32] MAINTAINERS: update marvell,armada-3700-utmi-phy.yaml reference
Changeset 6569d8386388 ("dt-bindings: phy: convert phy-mvebu-utmi to YAML
schema")
renamed: Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
to: Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml.
Update its cross-reference accordingly.
Fixes: 6569d8386388 ("dt-bindings: phy: convert phy-mvebu-utmi to YAML schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b16830f54226..17bd389b7985 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10774,7 +10774,7 @@ MARVELL ARMADA 3700 PHY DRIVERS
M: Miquel Raynal
S: Maintained
F: Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt
-F: Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
+F: Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml
F: drivers/phy/marvell/phy-mvebu-a3700-comphy.c
F: drivers/phy/marvell/phy-mvebu-a3700-utmi.c
--
2.30.2
[PATCH 25/32] dt-bindings:iio:dac: update microchip,mcp4725.yaml reference
Changeset 6ced946a4bba ("dt-bindings:iio:dac:microchip,mcp4725 yaml conversion")
renamed: Documentation/devicetree/bindings/iio/dac/mcp4725.txt
to: Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml.
Update its cross-reference accordingly.
Fixes: 6ced946a4bba ("dt-bindings:iio:dac:microchip,mcp4725 yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/iio/dac/mcp4725.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/iio/dac/mcp4725.h b/include/linux/iio/dac/mcp4725.h
index e9801c8d49c0..1f7e53c506b6 100644
--- a/include/linux/iio/dac/mcp4725.h
+++ b/include/linux/iio/dac/mcp4725.h
@@ -15,7 +15,7 @@
* @vref_buffered: Controls buffering of the external reference voltage.
*
* Vref related settings are available only on MCP4756. See
- * Documentation/devicetree/bindings/iio/dac/mcp4725.txt for more information.
+ * Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml for more
information.
*/
struct mcp4725_platform_data {
bool use_vref;
--
2.30.2
[PATCH 16/32] MAINTAINERS: update pni,rm3100.yaml reference
Changeset f383069be33e ("dt-bindings:iio:magnetometer:pni,rm3100: txt to yaml
conversion.")
renamed: Documentation/devicetree/bindings/iio/magnetometer/pni,rm3100.txt
to: Documentation/devicetree/bindings/iio/magnetometer/pni,rm3100.yaml.
Update its cross-reference accordingly.
Fixes: f383069be33e ("dt-bindings:iio:magnetometer:pni,rm3100: txt to yaml
conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 89ed435ca6c3..636b29fd2d4b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14445,7 +14445,7 @@ PNI RM3100 IIO DRIVER
M: Song Qiang
L: linux-...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/iio/magnetometer/pni,rm3100.txt
+F: Documentation/devicetree/bindings/iio/magnetometer/pni,rm3100.yaml
F: drivers/iio/magnetometer/rm3100*
PNP SUPPORT
--
2.30.2
[PATCH 15/32] MAINTAINERS: update atmel,sama5d2-adc.yaml reference
Changeset 58ff1b519753 ("dt-bindings:iio:adc:atmel,sama5d2-adc: txt to yaml
conversion")
renamed: Documentation/devicetree/bindings/iio/adc/at91-sama5d2_adc.txt
to: Documentation/devicetree/bindings/iio/adc/atmel,sama5d2-adc.yaml.
Update its cross-reference accordingly.
Fixes: 58ff1b519753 ("dt-bindings:iio:adc:atmel,sama5d2-adc: txt to yaml
conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 576d1bcabb20..89ed435ca6c3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11930,7 +11930,7 @@ MICROCHIP SAMA5D2-COMPATIBLE ADC DRIVER
M: Eugen Hristev
L: linux-...@vger.kernel.org
S: Supported
-F: Documentation/devicetree/bindings/iio/adc/at91-sama5d2_adc.txt
+F: Documentation/devicetree/bindings/iio/adc/atmel,sama5d2-adc.yaml
F: drivers/iio/adc/at91-sama5d2_adc.c
F: include/dt-bindings/iio/adc/at91-sama5d2_adc.h
--
2.30.2
[PATCH 11/32] MAINTAINERS: update invensense,mpu3050.yaml reference
Changeset 749787477ae4 ("dt-bindings:iio:gyro:invensense,mpu3050: txt to yaml
format conversion.")
renamed: Documentation/devicetree/bindings/iio/gyroscope/invensense,mpu3050.txt
to: Documentation/devicetree/bindings/iio/gyroscope/invensense,mpu3050.yaml.
Update its cross-reference accordingly.
Fixes: 749787477ae4 ("dt-bindings:iio:gyro:invensense,mpu3050: txt to yaml
format conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5110f47ebf85..ce675a0b3819 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9414,7 +9414,7 @@ INVENSENSE MPU-3050 GYROSCOPE DRIVER
M: Linus Walleij
L: linux-...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/iio/gyroscope/invensense,mpu3050.txt
+F: Documentation/devicetree/bindings/iio/gyroscope/invensense,mpu3050.yaml
F: drivers/iio/gyro/mpu3050*
IOC3 ETHERNET DRIVER
--
2.30.2
[PATCH 08/32] MAINTAINERS: update current-sense-amplifier.yaml reference
Changeset fbac26b9ad21 ("dt-bindings:iio:afe:current-sense-amplifier: txt to
yaml conversion.")
renamed: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.txt
to: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.yaml.
Update its cross-reference accordingly.
Fixes: fbac26b9ad21 ("dt-bindings:iio:afe:current-sense-amplifier: txt to yaml
conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 82220a72eba2..c7168833da8f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8795,7 +8795,7 @@ IIO UNIT CONVERTER
M: Peter Rosin
L: linux-...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.txt
+F: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.yaml
F: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.txt
F: Documentation/devicetree/bindings/iio/afe/voltage-divider.txt
F: drivers/iio/afe/iio-rescale.c
--
2.30.2
[PATCH 22/32] MAINTAINERS: update nxp,imx8-jpeg.yaml reference
The file name: Documentation/devicetree/bindings/media/imx8-jpeg.yaml
should be, instead: Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml.
Update its cross-reference accordingly.
Fixes: be157db0a3d8 ("media: Add maintainer for IMX jpeg v4l2 driver")
Fixes: b16ed1e66008 ("media: dt-bindings: Add bindings for i.MX8QXP/QM JPEG
driver")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2f63ebd2cfc8..0ee42d68a269 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13073,7 +13073,7 @@ M: Mirela Rabulea
R: NXP Linux Team
L: linux-me...@vger.kernel.org
S: Maintained
-F: Documentation/devicetree/bindings/media/imx8-jpeg.yaml
+F: Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml
F: drivers/media/platform/imx-jpeg
NZXT-KRAKEN2 HARDWARE MONITORING DRIVER
--
2.30.2
[PATCH 10/32] MAINTAINERS: update voltage-divider.yaml reference
Changeset 6f633bc91ac1 ("dt-bindings:iio:afe:voltage-divider: txt to yaml
conversion")
renamed: Documentation/devicetree/bindings/iio/afe/voltage-divider.txt
to: Documentation/devicetree/bindings/iio/afe/voltage-divider.yaml.
Update its cross-reference accordingly.
Fixes: 6f633bc91ac1 ("dt-bindings:iio:afe:voltage-divider: txt to yaml
conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 71950316c736..5110f47ebf85 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8797,7 +8797,7 @@ L:linux-...@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.yaml
F: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.yaml
-F: Documentation/devicetree/bindings/iio/afe/voltage-divider.txt
+F: Documentation/devicetree/bindings/iio/afe/voltage-divider.yaml
F: drivers/iio/afe/iio-rescale.c
IKANOS/ADI EAGLE ADSL USB DRIVER
--
2.30.2
[PATCH 09/32] MAINTAINERS: update current-sense-shunt.yaml reference
Changeset ce66e52b6c16 ("dt-bindings:iio:afe:current-sense-shunt: txt to yaml
conversion.")
renamed: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.txt
to: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.yaml.
Update its cross-reference accordingly.
Fixes: ce66e52b6c16 ("dt-bindings:iio:afe:current-sense-shunt: txt to yaml
conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index c7168833da8f..71950316c736 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8796,7 +8796,7 @@ M:Peter Rosin
L: linux-...@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.yaml
-F: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.txt
+F: Documentation/devicetree/bindings/iio/afe/current-sense-shunt.yaml
F: Documentation/devicetree/bindings/iio/afe/voltage-divider.txt
F: drivers/iio/afe/iio-rescale.c
--
2.30.2
[PATCH 23/32] MAINTAINERS: update ovti,ov2680.yaml reference
The file name: Documentation/devicetree/bindings/media/i2c/ov2680.yaml
should be, instead:
Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml.
Update its cross-reference accordingly.
Fixes: 57226cd8c8bf ("media: dt-bindings: ov2680: convert bindings to yaml")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0ee42d68a269..1644b6e9697c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13351,7 +13351,7 @@ M: Rui Miguel Silva
L: linux-me...@vger.kernel.org
S: Maintained
T: git git://linuxtv.org/media_tree.git
-F: Documentation/devicetree/bindings/media/i2c/ov2680.yaml
+F: Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
F: drivers/media/i2c/ov2680.c
OMNIVISION OV2685 SENSOR DRIVER
--
2.30.2
[PATCH 28/32] dt-bindings: power: update battery.yaml reference
Changesets: 70c23e62d20c ("dt-bindings: power: supply: Fix remaining
battery.txt links")
and: 471dec8023d1 ("dt-bindings: power: Convert battery.txt to battery.yaml")
renamed: Documentation/devicetree/bindings/power/supply/battery.txt
to: Documentation/devicetree/bindings/power/supply/battery.yaml.
Update its cross-reference accordingly.
Fixes: 70c23e62d20c ("dt-bindings: power: supply: Fix remaining battery.txt
links")
Fixes: 471dec8023d1 ("dt-bindings: power: Convert battery.txt to battery.yaml")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/power/power_supply_class.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/power_supply_class.rst
b/Documentation/power/power_supply_class.rst
index 7b8c42f8b1de..c04fabee0a58 100644
--- a/Documentation/power/power_supply_class.rst
+++ b/Documentation/power/power_supply_class.rst
@@ -233,7 +233,7 @@ Devicetree battery characteristics
~~
Drivers should call power_supply_get_battery_info() to obtain battery
characteristics from a devicetree battery node, defined in
-Documentation/devicetree/bindings/power/supply/battery.txt. This is
+Documentation/devicetree/bindings/power/supply/battery.yaml. This is
implemented in drivers/power/supply/bq27xxx_battery.c.
Properties in struct power_supply_battery_info and their counterparts in the
--
2.30.2
[PATCH 01/32] MAINTAINERS: update adi,ad5758.yaml reference
Changeset 1e6536ee349b ("dt-bindings:iio:dac:adi,ad5758 yaml conversion")
renamed: Documentation/devicetree/bindings/iio/dac/ad5758.txt
to: Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml.
Update its cross-reference accordingly.
Fixes: 1e6536ee349b ("dt-bindings:iio:dac:adi,ad5758 yaml conversion")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 38d823d72e52..4c8a926ef201 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1141,7 +1141,7 @@ W:
http://ez.analog.com/community/linux-device-drivers
F: Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
F: Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
F: Documentation/devicetree/bindings/iio/*/adi,*
-F: Documentation/devicetree/bindings/iio/dac/ad5758.txt
+F: Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml
F: drivers/iio/*/ad*
F: drivers/iio/adc/ltc249*
F: drivers/iio/amplifiers/hmc425a.c
--
2.30.2
[PATCH 14/32] MAINTAINERS: update mtk-sd.yaml reference
Changeset c626695ecd8b ("dt-bindings: mmc: Convert mtk-sd to json-schema")
renamed: Documentation/devicetree/bindings/mmc/mtk-sd.txt
to: Documentation/devicetree/bindings/mmc/mtk-sd.yaml.
Update its cross-reference accordingly.
Fixes: c626695ecd8b ("dt-bindings: mmc: Convert mtk-sd to json-schema")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 17bd389b7985..576d1bcabb20 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11410,7 +11410,7 @@ F: drivers/media/platform/mtk-vpu/
MEDIATEK MMC/SD/SDIO DRIVER
M: Chaotian Jing
S: Maintained
-F: Documentation/devicetree/bindings/mmc/mtk-sd.txt
+F: Documentation/devicetree/bindings/mmc/mtk-sd.yaml
F: drivers/mmc/host/mtk-sd.c
MEDIATEK MT76 WIRELESS LAN DRIVER
--
2.30.2
[PATCH 30/32] Documentation: net: dsa: update configuration.rst reference
The file name: Documentation/configuration.txt
should be, instead: Documentation/networking/dsa/configuration.rst.
Update its cross-reference accordingly.
Fixes: 75b8988dfe83 ("cifsd: add server handler for central processing and
tranport layers")
Fixes: 58dd7a8d9d02 ("Documentation: net: dsa: Describe DSA switch
configuration")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/filesystems/cifs/cifsd.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/cifs/cifsd.rst
b/Documentation/filesystems/cifs/cifsd.rst
index 48ae58f2a53c..082a839535e7 100644
--- a/Documentation/filesystems/cifs/cifsd.rst
+++ b/Documentation/filesystems/cifs/cifsd.rst
@@ -114,7 +114,7 @@ How to run
# ksmbd.adduser -a
3. Create /etc/ksmbd/smb.conf file, add SMB share in smb.conf file
- - Refer smb.conf.example and Documentation/configuration.txt
+ - Refer smb.conf.example and
Documentation/networking/dsa/configuration.rst
in ksmbd-tools
4. Insert ksmbd.ko module
--
2.30.2
[PATCH 29/32] docs: dt: update writing-schema.rst references
Changeset b83db5b84900 ("docs: dt: Group DT docs into relevant sub-sections")
renamed: Documentation/devicetree/writing-schema.rst
to: Documentation/devicetree/bindings/writing-schema.rst.
Update the cross-references accordingly.
Fixes: b83db5b84900 ("docs: dt: Group DT docs into relevant sub-sections")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
scripts/checkpatch.pl| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/submitting-patches.rst
b/Documentation/devicetree/bindings/submitting-patches.rst
index ee4feb53f8d0..104fa8fb2c17 100644
--- a/Documentation/devicetree/bindings/submitting-patches.rst
+++ b/Documentation/devicetree/bindings/submitting-patches.rst
@@ -25,7 +25,7 @@ I. For patch submitters
make dt_binding_check
- See Documentation/devicetree/writing-schema.rst for more details about
+ See Documentation/devicetree/bindings/writing-schema.rst for more details
about
schema and tools setup.
3) DT binding files should be dual licensed. The preferred license tag is
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 4dbda85fd7e5..3870c8a01987 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3245,7 +3245,7 @@ sub process {
($line =~ /^new file mode\s*\d+\s*$/) &&
($realfile =~
m@^Documentation/devicetree/bindings/.*\.txt$@)) {
WARN("DT_SCHEMA_BINDING_PATCH",
-"DT bindings should be in DT schema format. See:
Documentation/devicetree/writing-schema.rst\n");
+"DT bindings should be in DT schema format. See:
Documentation/devicetree/bindings/writing-schema.rst\n");
}
# Check for wrappage within a valid hunk of the file
--
2.30.2
[PATCH 07/32] MAINTAINERS: update envelope-detector.yaml reference
Changeset 66a6dcc20e63 ("dt-bindings:iio:adc:envelope-detector: txt to yaml
conversion.")
renamed: Documentation/devicetree/bindings/iio/adc/envelope-detector.txt
to: Documentation/devicetree/bindings/iio/adc/envelope-detector.yaml.
Update its cross-reference accordingly.
Fixes: 66a6dcc20e63 ("dt-bindings:iio:adc:envelope-detector: txt to yaml
conversion.")
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 52ce258fab37..82220a72eba2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8761,7 +8761,7 @@ M:Peter Rosin
L: linux-...@vger.kernel.org
S: Maintained
F: Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector
-F: Documentation/devicetree/bindings/iio/adc/envelope-detector.txt
+F: Documentation/devicetree/bindings/iio/adc/envelope-detector.yaml
F: drivers/iio/adc/envelope-detector.c
IIO MULTIPLEXER
--
2.30.2
Re: [PATCH 30/32] Documentation: net: dsa: update configuration.rst reference
Em Thu, 1 Apr 2021 14:41:15 +0200
Andrew Lunn escreveu:
> On Thu, Apr 01, 2021 at 02:17:50PM +0200, Mauro Carvalho Chehab wrote:
> > The file name: Documentation/configuration.txt
> > should be, instead: Documentation/networking/dsa/configuration.rst.
> >
> > Update its cross-reference accordingly.
> >
> > Fixes: 75b8988dfe83 ("cifsd: add server handler for central processing and
> > tranport layers")
> > Fixes: 58dd7a8d9d02 ("Documentation: net: dsa: Describe DSA switch
> > configuration")
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > Documentation/filesystems/cifs/cifsd.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/filesystems/cifs/cifsd.rst
> > b/Documentation/filesystems/cifs/cifsd.rst
> > index 48ae58f2a53c..082a839535e7 100644
> > --- a/Documentation/filesystems/cifs/cifsd.rst
> > +++ b/Documentation/filesystems/cifs/cifsd.rst
> > @@ -114,7 +114,7 @@ How to run
> > # ksmbd.adduser -a
> >
> > 3. Create /etc/ksmbd/smb.conf file, add SMB share in smb.conf file
> > - - Refer smb.conf.example and Documentation/configuration.txt
> > + - Refer smb.conf.example and
> > Documentation/networking/dsa/configuration.rst
> > in ksmbd-tools
>
> Hi Mauro
>
> This looks wrong. There is no relationship between SMB and DSA. I
> suspect you are looking for some other configuration.txt
Thanks for reviewing it.
I'll drop the patch from my series.
After re-reading cifsd.rst, I suspect that it is actually trying to
refer to:
https://github.com/cifsd-team/ksmbd-tools/blob/master/Documentation/configuration.txt
and not to a local file.
So, IMO, the right thing to do is to apply the enclosed patch instead.
Thanks,
Mauro
[PATCH] docs: cifsd: change the reference to configuration.txt
Changeset 75b8988dfe83 ("cifsd: add server handler for central processing and
tranport layers")
added documentation for cifsd. There, it points to a file
named:
Documentation/configuration.txt
This confuses Kernel scripts, as they think that this is a
document within the Kernel tree, instead of a file from
some other place.
Replace it by an hyperlink to the ksmbd-tools tree, in order
to avoid false-positives.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/Documentation/filesystems/cifs/cifsd.rst
b/Documentation/filesystems/cifs/cifsd.rst
index 48ae58f2a53c..a6ab85e68252 100644
--- a/Documentation/filesystems/cifs/cifsd.rst
+++ b/Documentation/filesystems/cifs/cifsd.rst
@@ -114,8 +114,8 @@ How to run
# ksmbd.adduser -a
3. Create /etc/ksmbd/smb.conf file, add SMB share in smb.conf file
- - Refer smb.conf.example and Documentation/configuration.txt
- in ksmbd-tools
+ - Refer smb.conf.example and
+
https://github.com/cifsd-team/ksmbd-tools/blob/master/Documentation/configuration.txt
4. Insert ksmbd.ko module
Re: [PATCH v2] of: Fix kerneldoc output formatting
Em Fri, 26 Mar 2021 13:26:06 -0600
Rob Herring escreveu:
> The indentation of the kerneldoc comments affects the output formatting.
> Leading tabs in particular don't work, sections need to be indented
> under the section header, and several code blocks are reformatted.
>
> Cc: Frank Rowand
> Cc: Mauro Carvalho Chehab
Reviewed-by: Mauro Carvalho Chehab
> Signed-off-by: Rob Herring
> ---
> v2:
> - Updated the example code blocks to use 'Example::' which depends (for
> nice output) on Mauro's fix.
>
> The rest of the series is here[1].
>
> [1] https://lore.kernel.org/r/20210325164713.1296407-1-r...@kernel.org/
>
> drivers/of/base.c | 275 +++---
> drivers/of/fdt.c | 9 +-
> 2 files changed, 141 insertions(+), 143 deletions(-)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 457d1ec27300..a64c093d30ef 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -651,11 +651,11 @@ bool of_device_is_big_endian(const struct device_node
> *device)
> EXPORT_SYMBOL(of_device_is_big_endian);
>
> /**
> - * of_get_parent - Get a node's parent if any
> - * @node: Node to get parent
> + * of_get_parent - Get a node's parent if any
> + * @node:Node to get parent
> *
> - * Returns a node pointer with refcount incremented, use
> - * of_node_put() on it when done.
> + * Return: A node pointer with refcount incremented, use
> + * of_node_put() on it when done.
> */
> struct device_node *of_get_parent(const struct device_node *node)
> {
> @@ -673,15 +673,15 @@ struct device_node *of_get_parent(const struct
> device_node *node)
> EXPORT_SYMBOL(of_get_parent);
>
> /**
> - * of_get_next_parent - Iterate to a node's parent
> - * @node: Node to get parent of
> + * of_get_next_parent - Iterate to a node's parent
> + * @node:Node to get parent of
> *
> - * This is like of_get_parent() except that it drops the
> - * refcount on the passed node, making it suitable for iterating
> - * through a node's parents.
> + * This is like of_get_parent() except that it drops the
> + * refcount on the passed node, making it suitable for iterating
> + * through a node's parents.
> *
> - * Returns a node pointer with refcount incremented, use
> - * of_node_put() on it when done.
> + * Return: A node pointer with refcount incremented, use
> + * of_node_put() on it when done.
> */
> struct device_node *of_get_next_parent(struct device_node *node)
> {
> @@ -719,13 +719,13 @@ static struct device_node *__of_get_next_child(const
> struct device_node *node,
>child = __of_get_next_child(parent, child))
>
> /**
> - * of_get_next_child - Iterate a node childs
> - * @node: parent node
> - * @prev: previous child of the parent node, or NULL to get first
> + * of_get_next_child - Iterate a node childs
> + * @node:parent node
> + * @prev:previous child of the parent node, or NULL to get first
> *
> - * Returns a node pointer with refcount incremented, use of_node_put() on
> - * it when done. Returns NULL when prev is the last child. Decrements the
> - * refcount of prev.
> + * Return: A node pointer with refcount incremented, use of_node_put() on
> + * it when done. Returns NULL when prev is the last child. Decrements the
> + * refcount of prev.
> */
> struct device_node *of_get_next_child(const struct device_node *node,
> struct device_node *prev)
> @@ -741,12 +741,12 @@ struct device_node *of_get_next_child(const struct
> device_node *node,
> EXPORT_SYMBOL(of_get_next_child);
>
> /**
> - * of_get_next_available_child - Find the next available child node
> - * @node: parent node
> - * @prev: previous child of the parent node, or NULL to get first
> + * of_get_next_available_child - Find the next available child node
> + * @node:parent node
> + * @prev:previous child of the parent node, or NULL to get first
> *
> - * This function is like of_get_next_child(), except that it
> - * automatically skips any disabled nodes (i.e. status = "disabled").
> + * This function is like of_get_next_child(), except that it
> + * automatically skips any disabled nodes (i.e. status = "disabled").
> */
> struct device_node *of_get_next_available_child(const struct device_node
> *node,
> struct device_node *prev)
> @@ -772,12 +772,12 @@ struct device_node *of_get_next_available_child(const
> struct device_node *node,
> EXPORT_SYMBOL(of_get_next_available_child);
>
> /**
> - * of_get_next_cpu_node - Iterate on cpu nodes
> - * @prev: previous child of the /cpus node, or NULL to get first
&g
Re: [PATCH v2 04/11] PCI: dwc: pcie-kirin: add support for Kirin 970 PCIe controller
Em Fri, 26 Mar 2021 14:21:02 +0530 Manivannan Sadhasivam escreveu: > On Fri, Mar 26, 2021 at 09:39:36AM +0100, Mauro Carvalho Chehab wrote: > > Em Wed, 3 Feb 2021 08:34:21 -0600 > > Rob Herring escreveu: > > > > > On Wed, Feb 3, 2021 at 1:02 AM Mauro Carvalho Chehab > > > wrote: > > > > > > > > From: Manivannan Sadhasivam > > > > > > > > Add support for HiSilicon Kirin 970 (hi3670) SoC PCIe controller, based > > > > on Synopsys DesignWare PCIe controller IP. > > > > > > > > [mchehab+hua...@kernel.org: fix merge conflicts] > > > > Signed-off-by: Manivannan Sadhasivam > > > > Signed-off-by: Mauro Carvalho Chehab > > > > --- > > > > drivers/pci/controller/dwc/pcie-kirin.c | 723 +++- > > > > 1 file changed, 707 insertions(+), 16 deletions(-) > > > > > > > > diff --git a/drivers/pci/controller/dwc/pcie-kirin.c > > > > b/drivers/pci/controller/dwc/pcie-kirin.c > > > > index 026fd1e42a55..5925d2b345a8 100644 > > > > --- a/drivers/pci/controller/dwc/pcie-kirin.c > > > > +++ b/drivers/pci/controller/dwc/pcie-kirin.c > > > > @@ -29,6 +29,7 @@ > > > > > [...] > > > > This looks like it is almost all phy related. I think it should all be > > > moved to a separate phy driver. Yes, we have some other PCI drivers > > > controlling their phys directly where the phy registers are > > > intermingled with the PCI host registers, but I think those either > > > predate the phy subsystem or are really simple. I also have a dream to > > > move all the phy control to the DWC core code. > > > > Please notice that this patch was not written by me, but, instead, > > by Mannivannan. So, I can't change it. > > Feel free to move the PHY pieces to a separate PHY driver as suggested. > My driver code was merely WIP one and I don't have any objection to > change the patch. > > I'd be happy if you add my Co-developed tag to the PCIe driver patch with > the SoB ofc. Ok. > > What I can certainly do is to > > write a separate patch at the end of this series moving the Kirin 970 > > phy to a separate driver. Would this be accepted? > > > > Ah, please don't do that. I know that you've already followed the same > process for other HiSi drivers but that looks messy IMO. The problem is related to licensing issues and US export regulations. By preserving the patches from the original authors, I played safe. > > > Btw, what should be done with the Kirin 960 PHY code that it is > > already embedded on this driver, and whose some of the DT properties > > are for its phy layer? > > > > You might need to create a PHY driver for both 960 and 970. I don't see > any harm there. But please make sure you test the patches on both boards. Testing on Kirin 960 will be harder. Well, I can get my hands on one such board, but right now I don't have any M.2 device I can spare with, in order to test. This will also break DT backward compatibility, as, for instance, the PERST# gpio seems to be part of the Kirin 960 PHY, as Kirin 970 has different PERST# logic: on Kirin 970, there's one PERST# GPIO per PCIe device. So, before starting such change, I need to know if DT maintainers are OK with that. Thanks, Mauro
Re: [PATCH v2 04/11] PCI: dwc: pcie-kirin: add support for Kirin 970 PCIe controller
Em Wed, 3 Feb 2021 08:34:21 -0600 Rob Herring escreveu: > On Wed, Feb 3, 2021 at 1:02 AM Mauro Carvalho Chehab > wrote: > > > > From: Manivannan Sadhasivam > > > > Add support for HiSilicon Kirin 970 (hi3670) SoC PCIe controller, based > > on Synopsys DesignWare PCIe controller IP. > > > > [mchehab+hua...@kernel.org: fix merge conflicts] > > Signed-off-by: Manivannan Sadhasivam > > Signed-off-by: Mauro Carvalho Chehab > > --- > > drivers/pci/controller/dwc/pcie-kirin.c | 723 +++- > > 1 file changed, 707 insertions(+), 16 deletions(-) > > > > diff --git a/drivers/pci/controller/dwc/pcie-kirin.c > > b/drivers/pci/controller/dwc/pcie-kirin.c > > index 026fd1e42a55..5925d2b345a8 100644 > > --- a/drivers/pci/controller/dwc/pcie-kirin.c > > +++ b/drivers/pci/controller/dwc/pcie-kirin.c > > @@ -29,6 +29,7 @@ > > #define to_kirin_pcie(x) dev_get_drvdata((x)->dev) > > > > #define REF_CLK_FREQ 1 > > +#define AXI_CLK_FREQ 20750 > > > > /* PCIe ELBI registers */ > > #define SOC_PCIECTRL_CTRL0_ADDR0x000 > > @@ -60,6 +61,65 @@ > > #define PCIE_DEBOUNCE_PARAM0xF0F400 > > #define PCIE_OE_BYPASS (0x3 << 28) > > > > +/* PCIe CTRL registers */ > > +#define SOC_PCIECTRL_CTRL0_ADDR 0x000 > > +#define SOC_PCIECTRL_CTRL1_ADDR 0x004 > > +#define SOC_PCIECTRL_CTRL7_ADDR 0x01c > > +#define SOC_PCIECTRL_CTRL12_ADDR 0x030 > > +#define SOC_PCIECTRL_CTRL20_ADDR 0x050 > > +#define SOC_PCIECTRL_CTRL21_ADDR 0x054 > > +#define SOC_PCIECTRL_STATE0_ADDR 0x400 > > + > > +/* PCIe PHY registers */ > > +#define SOC_PCIEPHY_CTRL0_ADDR0x000 > > +#define SOC_PCIEPHY_CTRL1_ADDR0x004 > > +#define SOC_PCIEPHY_CTRL2_ADDR0x008 > > +#define SOC_PCIEPHY_CTRL3_ADDR0x00c > > +#define SOC_PCIEPHY_CTRL38_ADDR 0x0098 > > +#define SOC_PCIEPHY_STATE0_ADDR 0x400 > > + > > +#define PCIE_LINKUP_ENABLE(0x8020) > > +#define PCIE_ELBI_SLV_DBI_ENABLE (0x1 << 21) > > +#define PCIE_LTSSM_ENABLE_BIT (0x1 << 11) > > +#define PCIEPHY_RESET_BIT (0x1 << 17) > > +#define PCIEPHY_PIPE_LINE0_RESET_BIT (0x1 << 19) > > + > > +#define PORT_MSI_CTRL_ADDR0x820 > > +#define PORT_MSI_CTRL_UPPER_ADDR 0x824 > > +#define PORT_MSI_CTRL_INT0_ENABLE 0x828 > > These are common DWC 'port logic' registers. I think the core DWC > should handle them if not already. > > > + > > +#define EYEPARAM_NOCFG 0x > > +#define RAWLANEN_DIG_PCS_XF_TX_OVRD_IN_1 0x3001 > > +#define SUP_DIG_LVL_OVRD_IN 0xf > > +#define LANEN_DIG_ASIC_TX_OVRD_IN_1 0x1002 > > +#define LANEN_DIG_ASIC_TX_OVRD_IN_2 0x1003 > > + > > +/* kirin970 pciephy register */ > > +#define SOC_PCIEPHY_MMC1PLL_CTRL1 0xc04 > > +#define SOC_PCIEPHY_MMC1PLL_CTRL16 0xC40 > > +#define SOC_PCIEPHY_MMC1PLL_CTRL17 0xC44 > > +#define SOC_PCIEPHY_MMC1PLL_CTRL20 0xC50 > > +#define SOC_PCIEPHY_MMC1PLL_CTRL21 0xC54 > > +#define SOC_PCIEPHY_MMC1PLL_STAT0 0xE00 > > This looks like it is almost all phy related. I think it should all be > moved to a separate phy driver. Yes, we have some other PCI drivers > controlling their phys directly where the phy registers are > intermingled with the PCI host registers, but I think those either > predate the phy subsystem or are really simple. I also have a dream to > move all the phy control to the DWC core code. Please notice that this patch was not written by me, but, instead, by Mannivannan. So, I can't change it. What I can certainly do is to write a separate patch at the end of this series moving the Kirin 970 phy to a separate driver. Would this be accepted? Btw, what should be done with the Kirin 960 PHY code that it is already embedded on this driver, and whose some of the DT properties are for its phy layer? Thanks, Mauro
Re: [PATCH v2 0/7] Fix some issues at get_abi.pl script
Em Thu, 25 Mar 2021 13:01:14 -0600 Jonathan Corbet escreveu: > Mauro Carvalho Chehab writes: > > > This series replace this patch: > > https://lore.kernel.org/linux-doc/20210324191722.08d35...@coco.lan/T/#t > > > > It turns that there were multiple bugs at the get_abi.pl code that > > create cross-references. > > > > Patches 1 to 6 fix those issues, and should apply cleanly on the top of > > the docs tree (although I tested against next-20210323). > > > > Patch 7 is optional, and independent from the other patches. It is meant > > to be applied against akpm's tree. It makes the description (IMHO) > > clearer, while producing cross references for the two mentioned symbols. > > So perhaps this is the best solution to the problem, but I must confess > to not being entirely happy with it. get_abi.pl is becoming another > unreadable perlpile like kerneldoc, and this makes it worse. Doing RST > parsing there seems particularly unwelcome. Nah, it is not that complex ;-) It has 628 lines of code; kernel-doc has 2488. It is 1/4 the size of kernel-doc :-D Btw, 20 lines can be removed from it, if we drop support for --no-rst-source. I almost dropped it this time :-) Ah, the entire code that outputs the rst description and does the xref has just 34 lines (with 5 lines with comments and 5 blank lines). It is not much, and some cleanups could be done to make it a little shorter. Most of the script complexity is actually at the parsing part. The thing is that the ABI files are somewhat free-style: some files don't strictly follow the format, which requires some extra steps in order to cope with some "soft" violations, as well as to report problems when the violation is more severe. > Should the cross-reference generation, it now occurs to me, be done in > the automarkup module instead? Then there's no need to interpret RST, > and we'd get cross-references throughout the kernel docs rather than in > just the ABI stuff. Am I completely out to lunch here? Yes, I guess we can move the Xref code to automarkup some day, that is if we can ensure that get_abi.pl will run before automarkup. There's currently an issue, though. We need first to get rid of those duplicated symbols: Warning: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:0 Documentation/ABI/testing/sysfs-bus-iio:395 Warning: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:1 Documentation/ABI/testing/sysfs-bus-iio:396 Warning: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:2 Documentation/ABI/testing/sysfs-bus-iio:397 Warning: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:3 Documentation/ABI/testing/sysfs-bus-iio:398 Warning: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:4 Documentation/ABI/testing/sysfs-bus-iio:399 Warning: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-icm42600:5 Documentation/ABI/testing/sysfs-bus-iio:400 Warning: /sys/bus/iio/devices/iio:deviceX/in_count0_preset is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-timer-stm32:100 Documentation/ABI/testing/sysfs-bus-iio-lptimer-stm32:0 Warning: /sys/bus/iio/devices/iio:deviceX/in_count_quadrature_mode_available is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-counter-104-quad-8:2 Documentation/ABI/testing/sysfs-bus-iio-lptimer-stm32:8 Warning: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371:0 Documentation/ABI/testing/sysfs-bus-iio:600 Warning: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371:36 Documentation/ABI/testing/sysfs-bus-iio:589 Warning: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als:43 Documentation/ABI/testing/sysfs-bus-iio-health-afe440x:38 Warning: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc2010:0 Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc100x:0 Warning: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw_available is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc2010:1 Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc100x:1 Warning: /sys/bu
Re: [PATCH v5 4/7] mfd: hi6421-spmi-pmic: move driver from staging
Em Thu, 25 Mar 2021 16:36:41 +
Lee Jones escreveu:
> On Thu, 25 Mar 2021, Mauro Carvalho Chehab wrote:
>
> > This driver is ready for mainstream. So, move it out of staging.
> >
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > .../mfd}/hisilicon,hi6421-spmi-pmic.yaml | 0
> > MAINTAINERS| 7 +++
> > drivers/mfd/Kconfig| 16
> > drivers/mfd/Makefile | 1 +
> > .../hikey9xx => mfd}/hi6421-spmi-pmic.c| 0
> > drivers/staging/hikey9xx/Kconfig | 18 --
> > drivers/staging/hikey9xx/Makefile | 1 -
> > 7 files changed, 24 insertions(+), 19 deletions(-)
> > rename {drivers/staging/hikey9xx =>
> > Documentation/devicetree/bindings/mfd}/hisilicon,hi6421-spmi-pmic.yaml
> > (100%)
> > rename drivers/{staging/hikey9xx => mfd}/hi6421-spmi-pmic.c (100%)
>
> Could you please resend this with out using the -M flag.
>
> I can't review a driver I can't see.
Sure! Resent.
Regards,
Mauro
[PATCH] kernel-doc: better handle '::' sequences
Right now, if one of the following headers end with a '::', the kernel-doc script will do the wrong thing: description|context|returns?|notes?|examples? The real issue is with examples, as people could try to write something like: example:: /* Some C code */ and this won't be properly evaluated. So, improve the regex to not catch '\w+::' regex for the above identifiers. Signed-off-by: Mauro Carvalho Chehab --- scripts/kernel-doc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/kernel-doc b/scripts/kernel-doc index cb92d0e1e932..0ecd71477a16 100755 --- a/scripts/kernel-doc +++ b/scripts/kernel-doc @@ -392,7 +392,7 @@ my $doc_com_body = '\s*\* ?'; my $doc_decl = $doc_com . '(\w+)'; # @params and a strictly limited set of supported section names my $doc_sect = $doc_com . - '\s*(\@[.\w]+|\@\.\.\.|description|context|returns?|notes?|examples?)\s*:(.*)'; + '\s*(\@[.\w]+|\@\.\.\.|description|context|returns?|notes?|examples?)\s*:([^:]*)$'; my $doc_content = $doc_com_body . '(.*)'; my $doc_block = $doc_com . 'DOC:\s*(.*)?'; my $doc_inline_start = '^\s*/\*\*\s*$'; -- 2.30.2
[PATCH v5 (RESEND) 4/7] mfd: hi6421-spmi-pmic: move driver from staging
This driver is ready for mainstream. So, move it out of staging.
Signed-off-by: Mauro Carvalho Chehab
---
.../mfd/hisilicon,hi6421-spmi-pmic.yaml | 135
MAINTAINERS | 7 +
drivers/mfd/Kconfig | 16 +
drivers/mfd/Makefile | 1 +
drivers/mfd/hi6421-spmi-pmic.c| 297 ++
drivers/staging/hikey9xx/Kconfig | 18 --
drivers/staging/hikey9xx/Makefile | 1 -
drivers/staging/hikey9xx/hi6421-spmi-pmic.c | 297 --
.../hikey9xx/hisilicon,hi6421-spmi-pmic.yaml | 135
9 files changed, 456 insertions(+), 451 deletions(-)
create mode 100644
Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
create mode 100644 drivers/mfd/hi6421-spmi-pmic.c
delete mode 100644 drivers/staging/hikey9xx/hi6421-spmi-pmic.c
delete mode 100644 drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml
diff --git
a/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
b/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
new file mode 100644
index ..3b23ad56b31a
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
@@ -0,0 +1,135 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mfd/hisilicon,hi6421-spmi-pmic.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HiSilicon 6421v600 SPMI PMIC
+
+maintainers:
+ - Mauro Carvalho Chehab
+
+description: |
+ HiSilicon 6421v600 should be connected inside a MIPI System Power Management
+ (SPMI) bus. It provides interrupts and power supply.
+
+ The GPIO and interrupt settings are represented as part of the top-level PMIC
+ node.
+
+ The SPMI controller part is provided by
+ drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml.
+
+properties:
+ $nodename:
+pattern: "pmic@[0-9a-f]"
+
+ compatible:
+const: hisilicon,hi6421v600-spmi
+
+ reg:
+maxItems: 1
+
+ '#interrupt-cells':
+const: 2
+
+ interrupt-controller:
+description:
+ Identify that the PMIC is capable of behaving as an interrupt controller.
+
+ gpios:
+maxItems: 1
+
+ regulators:
+type: object
+
+properties:
+ '#address-cells':
+const: 1
+
+ '#size-cells':
+const: 0
+
+patternProperties:
+ '^ldo[0-9]+@[0-9a-f]$':
+type: object
+
+$ref: "/schemas/regulator/regulator.yaml#"
+
+required:
+ - compatible
+ - reg
+ - regulators
+
+additionalProperties: false
+
+examples:
+ - |
+/* pmic properties */
+
+pmic: pmic@0 {
+ compatible = "hisilicon,hi6421-spmi";
+ reg = <0 0>;
+
+ #interrupt-cells = <2>;
+ interrupt-controller;
+ gpios = < 0 0>;
+
+ regulators {
+#address-cells = <1>;
+#size-cells = <0>;
+
+ldo3: LDO3 {
+ regulator-name = "ldo3";
+ regulator-min-microvolt = <150>;
+ regulator-max-microvolt = <200>;
+ regulator-boot-on;
+};
+
+ldo4: LDO4 {
+ regulator-name = "ldo4";
+ regulator-min-microvolt = <1725000>;
+ regulator-max-microvolt = <190>;
+ regulator-boot-on;
+};
+
+ldo9: LDO9 {
+ regulator-name = "ldo9";
+ regulator-min-microvolt = <175>;
+ regulator-max-microvolt = <330>;
+ regulator-boot-on;
+};
+
+ldo15: LDO15 {
+ regulator-name = "ldo15";
+ regulator-min-microvolt = <180>;
+ regulator-max-microvolt = <300>;
+ regulator-always-on;
+};
+
+ldo16: LDO16 {
+ regulator-name = "ldo16";
+ regulator-min-microvolt = <180>;
+ regulator-max-microvolt = <300>;
+ regulator-boot-on;
+};
+
+ldo17: LDO17 {
+ regulator-name = "ldo17";
+ regulator-min-microvolt = <250>;
+ regulator-max-microvolt = <330>;
+};
+
+ldo33: LDO33 {
+ regulator-name = "ldo33";
+ regulator-min-microvolt = <250>;
+ regulator-max-microvolt = <330>;
+ regulator-boot-on;
+};
+
+ldo34: LDO34 {
+ regulator-name = "ldo34";
+ regulator-min-microvolt = <260>;
+ regulator-max-microvolt = <330>;
+};
+ };
+};
diff --git a/MAINTAINERS b/MAINTAINERS
index 2fdea49400c9..c7b4c2325890 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8156,6 +8156,13 @@ S: Maintained
F:
Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
F: drivers/spmi/hisi-spmi-contro
[PATCH v5 (RESEND) 1/7] phy: phy-hi3670-usb3: move driver from staging into phy
The phy USB3 driver for Hisilicon 970 (hi3670) is ready
for mainstream. Mode it from staging into the main driver's
phy/ directory.
Acked-by: Rob Herring
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/hisilicon,hi3670-usb3.yaml | 73 ++
MAINTAINERS | 9 +-
drivers/phy/hisilicon/Kconfig | 10 +
drivers/phy/hisilicon/Makefile| 1 +
drivers/phy/hisilicon/phy-hi3670-usb3.c | 668 ++
drivers/staging/hikey9xx/Kconfig | 11 -
drivers/staging/hikey9xx/Makefile | 2 -
drivers/staging/hikey9xx/phy-hi3670-usb3.c| 668 --
drivers/staging/hikey9xx/phy-hi3670-usb3.yaml | 73 --
9 files changed, 760 insertions(+), 755 deletions(-)
create mode 100644
Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml
create mode 100644 drivers/phy/hisilicon/phy-hi3670-usb3.c
delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.c
delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.yaml
diff --git a/Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml
b/Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml
new file mode 100644
index ..ebd78acfe2de
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml
@@ -0,0 +1,73 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/phy/hisilicon,hi3670-usb3.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Hisilicon Kirin970 USB PHY
+
+maintainers:
+ - Mauro Carvalho Chehab
+
+description: |+
+ Bindings for USB3 PHY on HiSilicon Kirin 970.
+
+properties:
+ compatible:
+const: hisilicon,hi3670-usb-phy
+
+ "#phy-cells":
+const: 0
+
+ hisilicon,pericrg-syscon:
+$ref: '/schemas/types.yaml#/definitions/phandle'
+description: phandle of syscon used to control iso refclk.
+
+ hisilicon,pctrl-syscon:
+$ref: '/schemas/types.yaml#/definitions/phandle'
+description: phandle of syscon used to control usb tcxo.
+
+ hisilicon,sctrl-syscon:
+$ref: '/schemas/types.yaml#/definitions/phandle'
+description: phandle of syscon used to control phy deep sleep.
+
+ hisilicon,eye-diagram-param:
+$ref: /schemas/types.yaml#/definitions/uint32
+description: Eye diagram for phy.
+
+ hisilicon,tx-vboost-lvl:
+$ref: /schemas/types.yaml#/definitions/uint32
+description: TX level vboost for phy.
+
+required:
+ - compatible
+ - hisilicon,pericrg-syscon
+ - hisilicon,pctrl-syscon
+ - hisilicon,sctrl-syscon
+ - hisilicon,eye-diagram-param
+ - hisilicon,tx-vboost-lvl
+ - "#phy-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+bus {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ usb3_otg_bc: usb3_otg_bc@ff20 {
+compatible = "syscon", "simple-mfd";
+reg = <0x0 0xff20 0x0 0x1000>;
+
+usb_phy {
+ compatible = "hisilicon,hi3670-usb-phy";
+ #phy-cells = <0>;
+ hisilicon,pericrg-syscon = <_ctrl>;
+ hisilicon,pctrl-syscon = <>;
+ hisilicon,sctrl-syscon = <>;
+ hisilicon,eye-diagram-param = <0xfdfee4>;
+ hisilicon,tx-vboost-lvl = <0x5>;
+};
+ };
+};
diff --git a/MAINTAINERS b/MAINTAINERS
index 8c44fd8fd85d..a37489f5b070 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18654,7 +18654,7 @@ L: linux-...@vger.kernel.org
S: Maintained
F: drivers/usb/roles/intel-xhci-usb-role-switch.c
-USB IP DRIVER FOR HISILICON KIRIN
+USB IP DRIVER FOR HISILICON KIRIN 960
M: Yu Chen
M: Binghui Wang
L: linux-...@vger.kernel.org
@@ -18662,6 +18662,13 @@ S: Maintained
F: Documentation/devicetree/bindings/phy/hisilicon,hi3660-usb3.yaml
F: drivers/phy/hisilicon/phy-hi3660-usb3.c
+USB IP DRIVER FOR HISILICON KIRIN 970
+M: Mauro Carvalho Chehab
+L: linux-...@vger.kernel.org
+S: Maintained
+F: Documentation/devicetree/bindings/phy/hisilicon,kirin970-usb3.yaml
+F: drivers/phy/hisilicon/phy-kirin970-usb3.c
+
USB ISP116X DRIVER
M: Olav Kongas
L: linux-...@vger.kernel.org
diff --git a/drivers/phy/hisilicon/Kconfig b/drivers/phy/hisilicon/Kconfig
index 1c73053bcc98..4d008cfc279c 100644
--- a/drivers/phy/hisilicon/Kconfig
+++ b/drivers/phy/hisilicon/Kconfig
@@ -23,6 +23,16 @@ config PHY_HI3660_USB
To compile this driver as a module, choose M here.
+config PHY_HI3670_USB
+ tristate "hi3670 USB PHY support"
+ depends on (ARCH_HISI && ARM64) || COMPILE_TEST
+ select GENERIC_PHY
+ select MFD_SYSCON
+ help
+ Enable this to support the HISILICON HI3670 USB PHY.
+
+ To compile this driver as a module, choose M here.
+
config PHY_HISTB_COMBPHY
tristate "HiSilicon STB SoCs COMBPHY support"
[PATCH v5 (RESEND) 7/7] dts: hisilicon: add support for USB3 on Hikey 970
Add the USB3 bindings for Kirin 970 phy and Hikey 970 board.
Signed-off-by: Mauro Carvalho Chehab
---
.../boot/dts/hisilicon/hi3670-hikey970.dts| 102 ++
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 58 ++
2 files changed, 160 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
b/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
index 5e6d7b329771..1f221cb97690 100644
--- a/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
+++ b/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
@@ -53,6 +53,29 @@ wlan_en: wlan-en-1-8v {
startup-delay-us = <7>;
enable-active-high;
};
+ hikey_usbhub: hikey_usbhub {
+ compatible = "hisilicon,kirin970_hikey_usbhub";
+
+ typec-vbus-gpios = < 1 0>;
+ otg-switch-gpios = < 2 0>;
+ hub_reset_en_gpio = < 3 0>;
+ hub-vdd-supply = <>;
+ usb-role-switch;
+
+ port {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ hikey_usb_ep0: endpoint@0 {
+ reg = <0>;
+ remote-endpoint = <_role_switch>;
+ };
+ hikey_usb_ep1: endpoint@1 {
+ reg = <1>;
+ remote-endpoint = <_ep>;
+ };
+ };
+ };
};
/*
@@ -430,3 +453,82 @@ {
label = "LS-UART1";
status = "okay";
};
+
+ {
+ status = "okay";
+
+ rt1711h: rt1711h@4e {
+ compatible = "richtek,rt1711h";
+ reg = <0x4e>;
+ status = "okay";
+ interrupt-parent = <>;
+ interrupts = <5 IRQ_TYPE_LEVEL_LOW>;
+ pinctrl-names = "default";
+ pinctrl-0 = <_cfg_func>;
+
+ usb_con: connector {
+ compatible = "usb-c-connector";
+ label = "USB-C";
+ data-role = "dual";
+ power-role = "dual";
+ try-power-role = "sink";
+ source-pdos = ;
+ sink-pdos = ;
+ op-sink-microwatt = <1000>;
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ port@1 {
+ reg = <1>;
+ usb_con_ss: endpoint {
+ remote-endpoint = <_ss>;
+ };
+ };
+ };
+ };
+ port {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ rt1711h_ep: endpoint@0 {
+ reg = <0>;
+ remote-endpoint = <_usb_ep1>;
+ };
+ };
+ };
+};
+
+ {
+ /* USB HUB is on this bus at address 0x44 */
+ status = "okay";
+};
+
+ { /* USB */
+ dr_mode = "otg";
+ maximum-speed = "super-speed";
+ phy_type = "utmi";
+ snps,dis-del-phy-power-chg-quirk;
+ snps,dis_u2_susphy_quirk;
+ snps,dis_u3_susphy_quirk;
+ snps,tx_de_emphasis_quirk;
+ snps,tx_de_emphasis = <1>;
+ snps,dis-split-quirk;
+ snps,gctl-reset-quirk;
+ usb-role-switch;
+ role-switch-default-mode = "host";
+ port {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ dwc3_role_switch: endpoint@0 {
+ reg = <0>;
+ remote-endpoint = <_usb_ep0>;
+ };
+
+ dwc3_ss: endpoint@1 {
+ reg = <1>;
+ remote-endpoint = <_con_ss>;
+ };
+ };
+};
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
b/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
index 8830795c8efc..5522a5de07a8 100644
--- a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
+++ b/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
@@ -8,6 +8,7 @@
#include
#include
+#include
/ {
compatible = "hisilicon,hi3670";
@@ -785,5 +786,62 @@ i2c4: i2c@fdf0d000 {
pinctrl-0 = <_pmx_func _cfg_func>;
status = "disabled";
};
+
+ usb3_o
[PATCH v5 (RESEND) 3/7] spmi: hisi-spmi-controller: move driver from staging
The Hisilicon 6421v600 SPMI driver is ready for mainstream.
So, move it from staging.
Acked-by: Stephen Boyd
Signed-off-by: Mauro Carvalho Chehab
---
.../spmi/hisilicon,hisi-spmi-controller.yaml | 71
MAINTAINERS | 7 +
drivers/spmi/Kconfig | 9 +
drivers/spmi/Makefile | 1 +
drivers/spmi/hisi-spmi-controller.c | 367 ++
drivers/staging/hikey9xx/Kconfig | 11 -
drivers/staging/hikey9xx/Makefile | 1 -
.../staging/hikey9xx/hisi-spmi-controller.c | 367 --
.../hisilicon,hisi-spmi-controller.yaml | 71
9 files changed, 455 insertions(+), 450 deletions(-)
create mode 100644
Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
create mode 100644 drivers/spmi/hisi-spmi-controller.c
delete mode 100644 drivers/staging/hikey9xx/hisi-spmi-controller.c
delete mode 100644 drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml
diff --git
a/Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
b/Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
new file mode 100644
index ..6b755039a74c
--- /dev/null
+++ b/Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
@@ -0,0 +1,71 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/spmi/hisilicon,hisi-spmi-controller.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HiSilicon SPMI controller
+
+maintainers:
+ - Mauro Carvalho Chehab
+
+description: |
+ The HiSilicon SPMI BUS controller is found on some Kirin-based designs.
+ It is a MIPI System Power Management (SPMI) controller.
+
+ The PMIC part is provided by
+ drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml.
+
+allOf:
+ - $ref: spmi.yaml#
+
+properties:
+
+ $nodename:
+pattern: "spmi@[0-9a-f]"
+
+ compatible:
+const: hisilicon,kirin970-spmi-controller
+
+ reg:
+maxItems: 1
+
+ spmi-channel:
+$ref: /schemas/types.yaml#/definitions/uint32
+description: |
+ number of the Kirin 970 SPMI channel where the SPMI devices are
connected.
+
+required:
+ - compatible
+ - reg
+ - spmi-channel
+
+patternProperties:
+ "@[0-9a-f]$":
+description: |
+ PMIC properties, which are specific to the used SPMI PMIC device(s).
+ When used in combination with HiSilicon 6421v600, the properties
+ are documented at
+ drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml.
+
+unevaluatedProperties: false
+
+examples:
+ - |
+bus {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ spmi: spmi@fff24000 {
+compatible = "hisilicon,kirin970-spmi-controller";
+#address-cells = <2>;
+#size-cells = <0>;
+reg = <0x0 0xfff24000 0x0 0x1000>;
+spmi-channel = <2>;
+
+pmic@0 {
+ reg = <0 0>;
+ /* pmic properties */
+};
+ };
+};
diff --git a/MAINTAINERS b/MAINTAINERS
index a37489f5b070..2fdea49400c9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8149,6 +8149,13 @@ F: drivers/crypto/hisilicon/sec2/sec_crypto.c
F: drivers/crypto/hisilicon/sec2/sec_crypto.h
F: drivers/crypto/hisilicon/sec2/sec_main.c
+HISILICON SPMI CONTROLLER DRIVER FOR HIKEY 970
+M: Mauro Carvalho Chehab
+L: linux-kernel@vger.kernel.org
+S: Maintained
+F:
Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml
+F: drivers/spmi/hisi-spmi-controller.c
+
HISILICON STAGING DRIVERS FOR HIKEY 960/970
M: Mauro Carvalho Chehab
S: Maintained
diff --git a/drivers/spmi/Kconfig b/drivers/spmi/Kconfig
index a53bad541f1a..2874b6c26028 100644
--- a/drivers/spmi/Kconfig
+++ b/drivers/spmi/Kconfig
@@ -11,6 +11,15 @@ menuconfig SPMI
if SPMI
+config SPMI_HISI3670
+ tristate "Hisilicon 3670 SPMI Controller"
+ select IRQ_DOMAIN_HIERARCHY
+ depends on HAS_IOMEM
+ help
+ If you say yes to this option, support will be included for the
+ built-in SPMI PMIC Arbiter interface on Hisilicon 3670
+ processors.
+
config SPMI_MSM_PMIC_ARB
tristate "Qualcomm MSM SPMI Controller (PMIC Arbiter)"
select IRQ_DOMAIN_HIERARCHY
diff --git a/drivers/spmi/Makefile b/drivers/spmi/Makefile
index 55a94cadeffe..6e092e6f290c 100644
--- a/drivers/spmi/Makefile
+++ b/drivers/spmi/Makefile
@@ -4,4 +4,5 @@
#
obj-$(CONFIG_SPMI) += spmi.o
+obj-$(CONFIG_SPMI_HISI3670)+= hisi-spmi-controller.o
obj-$(CONFIG_SPMI_MSM_PMIC_ARB)+= spmi-pmic-arb.o
diff --git a/drivers/spmi/hisi-spmi-controller.c
b/drivers/spmi/hisi-spmi-controller.c
new file mode 100644
index ..0d42bc65f39b
--- /dev/null
+++ b/drivers/spmi/hisi-spmi-controller.c
@@ -0,0 +1,367 @@
+// SPDX-License-Ident
[PATCH v5 (RESEND) 5/7] regulator: hi6421v600-regulator: move it from staging
This driver is ready for mainstream. Move it out of staging.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/regulator/Kconfig | 9 +
drivers/regulator/Makefile| 1 +
drivers/regulator/hi6421v600-regulator.c | 299 ++
drivers/staging/Kconfig | 2 -
drivers/staging/Makefile | 1 -
drivers/staging/hikey9xx/Kconfig | 12 -
drivers/staging/hikey9xx/Makefile | 3 -
drivers/staging/hikey9xx/TODO | 5 -
.../staging/hikey9xx/hi6421v600-regulator.c | 299 --
9 files changed, 309 insertions(+), 322 deletions(-)
create mode 100644 drivers/regulator/hi6421v600-regulator.c
delete mode 100644 drivers/staging/hikey9xx/Kconfig
delete mode 100644 drivers/staging/hikey9xx/Makefile
delete mode 100644 drivers/staging/hikey9xx/TODO
delete mode 100644 drivers/staging/hikey9xx/hi6421v600-regulator.c
diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index 77c43134bc9e..ea1d284741cb 100644
--- a/drivers/regulator/Kconfig
+++ b/drivers/regulator/Kconfig
@@ -422,6 +422,15 @@ config REGULATOR_HI655X
This driver provides support for the voltage regulators of the
Hisilicon Hi655x PMIC device.
+config REGULATOR_HI6421V600
+ tristate "HiSilicon Hi6421v600 PMIC voltage regulator support"
+ depends on MFD_HI6421_SPMI && OF
+ select REGMAP
+ help
+ This driver provides support for the voltage regulators on
+ HiSilicon Hi6421v600 PMU / Codec IC.
+ This is used on Kirin 3670 boards, like HiKey 970.
+
config REGULATOR_ISL9305
tristate "Intersil ISL9305 regulator"
depends on I2C
diff --git a/drivers/regulator/Makefile b/drivers/regulator/Makefile
index 44d2f8bf4b74..11c145886c98 100644
--- a/drivers/regulator/Makefile
+++ b/drivers/regulator/Makefile
@@ -49,6 +49,7 @@ obj-$(CONFIG_REGULATOR_FAN53880) += fan53880.o
obj-$(CONFIG_REGULATOR_GPIO) += gpio-regulator.o
obj-$(CONFIG_REGULATOR_HI6421) += hi6421-regulator.o
obj-$(CONFIG_REGULATOR_HI6421V530) += hi6421v530-regulator.o
+obj-$(CONFIG_REGULATOR_HI6421V600) += hi6421v600-regulator.o
obj-$(CONFIG_REGULATOR_HI655X) += hi655x-regulator.o
obj-$(CONFIG_REGULATOR_ISL6271A) += isl6271a-regulator.o
obj-$(CONFIG_REGULATOR_ISL9305) += isl9305.o
diff --git a/drivers/regulator/hi6421v600-regulator.c
b/drivers/regulator/hi6421v600-regulator.c
new file mode 100644
index ..f6a14e9c3cbf
--- /dev/null
+++ b/drivers/regulator/hi6421v600-regulator.c
@@ -0,0 +1,299 @@
+// SPDX-License-Identifier: GPL-2.0
+//
+// Device driver for regulators in Hisi IC
+//
+// Copyright (c) 2013 Linaro Ltd.
+// Copyright (c) 2011 Hisilicon.
+// Copyright (c) 2020-2021 Huawei Technologies Co., Ltd
+//
+// Guodong Xu
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+struct hi6421_spmi_reg_info {
+ struct regulator_desc desc;
+ struct hi6421_spmi_pmic *pmic;
+ u8 eco_mode_mask;
+ u32 eco_uA;
+
+ /* Serialize regulator enable logic */
+ struct mutex enable_mutex;
+};
+
+static const unsigned int ldo3_voltages[] = {
+ 150, 155, 160, 165,
+ 170, 1725000, 175, 1775000,
+ 180, 1825000, 185, 1875000,
+ 190, 1925000, 195, 200
+};
+
+static const unsigned int ldo4_voltages[] = {
+ 1725000, 175, 1775000, 180,
+ 1825000, 185, 1875000, 190
+};
+
+static const unsigned int ldo9_voltages[] = {
+ 175, 180, 1825000, 280,
+ 285, 295, 300, 330
+};
+
+static const unsigned int ldo15_voltages[] = {
+ 180, 185, 240, 260,
+ 270, 285, 295, 300
+};
+
+static const unsigned int ldo17_voltages[] = {
+ 250, 260, 270, 280,
+ 300, 310, 320, 330
+};
+
+static const unsigned int ldo34_voltages[] = {
+ 260, 270, 280, 290,
+ 300, 310, 320, 330
+};
+
+/**
+ * HI6421V600_LDO() - specify a LDO power line
+ * @_id: LDO id name string
+ * @vtable: voltage table
+ * @ereg: enable register
+ * @emask: enable mask
+ * @vreg: voltage select register
+ * @odelay: off/on delay time in uS
+ * @etime: enable time in uS
+ * @ecomask: eco mode mask
+ * @ecoamp: eco mode load uppler limit in uA
+ */
+#define HI6421V600_LDO(_id, vtable, ereg, emask, vreg,\
+ odelay, etime, ecomask, ecoamp) \
+ [HI6421V600_##_id] = { \
+ .desc = { \
+ .name = #_id,\
+ .of_matc
[PATCH v5 (RESEND) 0/7] Move Hisilicon 6421v600 SPMI and USB drivers out of staging
PS.: this series is identical to the one I posted earlier today. The only difference is that it was generated with --no-renames, as per Lee Jones request, in order to make easier to review the code. Hi Greg, Those are the remaining patches that are needed for the USB to work with Hikey970. This is based on the top of next-20210323. The main change from the previous patch series is that a new patch was added: - staging: hisilicon,hisi-spmi-controller.yaml cleanup schema It does some changes at the DT binding file, as requested by Rob. My understanding from the discussions we had, back on Feb, is that those patches will be merged via the staging tree. Thanks! Mauro Mauro Carvalho Chehab (7): phy: phy-hi3670-usb3: move driver from staging into phy staging: hisilicon,hisi-spmi-controller.yaml cleanup schema spmi: hisi-spmi-controller: move driver from staging mfd: hi6421-spmi-pmic: move driver from staging regulator: hi6421v600-regulator: move it from staging dts: hisilicon: add support for the PMIC found on Hikey 970 dts: hisilicon: add support for USB3 on Hikey 970 .../mfd/hisilicon,hi6421-spmi-pmic.yaml | 135 .../bindings/phy/hisilicon,hi3670-usb3.yaml | 73 ++ .../spmi/hisilicon,hisi-spmi-controller.yaml | 71 ++ MAINTAINERS | 23 +- .../boot/dts/hisilicon/hi3670-hikey970.dts| 124 +++- arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 58 ++ .../boot/dts/hisilicon/hikey970-pmic.dtsi | 87 +++ drivers/mfd/Kconfig | 16 + drivers/mfd/Makefile | 1 + drivers/mfd/hi6421-spmi-pmic.c| 297 drivers/phy/hisilicon/Kconfig | 10 + drivers/phy/hisilicon/Makefile| 1 + drivers/phy/hisilicon/phy-hi3670-usb3.c | 668 ++ drivers/regulator/Kconfig | 9 + drivers/regulator/Makefile| 1 + drivers/regulator/hi6421v600-regulator.c | 299 drivers/spmi/Kconfig | 9 + drivers/spmi/Makefile | 1 + drivers/spmi/hisi-spmi-controller.c | 367 ++ drivers/staging/Kconfig | 2 - drivers/staging/Makefile | 1 - drivers/staging/hikey9xx/Kconfig | 52 -- drivers/staging/hikey9xx/Makefile | 7 - drivers/staging/hikey9xx/TODO | 5 - drivers/staging/hikey9xx/hi6421-spmi-pmic.c | 297 .../staging/hikey9xx/hi6421v600-regulator.c | 299 .../staging/hikey9xx/hisi-spmi-controller.c | 367 -- .../hikey9xx/hisilicon,hi6421-spmi-pmic.yaml | 135 .../hisilicon,hisi-spmi-controller.yaml | 75 -- drivers/staging/hikey9xx/phy-hi3670-usb3.c| 668 -- drivers/staging/hikey9xx/phy-hi3670-usb3.yaml | 73 -- 31 files changed, 2230 insertions(+), 2001 deletions(-) create mode 100644 Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml create mode 100644 Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml create mode 100644 Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml create mode 100644 arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi create mode 100644 drivers/mfd/hi6421-spmi-pmic.c create mode 100644 drivers/phy/hisilicon/phy-hi3670-usb3.c create mode 100644 drivers/regulator/hi6421v600-regulator.c create mode 100644 drivers/spmi/hisi-spmi-controller.c delete mode 100644 drivers/staging/hikey9xx/Kconfig delete mode 100644 drivers/staging/hikey9xx/Makefile delete mode 100644 drivers/staging/hikey9xx/TODO delete mode 100644 drivers/staging/hikey9xx/hi6421-spmi-pmic.c delete mode 100644 drivers/staging/hikey9xx/hi6421v600-regulator.c delete mode 100644 drivers/staging/hikey9xx/hisi-spmi-controller.c delete mode 100644 drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml delete mode 100644 drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.c delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.yaml -- 2.30.2
[PATCH v5 (RESEND) 6/7] dts: hisilicon: add support for the PMIC found on Hikey 970
Add a device tree for the HiSilicon 6421v600 SPMI PMIC, used
on HiKey970 board.
As we now have support for it, change the fixed regulators
used by the SD I/O to use the proper LDO supplies.
Signed-off-by: Mauro Carvalho Chehab
---
.../boot/dts/hisilicon/hi3670-hikey970.dts| 22 +
.../boot/dts/hisilicon/hikey970-pmic.dtsi | 87 +++
2 files changed, 90 insertions(+), 19 deletions(-)
create mode 100644 arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
b/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
index 7f9f9886c349..5e6d7b329771 100644
--- a/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
+++ b/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts
@@ -12,6 +12,7 @@
#include "hi3670.dtsi"
#include "hikey970-pinctrl.dtsi"
+#include "hikey970-pmic.dtsi"
/ {
model = "HiKey970";
@@ -39,23 +40,6 @@ memory@0 {
reg = <0x0 0x0 0x0 0x0>;
};
- sd_1v8: regulator-1v8 {
- compatible = "regulator-fixed";
- regulator-name = "fixed-1.8V";
- regulator-min-microvolt = <180>;
- regulator-max-microvolt = <180>;
- regulator-always-on;
- };
-
- sd_3v3: regulator-3v3 {
- compatible = "regulator-fixed";
- regulator-name = "fixed-3.3V";
- regulator-min-microvolt = <330>;
- regulator-max-microvolt = <330>;
- regulator-boot-on;
- regulator-always-on;
- };
-
wlan_en: wlan-en-1-8v {
compatible = "regulator-fixed";
regulator-name = "wlan-en-regulator";
@@ -402,8 +386,8 @@ {
pinctrl-0 = <_pmx_func
_clk_cfg_func
_cfg_func>;
- vmmc-supply = <_3v3>;
- vqmmc-supply = <_1v8>;
+ vmmc-supply = <>;
+ vqmmc-supply = <>;
status = "okay";
};
diff --git a/arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi
b/arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi
new file mode 100644
index ..8cf45b962fea
--- /dev/null
+++ b/arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi
@@ -0,0 +1,87 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * dts file for Hi6421v600 SPMI PMIC used at the HiKey970 Development Board
+ *
+ * Copyright (C) 2020, Huawei Tech. Co., Ltd.
+ */
+
+#include
+
+/ {
+ spmi: spmi@fff24000 {
+ compatible = "hisilicon,kirin970-spmi-controller";
+ #address-cells = <2>;
+ #size-cells = <0>;
+ status = "okay";
+ reg = <0x0 0xfff24000 0x0 0x1000>;
+ spmi-channel = <2>;
+
+ pmic: pmic@0 {
+ compatible = "hisilicon,hi6421-spmi";
+ reg = <0 SPMI_USID>;
+
+ #interrupt-cells = <2>;
+ interrupt-controller;
+ gpios = < 0 0>;
+
+ regulators {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ ldo3: LDO3 {
+ regulator-name = "ldo3";
+ regulator-min-microvolt = <150>;
+ regulator-max-microvolt = <200>;
+ regulator-boot-on;
+ };
+
+ ldo4: LDO4 { /* 40 PIN */
+ regulator-name = "ldo4";
+ regulator-min-microvolt = <1725000>;
+ regulator-max-microvolt = <190>;
+ regulator-boot-on;
+ };
+
+ ldo9: LDO9 { /* SDCARD I/O */
+ regulator-name = "ldo9";
+ regulator-min-microvolt = <175>;
+ regulator-max-microvolt = <330>;
+ regulator-boot-on;
+ };
+
+ ldo15: LDO15 { /* UFS */
+ regulator-name = "ldo15";
+ regulator-min-microvolt = <180>;
+ regulator-max-microvolt = <300>;
+ regulator-always-on;
+
[PATCH v5 (RESEND) 2/7] staging: hisilicon,hisi-spmi-controller.yaml cleanup schema
Remove some properties already defined at SPMI bus, and place the type for the spmi-channel. Signed-off-by: Mauro Carvalho Chehab --- .../hisilicon,hisi-spmi-controller.yaml| 18 +++--- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml b/drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml index 21f68a9c2df1..6b755039a74c 100644 --- a/drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml +++ b/drivers/staging/hikey9xx/hisilicon,hisi-spmi-controller.yaml @@ -16,7 +16,11 @@ description: | The PMIC part is provided by drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml. +allOf: + - $ref: spmi.yaml# + properties: + $nodename: pattern: "spmi@[0-9a-f]" @@ -26,13 +30,8 @@ properties: reg: maxItems: 1 - "#address-cells": -const: 2 - - "#size-cells": -const: 0 - spmi-channel: +$ref: /schemas/types.yaml#/definitions/uint32 description: | number of the Kirin 970 SPMI channel where the SPMI devices are connected. @@ -40,18 +39,16 @@ required: - compatible - reg - spmi-channel - - "#address-cells" - - "#size-cells" patternProperties: - "^pmic@[0-9a-f]$": + "@[0-9a-f]$": description: | PMIC properties, which are specific to the used SPMI PMIC device(s). When used in combination with HiSilicon 6421v600, the properties are documented at drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml. -additionalProperties: false +unevaluatedProperties: false examples: - | @@ -63,7 +60,6 @@ examples: compatible = "hisilicon,kirin970-spmi-controller"; #address-cells = <2>; #size-cells = <0>; -status = "ok"; reg = <0x0 0xfff24000 0x0 0x1000>; spmi-channel = <2>; -- 2.30.2
Re: [PATCH 8/8] docs: dt: Add DT API documentation
Em Thu, 25 Mar 2021 10:47:13 -0600 Rob Herring escreveu: > The kernel-doc for the DT APIs are not included in the documentation > build. Add them. > > Cc: Frank Rowand > Cc: Mauro Carvalho Chehab Reviewed-by: Mauro Carvalho Chehab > Signed-off-by: Rob Herring > --- > Documentation/devicetree/index.rst | 1 + > Documentation/devicetree/kernel-api.rst | 57 + > 2 files changed, 58 insertions(+) > create mode 100644 Documentation/devicetree/kernel-api.rst > > diff --git a/Documentation/devicetree/index.rst > b/Documentation/devicetree/index.rst > index 70b5dcdbcf07..1a2fc8014996 100644 > --- a/Documentation/devicetree/index.rst > +++ b/Documentation/devicetree/index.rst > @@ -11,6 +11,7 @@ Kernel Devicetree Usage > > usage-model > of_unittest > + kernel-api > > Devicetree Overlays > === > diff --git a/Documentation/devicetree/kernel-api.rst > b/Documentation/devicetree/kernel-api.rst > new file mode 100644 > index ..b7429e6ed6d5 > --- /dev/null > +++ b/Documentation/devicetree/kernel-api.rst > @@ -0,0 +1,57 @@ > +.. SPDX-License-Identifier: GPL-2.0 > +.. _devicetree: > + > +== > +DeviceTree Kernel API > +== > + > +Core functions > +-- > + > +.. kernel-doc:: drivers/of/base.c > + :export: > + > +.. kernel-doc:: include/linux/of.h > + :internal: > + > +.. kernel-doc:: drivers/of/property.c > + :export: > + > +.. kernel-doc:: include/linux/of_graph.h > + :internal: > + > +.. kernel-doc:: drivers/of/address.c > + :export: > + > +.. kernel-doc:: drivers/of/irq.c > + :export: > + > +.. kernel-doc:: drivers/of/fdt.c > + :export: > + > +Driver model functions > +-- > + > +.. kernel-doc:: include/linux/of_device.h > + :internal: > + > +.. kernel-doc:: drivers/of/device.c > + :export: > + > +.. kernel-doc:: include/linux/of_platform.h > + :internal: > + > +.. kernel-doc:: drivers/of/platform.c > + :export: > + > +Overlay and Dynamic DT functions > + > + > +.. kernel-doc:: drivers/of/resolver.c > + :export: > + > +.. kernel-doc:: drivers/of/dynamic.c > + :export: > + > +.. kernel-doc:: drivers/of/overlay.c > + :export: Thanks, Mauro
Re: [PATCH 5/8] docs: dt: Group DT docs into relevant sub-sections
Em Thu, 25 Mar 2021 10:47:10 -0600
Rob Herring escreveu:
> The DT docs are currently all just lumped together in the doc build.
> Let's organize the documents by kernel specifics, overlays and bindings.
>
> As writing-schema.rst is about bindings, let's move it to the bindings
> directory.
>
> Cc: Frank Rowand
> Cc: Mauro Carvalho Chehab
Reviewed-by: Mauro Carvalho Chehab
> Signed-off-by: Rob Herring
> ---
> Documentation/devicetree/bindings/index.rst | 7 ++-
> .../devicetree/{ => bindings}/writing-schema.rst | 0
> Documentation/devicetree/index.rst | 16 ++--
> 3 files changed, 16 insertions(+), 7 deletions(-)
> rename Documentation/devicetree/{ => bindings}/writing-schema.rst (100%)
>
> diff --git a/Documentation/devicetree/bindings/index.rst
> b/Documentation/devicetree/bindings/index.rst
> index 3837b17c234f..d9002a3a0abb 100644
> --- a/Documentation/devicetree/bindings/index.rst
> +++ b/Documentation/devicetree/bindings/index.rst
> @@ -1,12 +1,9 @@
> .. SPDX-License-Identifier: GPL-2.0
>
> -===
> -Device Tree
> -===
> -
> .. toctree::
> :maxdepth: 1
>
> ABI
> - submitting-patches
> writing-bindings
> + writing-schema
> + submitting-patches
> diff --git a/Documentation/devicetree/writing-schema.rst
> b/Documentation/devicetree/bindings/writing-schema.rst
> similarity index 100%
> rename from Documentation/devicetree/writing-schema.rst
> rename to Documentation/devicetree/bindings/writing-schema.rst
> diff --git a/Documentation/devicetree/index.rst
> b/Documentation/devicetree/index.rst
> index 32509e8de8da..70b5dcdbcf07 100644
> --- a/Documentation/devicetree/index.rst
> +++ b/Documentation/devicetree/index.rst
> @@ -4,14 +4,26 @@
> Open Firmware and Devicetree
> =
>
> +Kernel Devicetree Usage
> +===
> .. toctree::
> :maxdepth: 1
>
> usage-model
> - writing-schema
> + of_unittest
> +
> +Devicetree Overlays
> +===
> +.. toctree::
> + :maxdepth: 1
> +
> changesets
> dynamic-resolution-notes
> - of_unittest
> overlay-notes
>
> +Devicetree Bindings
> +===
> +.. toctree::
> + :maxdepth: 1
> +
> bindings/index
Thanks,
Mauro
Re: [PATCH 7/8] of: Add missing 'Return' section in kerneldoc comments
Em Thu, 25 Mar 2021 10:47:12 -0600
Rob Herring escreveu:
> Many of the DT kerneldoc comments are lacking a 'Return' section. Let's
> add the section in cases we have a description of return values. There's
> still some cases where the return values are not documented.
>
> Cc: Frank Rowand
> Cc: Mauro Carvalho Chehab
Reviewed-by: Mauro Carvalho Chehab
> Signed-off-by: Rob Herring
> ---
> drivers/of/base.c | 39 +
> drivers/of/dynamic.c | 19 -
> drivers/of/fdt.c | 8 +++---
> drivers/of/irq.c | 14 -
> drivers/of/overlay.c | 16 +--
> drivers/of/platform.c | 10 +++
> drivers/of/property.c | 66 +++
> include/linux/of.h| 63 ++---
> 8 files changed, 140 insertions(+), 95 deletions(-)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index b06bcb3f001a..3bf189d394bd 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -244,7 +244,7 @@ struct device_node *__of_find_all_nodes(struct
> device_node *prev)
> * @prev:Previous node or NULL to start iteration
> * of_node_put() will be called on it
> *
> - * Returns a node pointer with refcount incremented, use
> + * Return: A node pointer with refcount incremented, use
> * of_node_put() on it when done.
> */
> struct device_node *of_find_all_nodes(struct device_node *prev)
> @@ -374,7 +374,7 @@ bool __weak arch_find_n_match_cpu_physical_id(struct
> device_node *cpun,
> * before booting secondary cores. This function uses arch_match_cpu_phys_id
> * which can be overridden by architecture specific implementation.
> *
> - * Returns a node pointer for the logical cpu with refcount incremented, use
> + * Return: A node pointer for the logical cpu with refcount incremented, use
> * of_node_put() on it when done. Returns NULL if not found.
> */
> struct device_node *of_get_cpu_node(int cpu, unsigned int *thread)
> @@ -394,8 +394,8 @@ EXPORT_SYMBOL(of_get_cpu_node);
> *
> * @cpu_node: Pointer to the device_node for CPU.
> *
> - * Returns the logical CPU number of the given CPU device_node.
> - * Returns -ENODEV if the CPU is not found.
> + * Return: The logical CPU number of the given CPU device_node or -ENODEV if
> the
> + * CPU is not found.
> */
> int of_cpu_node_to_id(struct device_node *cpu_node)
> {
> @@ -427,7 +427,7 @@ EXPORT_SYMBOL(of_cpu_node_to_id);
> * bindings. This function check for both and returns the idle state node for
> * the requested index.
> *
> - * In case an idle state node is found at @index, the refcount is incremented
> + * Return: An idle state node if found at @index. The refcount is incremented
> * for it, so call of_node_put() on it when done. Returns NULL if not found.
> */
> struct device_node *of_get_cpu_state_node(struct device_node *cpu_node,
> @@ -561,7 +561,7 @@ int of_device_compatible_match(struct device_node *device,
> * of_machine_is_compatible - Test root of device tree for a given
> compatible value
> * @compat: compatible string to look for in root node's compatible property.
> *
> - * Returns a positive integer if the root node has the given value in its
> + * Return: A positive integer if the root node has the given value in its
> * compatible property.
> */
> int of_machine_is_compatible(const char *compat)
> @@ -583,7 +583,7 @@ EXPORT_SYMBOL(of_machine_is_compatible);
> *
> * @device: Node to check for availability, with locks already held
> *
> - * Returns true if the status property is absent or set to "okay" or "ok",
> + * Return: True if the status property is absent or set to "okay" or "ok",
> * false otherwise
> */
> static bool __of_device_is_available(const struct device_node *device)
> @@ -611,7 +611,7 @@ static bool __of_device_is_available(const struct
> device_node *device)
> *
> * @device: Node to check for availability
> *
> - * Returns true if the status property is absent or set to "okay" or "ok",
> + * Return: True if the status property is absent or set to "okay" or "ok",
> * false otherwise
> */
> bool of_device_is_available(const struct device_node *device)
> @@ -632,7 +632,7 @@ EXPORT_SYMBOL(of_device_is_available);
> *
> * @device: Node to check for endianness
> *
> - * Returns true if the device has a "big-endian" property, or if the kernel
> + * Return: True if the device has a "big-endian" property, or if the kernel
> * was compiled for BE *and* the device has a "native-endian" property.
> * Returns
Re: [PATCH 3/8] docs: dt: writing-schema: Include the example schema in the doc build
Em Thu, 25 Mar 2021 10:47:08 -0600 Rob Herring escreveu: > The example-schema.yaml file serves as documentation, so let's include it > from writing-schema.rst. > > Cc: Frank Rowand > Cc: Mauro Carvalho Chehab Reviewed-by: Mauro Carvalho Chehab > Signed-off-by: Rob Herring > --- > Documentation/devicetree/writing-schema.rst | 11 +++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/writing-schema.rst > b/Documentation/devicetree/writing-schema.rst > index 03e279d8fd6a..be14dbed6081 100644 > --- a/Documentation/devicetree/writing-schema.rst > +++ b/Documentation/devicetree/writing-schema.rst > @@ -8,6 +8,8 @@ written in a JSON compatible subset of YAML. YAML is used > instead of JSON as it > is considered more human readable and has some advantages such as allowing > comments (Prefixed with '#'). > > +Also see :ref:`example-schema`. > + > Schema Contents > --- > > @@ -170,3 +172,12 @@ json-schema Resources > `JSON-Schema Specifications <http://json-schema.org/>`_ > > `Using JSON Schema Book <http://usingjsonschema.com/>`_ > + > +.. _example-schema: > + > +Annotated Example Schema > + > + > +Also available as a separate file: :download:`example-schema.yaml` > + > +.. literalinclude:: example-schema.yaml Thanks, Mauro
Re: [PATCH 2/8] docs: dt: writing-schema: Remove spurious indentation
Em Thu, 25 Mar 2021 10:47:07 -0600 Rob Herring escreveu: > 'allOf' and 'properties' have a leading space which causes them to be > indented in the doc output. > > Cc: Frank Rowand > Cc: Mauro Carvalho Chehab Reviewed-by: Mauro Carvalho Chehab > Signed-off-by: Rob Herring > --- > Documentation/devicetree/writing-schema.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/writing-schema.rst > b/Documentation/devicetree/writing-schema.rst > index 16f21e182ff6..03e279d8fd6a 100644 > --- a/Documentation/devicetree/writing-schema.rst > +++ b/Documentation/devicetree/writing-schema.rst > @@ -46,12 +46,12 @@ select >schema. By default without 'select', nodes are matched against their > possible >compatible string values or node name. Most bindings should not need > select. > > - allOf > +allOf >Optional. A list of other schemas to include. This is used to >include other schemas the binding conforms to. This may be schemas for a >particular class of devices such as I2C or SPI controllers. > > - properties > +properties >A set of sub-schema defining all the DT properties for the >binding. The exact schema syntax depends on whether properties are known, >common properties (e.g. 'interrupts') or are binding/vendor specific > properties. Thanks, Mauro
Re: [PATCH 1/8] dt-bindings: Fix reference in submitting-patches.rst to the DT ABI doc
Em Thu, 25 Mar 2021 10:47:06 -0600 Rob Herring escreveu: > submitting-patches.rst has a stale reference to ABI.txt. Fix this with a > proper rSt link. > > Cc: Frank Rowand > Cc: Mauro Carvalho Chehab > Signed-off-by: Rob Herring Reviewed-by: Mauro Carvalho Chehab > --- > Documentation/devicetree/bindings/submitting-patches.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/submitting-patches.rst > b/Documentation/devicetree/bindings/submitting-patches.rst > index 68129ff09967..42e86f978be2 100644 > --- a/Documentation/devicetree/bindings/submitting-patches.rst > +++ b/Documentation/devicetree/bindings/submitting-patches.rst > @@ -84,7 +84,7 @@ II. For kernel maintainers > III. Notes > == > > - 0) Please see ...bindings/ABI.txt for details regarding devicetree ABI. > + 0) Please see :doc:`ABI` for details regarding devicetree ABI. > >1) This document is intended as a general familiarization with the process > as > decided at the 2013 Kernel Summit. When in doubt, the current word of > the Thanks, Mauro
Re: [PATCH 6/8] of: Fix kerneldoc output formatting
Em Thu, 25 Mar 2021 10:47:11 -0600
Rob Herring escreveu:
> The indentation of the kerneldoc comments affects the output formatting.
> Leading tabs in particular don't work, and sections need to be indented
> under the section header.
>
> The example snippets for DT source in the comments still have some
> formatting issues, but there doesn't seem to be any way to do multi-line
> literal blocks in kerneldoc.
>
> Cc: Frank Rowand
> Cc: Mauro Carvalho Chehab
> Signed-off-by: Rob Herring
> ---
>
> Note the dts examples still cause warnings. I couldn't find any way to
> do a literal block and fix them. Minimally, there needs to be a way to
> escape ':' and not create sections:
>
> Documentation/devicetree/kernel-api:11: ../drivers/of/base.c:1466: WARNING:
> Definition list ends without a blank line; unexpected unindent.
You can do something like this:
/**
* of_parse_phandle_with_args() - Find a node pointed by phandle in a list
* @np: pointer to a device tree node containing a list
* @list_name: property name that contains a list
* @cells_name: property name that specifies phandles' arguments count
* @index: index of a phandle to parse out
* @out_args: optional pointer to output arguments structure (will be filled)
*
* This function is useful to parse lists of phandles and their arguments.
* Returns 0 on success and fills out_args, on error returns appropriate
* errno value.
*
* Caller is responsible to call of_node_put() on the returned out_args->np
* pointer.
*
* For example::
*
* phandle1: node1 {
* #list-cells = <2>;
* };
*
* phandle2: node2 {
* #list-cells = <1>;
* };
*
* node3 {
* list = < 1 2 3>;
* };
*
* To get a device_node of the ``node2`` node you may call this:
* of_parse_phandle_with_args(node3, "list", "#list-cells", 1, );
*/
The problem is that using just:
/**
...
* Example::
...
Would make confusion with an existing regex at kernel-doc script that
parses a regex similar to this:
\*\s+(\w+):
Into:
**$1**
So, using two words fix the issue.
Granted, this is something that could be improved at kernel-doc with
something like (untested):
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index cb92d0e1e932..cea82e004fce 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -392,7 +392,7 @@ my $doc_com_body = '\s*\* ?';
my $doc_decl = $doc_com . '(\w+)';
# @params and a strictly limited set of supported section names
my $doc_sect = $doc_com .
-
'\s*(\@[.\w]+|\@\.\.\.|description|context|returns?|notes?|examples?)\s*:(.*)';
+
'\s*(\@[.\w]+|\@\.\.\.|description|context|returns?|notes?|examples?)\s*:([^:]*)$';
my $doc_content = $doc_com_body . '(.*)';
my $doc_block = $doc_com . 'DOC:\s*(.*)?';
my $doc_inline_start = '^\s*/\*\*\s*$';
I'll run some tests if the above works and submit a separate patch
addressing it, likely tomorrow.
Thanks,
Mauro
Re: [PATCH 4/8] docs: dt: Make 'Devicetree' wording more consistent
Em Thu, 25 Mar 2021 10:47:09 -0600 Rob Herring escreveu: > There's a variety of ways 'Devicetree' has been written. This is most > evident in the documentation build contents where we have 'Device Tree', > 'DeviceTree', etc. The DT spec has somewhat standardized on > 'Devicetree', so let's use that. > > Cc: Frank Rowand > Cc: Mauro Carvalho Chehab > Signed-off-by: Rob Herring > --- > Documentation/devicetree/bindings/submitting-patches.rst | 2 +- > Documentation/devicetree/changesets.rst | 8 > Documentation/devicetree/dynamic-resolution-notes.rst| 8 > Documentation/devicetree/index.rst | 2 +- > Documentation/devicetree/of_unittest.rst | 6 +++--- > Documentation/devicetree/overlay-notes.rst | 8 > Documentation/devicetree/usage-model.rst | 8 > Documentation/devicetree/writing-schema.rst | 2 +- > 8 files changed, 22 insertions(+), 22 deletions(-) > > diff --git a/Documentation/devicetree/bindings/submitting-patches.rst > b/Documentation/devicetree/bindings/submitting-patches.rst > index 42e86f978be2..51c459909575 100644 > --- a/Documentation/devicetree/bindings/submitting-patches.rst > +++ b/Documentation/devicetree/bindings/submitting-patches.rst > @@ -1,7 +1,7 @@ > .. SPDX-License-Identifier: GPL-2.0 > > == > -Submitting devicetree (DT) binding patches > +Submitting Devicetree (DT) binding patches > == > > I. For patch submitters > diff --git a/Documentation/devicetree/changesets.rst > b/Documentation/devicetree/changesets.rst > index c7fd8cd6a270..2091468d4837 100644 > --- a/Documentation/devicetree/changesets.rst > +++ b/Documentation/devicetree/changesets.rst > @@ -1,10 +1,10 @@ > .. SPDX-License-Identifier: GPL-2.0 > > -= > -DT Changesets > -= > += > +Devicetree Changesets > += > > -A DT changeset is a method which allows one to apply changes > +A Devicetree changeset is a method which allows one to apply changes > in the live tree in such a way that either the full set of changes > will be applied, or none of them will be. If an error occurs partway > through applying the changeset, then the tree will be rolled back to the > diff --git a/Documentation/devicetree/dynamic-resolution-notes.rst > b/Documentation/devicetree/dynamic-resolution-notes.rst > index 570b7e1f39eb..f81ad8daa36f 100644 > --- a/Documentation/devicetree/dynamic-resolution-notes.rst > +++ b/Documentation/devicetree/dynamic-resolution-notes.rst > @@ -1,11 +1,11 @@ > .. SPDX-License-Identifier: GPL-2.0 > > -== > -Device Tree Dynamic Resolver Notes > -== > += > +Devicetree Dynamic Resolver Notes > += > > This document describes the implementation of the in-kernel > -Device Tree resolver, residing in drivers/of/resolver.c > +DeviceTree resolver, residing in drivers/of/resolver.c DeviceTree -> Devicetree. The rest looks ok to me. Reviewed-by: Mauro Carvalho Chehab > > How the resolver works > -- > diff --git a/Documentation/devicetree/index.rst > b/Documentation/devicetree/index.rst > index 54026763916d..32509e8de8da 100644 > --- a/Documentation/devicetree/index.rst > +++ b/Documentation/devicetree/index.rst > @@ -1,7 +1,7 @@ > .. SPDX-License-Identifier: GPL-2.0 > > = > -Open Firmware and Device Tree > +Open Firmware and Devicetree > = > > .. toctree:: > diff --git a/Documentation/devicetree/of_unittest.rst > b/Documentation/devicetree/of_unittest.rst > index dea05214f3ad..2afe41a37148 100644 > --- a/Documentation/devicetree/of_unittest.rst > +++ b/Documentation/devicetree/of_unittest.rst > @@ -1,8 +1,8 @@ > .. SPDX-License-Identifier: GPL-2.0 > > -== > -Open Firmware Device Tree Unittest > -== > += > +Open Firmware Devicetree Unittest > += > > Author: Gaurav Minocha > > diff --git a/Documentation/devicetree/overlay-notes.rst > b/Documentation/devicetree/overlay-notes.rst > index c67cc676bbd2..b2b8db765b8c 100644 > --- a/Documentation/devicetree/overlay-notes.rst > +++ b/Documentation/devicetree/overlay-notes.rst > @@ -1,8 +1,8 @@ > .. SPDX-License-Identifier: GPL-2.0 > > -= > -Device Tree Ov
