From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DT binding and support and general SOC
Date: Wed, 31 Jul 2013 17:42:17 -0700 [thread overview]
Message-ID: <20130801004217.GA12730@codeaurora.org> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: David Brown <davidb@codeaurora.org>
To: ksummit-2013-discuss@lists.linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DT binding and support and general SOC
Date: Wed, 31 Jul 2013 17:42:17 -0700 [thread overview]
Message-ID: <20130801004217.GA12730@codeaurora.org> (raw)
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
next reply other threads:[~2013-08-01 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 0:42 David Brown [this message]
2013-08-01 0:42 ` [ARM ATTEND] DT binding and support and general SOC David Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130801004217.GA12730@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.