2015-08-27 10:11:51

by Marcel Ziswiler

[permalink] [raw]
Subject: [PATCH] arm: tegra: update default configuration

* Expose hardware/virtual IRQ mapping via debugfs
* WM9712 audio/touch controller as found on Colibri T20
* sysfs interface for GPIOs
* NFS client support for NFS version 4

Signed-off-by: Marcel Ziswiler <[email protected]>
---

arch/arm/configs/tegra_defconfig | 8 ++++++++
1 file changed, 8 insertions(+)

diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig
index 9808581..6645460 100644
--- a/arch/arm/configs/tegra_defconfig
+++ b/arch/arm/configs/tegra_defconfig
@@ -1,5 +1,6 @@
CONFIG_SYSVIPC=y
CONFIG_FHANDLE=y
+CONFIG_IRQ_DOMAIN_DEBUG=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_IKCONFIG=y
@@ -121,6 +122,9 @@ CONFIG_KEYBOARD_CROS_EC=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ATMEL_MXT=y
+CONFIG_TOUCHSCREEN_WM97XX=y
+# CONFIG_TOUCHSCREEN_WM9705 is not set
+# CONFIG_TOUCHSCREEN_WM9713 is not set
CONFIG_TOUCHSCREEN_STMPE=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_MPU3050=y
@@ -142,11 +146,13 @@ CONFIG_SPI_TEGRA20_SFLASH=y
CONFIG_SPI_TEGRA20_SLINK=y
CONFIG_PINCTRL_AS3722=y
CONFIG_PINCTRL_PALMAS=y
+CONFIG_GPIO_SYSFS=y
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_GPIO_PALMAS=y
CONFIG_GPIO_TPS6586X=y
CONFIG_GPIO_TPS65910=y
+CONFIG_BATTERY_WM97XX=y
CONFIG_BATTERY_SBS=y
CONFIG_CHARGER_TPS65090=y
CONFIG_POWER_RESET=y
@@ -208,6 +214,7 @@ CONFIG_SND_SOC_TEGRA=y
CONFIG_SND_SOC_TEGRA_RT5640=y
CONFIG_SND_SOC_TEGRA_WM8753=y
CONFIG_SND_SOC_TEGRA_WM8903=y
+CONFIG_SND_SOC_TEGRA_WM9712=y
CONFIG_SND_SOC_TEGRA_TRIMSLICE=y
CONFIG_SND_SOC_TEGRA_ALC5632=y
CONFIG_SND_SOC_TEGRA_MAX98090=y
@@ -278,6 +285,7 @@ CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
CONFIG_NFS_FS=y
+CONFIG_NFS_V4=y
CONFIG_ROOT_NFS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
--
2.4.3


2015-08-27 14:55:06

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] arm: tegra: update default configuration

On Thu, Aug 27, 2015 at 12:10:55PM +0200, Marcel Ziswiler wrote:

> * WM9712 audio/touch controller as found on Colibri T20

> +CONFIG_BATTERY_WM97XX=y

Does the system really have the wm9712 wired up as a battery monitor?


Attachments:
(No filename) (225.00 B)
signature.asc (473.00 B)
Digital signature
Download all attachments

2015-08-28 16:52:10

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] arm: tegra: update default configuration

On Fri, Aug 28, 2015 at 05:41:43AM +0000, Marcel Ziswiler wrote:

Please fix your mailer to word wrap within paragraphs so that your mails
are legible.

> On 27 Aug 2015 16:55, Mark Brown <[email protected]> wrote:

> > Does the system really have the wm9712 wired up as a battery monitor?

> Well, remember we are talking about a system on module. Those WM9712
> pins all go to the 200 pin SODIMM edge connector and I know that
> certain customers indeed have carrier boards that use it that way. If
> there is any opposition and considering this being rather optional I
> may also drop this one but audio/touch is definitely a standard
> feature available on all or carrier boards.

Does that actually work with mainline? The driver requires platform
data to do anything useful (there's no DT bindings for it) and I can't
see anything providing that on Tegra systems.


Attachments:
(No filename) (872.00 B)
signature.asc (473.00 B)
Digital signature
Download all attachments

2015-08-28 20:30:43

by Marcel Ziswiler

[permalink] [raw]
Subject: Re: [PATCH] arm: tegra: update default configuration

On Fri, 2015-08-28 at 16:51 +0000, Mark Brown wrote:

> Please fix your mailer to word wrap within paragraphs so that your
> mails
> are legible.

Sure, sorry. At times I forget that Android isn't sane in that respect
and can't be used to send mailing list compliant emails.

> > On 27 Aug 2015 16:55, Mark Brown <[email protected]> wrote:
>
> > > Does the system really have the wm9712 wired up as a battery
> > > monitor?
>
> > Well, remember we are talking about a system on module. Those
> > WM9712
> > pins all go to the 200 pin SODIMM edge connector and I know that
> > certain customers indeed have carrier boards that use it that way.
> > If
> > there is any opposition and considering this being rather optional
> > I
> > may also drop this one but audio/touch is definitely a standard
> > feature available on all or carrier boards.
>
> Does that actually work with mainline? The driver requires platform
> data to do anything useful (there's no DT bindings for it) and I
> can't
> see anything providing that on Tegra systems.

To be honest I have not really tried it resp. I did actually notice it
bailing out but haven't had time to look closer into it yet. We are
using it with NVIDIA's still platform data based downstream L4T R16.5
and I do know that it works there so I just kind of assumed there will
be a way to make it work in mainline as well. However rather than
adding such platform data I guess migrating it to DT would make more
sense. But until such a migration has been completed I guess we rather
just drop enabling it for now and I will send out a v2 in that respect.????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?