From: Andy Gross <andy.gross@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
David Brown <david.brown@linaro.org>
Subject: Re: [PATCH] ARM: defconfig: qcom: add APQ8060 DragonBoard devices
Date: Tue, 10 Jan 2017 08:53:48 -0600 [thread overview]
Message-ID: <20170110145348.GD5710@hector.attlocal.net> (raw)
In-Reply-To: <20170110095521.14146-1-linus.walleij@linaro.org>
On Tue, Jan 10, 2017 at 10:55:21AM +0100, Linus Walleij wrote:
> This default-enables the devices found on the APQ8060 DragonBoard
> in the qcom_defconfig:
>
> - EBI2 bus
> - SMSC911x ethernet
> - LEDs class and PM8058 LEDs driver, trigger and heartbeat
> trigger (so we get heartbeat on the board by default)
> - IIO framework, including the HRTimer trigger, KXSD9
> accelerometer, MPU3050 gyroscope, AK8975 magnetometer and
> BMP085 pressure sensor
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This brings up a point of discussion. Do we even need the qcom_defconfig any
more? Is everyone comfortable with using the multi_v7_defconfig?
Aside from size of the image, i can't think of any other reason to keep around
the separate qcom file.
Regards,
Andy
WARNING: multiple messages have this Message-ID (diff)
From: andy.gross@linaro.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: defconfig: qcom: add APQ8060 DragonBoard devices
Date: Tue, 10 Jan 2017 08:53:48 -0600 [thread overview]
Message-ID: <20170110145348.GD5710@hector.attlocal.net> (raw)
In-Reply-To: <20170110095521.14146-1-linus.walleij@linaro.org>
On Tue, Jan 10, 2017 at 10:55:21AM +0100, Linus Walleij wrote:
> This default-enables the devices found on the APQ8060 DragonBoard
> in the qcom_defconfig:
>
> - EBI2 bus
> - SMSC911x ethernet
> - LEDs class and PM8058 LEDs driver, trigger and heartbeat
> trigger (so we get heartbeat on the board by default)
> - IIO framework, including the HRTimer trigger, KXSD9
> accelerometer, MPU3050 gyroscope, AK8975 magnetometer and
> BMP085 pressure sensor
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This brings up a point of discussion. Do we even need the qcom_defconfig any
more? Is everyone comfortable with using the multi_v7_defconfig?
Aside from size of the image, i can't think of any other reason to keep around
the separate qcom file.
Regards,
Andy
next prev parent reply other threads:[~2017-01-10 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 9:55 [PATCH] ARM: defconfig: qcom: add APQ8060 DragonBoard devices Linus Walleij
2017-01-10 9:55 ` Linus Walleij
2017-01-10 14:53 ` Andy Gross [this message]
2017-01-10 14:53 ` Andy Gross
2017-01-11 13:19 ` Linus Walleij
2017-01-11 13:19 ` Linus Walleij
2017-01-11 14:08 ` Arnd Bergmann
2017-01-11 14:08 ` Arnd Bergmann
2017-01-11 14:11 ` Neil Armstrong
2017-01-11 14:11 ` Neil Armstrong
2017-01-11 16:03 ` Andy Gross
2017-01-11 16:03 ` Andy Gross
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=20170110145348.GD5710@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=sboyd@codeaurora.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.