| Message ID | 20210527201309.13308-1-dariobin@libero.it |
|---|---|
| State | Accepted |
| Commit | 07d5136f9bf1fa6abe70a1f88b04c1216fbf87a2 |
| Headers | show |
| Series | docs/pinctrl: fix the reference to the u300 platform | expand |
On Thu, May 27, 2021 at 10:13 PM Dario Binacchi <dariobin@libero.it> wrote: > With commit ce1380c9f4bc ("ARM: remove u300 platform") it is wrong to > use arch/arm/mach-u300/Kconfig file as example. Since the u300 platform > has been replaced by the u8500, let's use its Kconfig as example. > > Signed-off-by: Dario Binacchi <dariobin@libero.it> Patch applied! Yours, Linus Walleij
diff --git a/Documentation/driver-api/pin-control.rst b/Documentation/driver-api/pin-control.rst index e2474425fb0c..71eefe5a023f 100644 --- a/Documentation/driver-api/pin-control.rst +++ b/Documentation/driver-api/pin-control.rst @@ -95,7 +95,7 @@ this in our driver:: To enable the pinctrl subsystem and the subgroups for PINMUX and PINCONF and selected drivers, you need to select them from your machine's Kconfig entry, since these are so tightly integrated with the machines they are used on. -See for example arch/arm/mach-u300/Kconfig for an example. +See for example arch/arm/mach-ux500/Kconfig for an example. Pins usually have fancier names than this. You can find these in the datasheet for your chip. Notice that the core pinctrl.h file provides a fancy macro
With commit ce1380c9f4bc ("ARM: remove u300 platform") it is wrong to use arch/arm/mach-u300/Kconfig file as example. Since the u300 platform has been replaced by the u8500, let's use its Kconfig as example. Signed-off-by: Dario Binacchi <dariobin@libero.it> --- Documentation/driver-api/pin-control.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)