linux-kernel - [ARM ATTEND] DT binding and support and general SOC

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>] [day] [month] [year] [list]

Message-ID: <20130801004217.GA12730@codeaurora.org>
Date:	Wed, 31 Jul 2013 17:42:17 -0700
From:	David Brown <davidb@...eaurora.org>
To:	ksummit-2013-discuss@...ts.linuxfoundation.org
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: [ARM ATTEND] DT binding and support and general SOC

Qualcomm is starting to ramp up actually contributing support for MSM
to the mainline kernel.  There are at least a couple of areas where I
see direct discussion involvement would be useful:

  - DT binding.  The Qualcomm out-of-tree code has roughly 37k lines
    of dts/dtsi files.  There has been a lot of effort here to try an
    manage/organize these bindings, but for the most part, this work
    has happened entirely internally.  As more MSM code is
    contributed, there will be a lot more bindings coming in.  I can
    bring experience with what we've done/learned with our current
    internal bindings, as well as bring feedback to more align our
    work with how the ARM bindings in general are moving.

  - SoC code structure and layout.  As ARM increases in variants (new
    CPU types, lots of SoCs, 64-bit etc), I think we should have some
    discussion of how to best organize the code.

David Brown

-- 
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
--
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/