public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: enable STM32 analog & timer drivers
Date: Fri, 4 May 2018 09:42:03 +0200	[thread overview]
Message-ID: <84f8b1bf-d6df-ca0e-cb3f-e5b7f7ded14b@st.com> (raw)
In-Reply-To: <CAK8P3a0maxno4S-dXoT1O5zp3NgHP2LWuGhtVoqFMMEv-tm07Q@mail.gmail.com>



On 05/04/2018 12:12 AM, Arnd Bergmann wrote:
> On Thu, May 3, 2018 at 10:05 AM, Alexandre Torgue
> <alexandre.torgue@st.com> wrote:
>> Hi Fabrice,
>>
>> On 05/02/2018 05:24 PM, Fabrice Gasnier wrote:
>>>
>>> This enables drivers for STM32 timer, low power timer and analog hardware
>>> that can be used on STM32MP1 SoC:
>>> - Timer & LP Timer MFD core, PWM, trigger & encoder drivers
>>> - IIO ADC/DAC/DFSDM
>>> - vrefbuf regu driver (voltage reference buffer).
>>>
>>> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
>>> ---
>>>    arch/arm/configs/multi_v7_defconfig | 10 ++++++++++
>>>    1 file changed, 10 insertions(+)
>>>
>>
>> Applied on stm32-next.
>>
>> Arnd,
>> Do you agree if I take multi_v7_defconfig related patches in my stm32 pull
>> requests ?
> 
> Yes, just make sure that all drivers that can reasonably be loadable
> modules are configured that way rather than as built-in, so a defconfig
> build doesn't become too big.

Ok. You're right, this drivers could be configured as module. We just 
need to verify impact before send it.

Regards
alex

> 
>         Arnd
> 

  reply	other threads:[~2018-05-04  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 15:24 [PATCH] ARM: multi_v7_defconfig: enable STM32 analog & timer drivers Fabrice Gasnier
2018-05-03 14:05 ` Alexandre Torgue
2018-05-03 22:12   ` Arnd Bergmann
2018-05-04  7:42     ` Alexandre Torgue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-03 11:22 Alexandre Torgue
2018-12-03 20:58 ` Olof Johansson

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=84f8b1bf-d6df-ca0e-cb3f-e5b7f7ded14b@st.com \
    --to=alexandre.torgue@st.com \
    --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