From: Sekhar Nori <nsekhar@ti.com>
To: David Lechner <david@lechnology.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: Kevin Hilman <khilman@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: davinci_all_defconfig: Enable Bluetooth
Date: Fri, 29 Jun 2018 19:30:11 +0530 [thread overview]
Message-ID: <b4c41d75-d253-c92e-8d3e-d9b83f0337f9@ti.com> (raw)
In-Reply-To: <0525829c-3070-6aee-39cf-1154dcbb1e75@lechnology.com>
On Wednesday 27 June 2018 10:43 PM, David Lechner wrote:
> On 06/27/2018 06:11 AM, Sekhar Nori wrote:
>> On Friday 01 June 2018 01:55 AM, David Lechner wrote:
>>> This enables Bluetooth modules in davinic_all_defconfig needed for LEGO
>>
>> davinci_all_defconfig
>>
>>> MINDSTORMS EV3.
>>>
>>> Signed-off-by: David Lechner <david@lechnology.com>
>>> ---
>>> arch/arm/configs/davinci_all_defconfig | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>
>>> +CONFIG_SERIAL_DEV_BUS=y
>>
>> Any reason to build this into the kernel?
>>
>
> Yes:
>
>
> config SERIAL_DEV_CTRL_TTYPORT
> bool "Serial device TTY port controller"
> help
> Say Y here if you want to use the Serial device bus with common TTY
> drivers (e.g. serial drivers).
>
> If unsure, say Y.
> depends on TTY
> depends on SERIAL_DEV_BUS != m
Patch applied to v4.19/defconfig. I added a note about this to commit
text in case I wonder again at a later time.
Thanks,
Sekhar
next prev parent reply other threads:[~2018-06-29 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 20:25 [PATCH 0/2] ARM: LEGO MINDSTORMS EV3 Bluetooth support David Lechner
2018-05-31 20:25 ` [PATCH 1/2] ARM: dts: da850-lego-ev3: Add Bluetooth nodes David Lechner
2018-06-27 11:12 ` Sekhar Nori
2018-05-31 20:25 ` [PATCH 2/2] ARM: davinci_all_defconfig: Enable Bluetooth David Lechner
2018-06-27 11:11 ` Sekhar Nori
2018-06-27 17:13 ` David Lechner
2018-06-29 14:00 ` Sekhar Nori [this message]
2018-06-26 16:51 ` [PATCH 0/2] ARM: LEGO MINDSTORMS EV3 Bluetooth support David Lechner
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=b4c41d75-d253-c92e-8d3e-d9b83f0337f9@ti.com \
--to=nsekhar@ti.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®