linux-kernel - Re: [PATCH v2 00/11] Improvements to Tegra-based Chromebook support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEUnVG4t3gGFv9SNY=LZwUuLsEgNUts6Q0oXsEO_OtR9W3s7Xg@mail.gmail.com>
Date:	Thu, 15 Jan 2015 08:43:57 -0800
From:	Dylan Reid <dgreid@...omium.org>
To:	Tomeu Vizoso <tomeu.vizoso@...labora.com>
Cc:	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Simon Glass <sjg@...omium.org>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 00/11] Improvements to Tegra-based Chromebook support

On Thu, Jan 15, 2015 at 8:12 AM, Tomeu Vizoso
<tomeu.vizoso@...labora.com> wrote:
> Hi,
>
> this started as adding support for the Nyan Blaze, but the Big is so similar to it that I thought it would be better to have both in the same series.
>
> With these changes, I get wifi, trackpad, audio playback and recording (with the internal mic) working in both machines.
>
> Patches 2 and 7 use the pinmux data as generated by tegra-pinmux-scripts. I will be sending patches adding the configs for the boards to it. I have chosen to copy the whole pinmux data to each leaf .dts even if they are very similar because it will be easier that way to check in the future that they match the canonical data in tegra-pinmux-scripts.
>
> Patch 3 changes the nvidia,model of the sound card, so that the exposed card name is GoogleNyan instead of just "A13" as it was before. I'm leaning towards having just one UCM config for both machines, but I'm not totally convinced of it and would love to hear other opinions.

ChromeOS uses one config for both.  The only audio difference between
these two boards is the speakers, that isn't represented in UCM, so
one config file is fine.

>
> Patches 8 and 9 depend on Ulf's pwrseq series [0].
>
> http://cgit.collabora.com/git/user/tomeu/linux.git/log/?h=nyan-v2
>
> [0] http://thread.gmane.org/gmane.linux.kernel.mmc/30611
>
> Stéphane Marchesin (1):
>   drm/panel: add support for Samsung LTN140AT29 panel
>
> Tomeu Vizoso (10):
>   ARM: tegra: Add node for trackpad in Nyan boards
>   ARM: tegra: Use the generated pinmux data
>   ARM: tegra: Set the sound card model that alsaucm expects
>   ARM: tegra: Set spi-max-frequency property to flash node
>   ARM: tegra: Move out nyan-generic parts out from the nyan-big DT
>   ARM: tegra: Add DTS for the nyan-blaze board
>   mmc: pwrseq_simple: Add support for a delay
>   ARM: tegra: Use pwrseq-simple for the wifi in Nyan
>   ASoC: tegra: Add a control for the headphone switch
>   ASoC: tegra: add sink for the internal mic to tegra_max98090
>
>  .../devicetree/bindings/mmc/mmc,pwrseq-simple.txt  |    2 +
>  .../bindings/sound/nvidia,tegra-audio-max98090.txt |    1 +
>  arch/arm/boot/dts/Makefile                         |    1 +
>  arch/arm/boot/dts/tegra124-nyan-big.dts            | 2112 +++++++++++---------
>  arch/arm/boot/dts/tegra124-nyan-blaze.dts          | 1325 ++++++++++++
>  arch/arm/boot/dts/tegra124-nyan.dtsi               |  692 +++++++
>  drivers/gpu/drm/panel/panel-simple.c               |   26 +
>  drivers/mmc/core/pwrseq_simple.c                   |    8 +
>  sound/soc/tegra/tegra_max98090.c                   |    3 +
>  9 files changed, 3209 insertions(+), 961 deletions(-)
>  create mode 100644 arch/arm/boot/dts/tegra124-nyan-blaze.dts
>  create mode 100644 arch/arm/boot/dts/tegra124-nyan.dtsi
>
> --
> 1.9.3
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/