From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 1/1] ARM: exynos_defconfig: Enable SBS battery support
Date: Mon, 11 Aug 2014 14:52:27 +0200 [thread overview]
Message-ID: <53E8BC8B.70709@collabora.co.uk> (raw)
In-Reply-To: <1761549.yKSqfXafKr@amdc1032>
Hello Bartlomiej,
On 08/11/2014 02:40 PM, Bartlomiej Zolnierkiewicz wrote:
>> index fc7d168..c390bb9 100644
>> --- a/arch/arm/configs/exynos_defconfig
>> +++ b/arch/arm/configs/exynos_defconfig
>> @@ -77,6 +77,7 @@ CONFIG_SPI_S3C64XX=y
>> CONFIG_I2C_S3C2410=y
>> CONFIG_DEBUG_GPIO=y
>> CONFIG_POWER_SUPPLY=y
>> +CONFIG_BATTERY_SBS=m
>
> Why not make it "=y"?
>
> Rationale:
> - currently no hardware related option uses "=m" in exynos_defconfig
> - it would match the SBS option usage in multi_v7_defconfig
>
>> CONFIG_CHARGER_TPS65090=y
>> # CONFIG_HWMON is not set
>> CONFIG_THERMAL=y
>
I know but personally I think this should be changed. The idea of having a multi
platform kernel is to build a single kernel image that can be used to boot
different platforms. Not all platforms have a SBS-compliant battery so this
support shouldn't be built in the kernel image IMHO.
This also matches to what real users will do since distributions most likely
will have a minimal kernel and every possible hardware support will be enabled
as a loadable kernel module. This is what distros do for other platforms too.
If someone has a different use case and wants a kernel image that is optimized
for a particular platform then she has to create its own defconfig anyways.
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
Best regards,
Javier
next prev parent reply other threads:[~2014-08-11 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 11:06 [RESEND PATCH 1/1] ARM: exynos_defconfig: Enable SBS battery support Javier Martinez Canillas
2014-08-11 12:40 ` Bartlomiej Zolnierkiewicz
2014-08-11 12:52 ` Javier Martinez Canillas [this message]
2014-08-11 15:42 ` Bartlomiej Zolnierkiewicz
2014-08-11 15:59 ` Doug Anderson
2014-08-11 16:23 ` Javier Martinez Canillas
2014-08-11 17:28 ` Bartlomiej Zolnierkiewicz
2014-08-11 17:36 ` Doug Anderson
2014-08-11 17:38 ` Javier Martinez Canillas
2014-08-11 15:13 ` Doug Anderson
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=53E8BC8B.70709@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox