mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Ariana.Lazar@microchip.com, robh@kernel.org, krzk+dt@kernel.org,
	jic23@kernel.org, nuno.sa@analog.com, conor+dt@kernel.org,
	andy@kernel.org
Cc: Jonathan.Cameron@huawei.com, Conor.Dooley@microchip.com,
	devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: dac: mcp47feb02: add MCP48FEB02 SPI driver to MCP47FEB02 I2C driver
Date: Tue, 14 Apr 2026 10:48:10 -0500	[thread overview]
Message-ID: <16816b5d-2316-43be-99ca-6b54d4326371@baylibre.com> (raw)
In-Reply-To: <4b289795ffe7ce3505087446a5f2aee053ace561.camel@microchip.com>

On 4/14/26 10:28 AM, Ariana.Lazar@microchip.com wrote:
> Hi David,
> 
>>> --- a/drivers/iio/dac/Makefile
>>> +++ b/drivers/iio/dac/Makefile
>>> @@ -54,6 +54,9 @@ obj-$(CONFIG_MAX5821) += max5821.o
>>>  obj-$(CONFIG_MCP4725) += mcp4725.o
>>>  obj-$(CONFIG_MCP4728) += mcp4728.o
>>>  obj-$(CONFIG_MCP47FEB02) += mcp47feb02.o
>>
>> Shouldn't we be removing this old file?
>>
>> The patch series would be eaiser to understand if it was split into
>> one commit to split the existing driver into two files and then
>> another commit to add support for the new parts.
>>
>>
>>> +mcp47feb02-objs := mcp47feb02-core.o

Ah, I missed this line.

>>> +obj-$(CONFIG_MCP47FEB02_I2C) += mcp47feb02-i2c.o
>>> +obj-$(CONFIG_MCP47FEB02_SPI) += mcp47feb02-spi.o
>>>  obj-$(CONFIG_MCP4821) += mcp4821.o
>>>  obj-$(CONFIG_MCP4922) += mcp4922.o
>>>  obj-$(CONFIG_STM32_DAC_CORE) += stm32-dac-core.o
>>
> 
> Thank you for the review.
> 
> I kept that line so the core module would compile as 'mcp47feb02.ko'.
> If you prefer, I can rename the core file to mcp47feb02.c and add just
> the lines for the SPI and I2C modules in the Makefile.

It looks like there is only a few other driver that implement
it the way you have. And only a few others that don't have "core"
in the C file name.

> 
> Another option would be to keep the core module named mcp47feb02-core.c
> and compile it as 'mcp47feb02-core.ko'.

It looks like this is the option most other drivers go with. So unless
there is a good reason to do otherwise, I would tend to go with the
most common pattern.

> 
> Best regards,
> Ariana


  reply	other threads:[~2026-04-14 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 10:50 [PATCH 0/2] Add support for Microchip MCP48F(E/V)B(0/1/2)(1/2/4/8) on MCP47F(E/V)B(0/1/2)(1/2/4/8) Ariana Lazar
2026-04-03 10:50 ` [PATCH 1/2] dt-bindings: iio: dac: add support for Microchip MCP48FEB02 to MCP47FEB02 Ariana Lazar
2026-04-03 11:32   ` Conor Dooley
2026-04-14 13:39     ` Ariana.Lazar
2026-04-14 15:34       ` Conor Dooley
2026-04-03 12:25   ` Rob Herring (Arm)
2026-04-04 13:43   ` David Lechner
2026-04-03 10:50 ` [PATCH 2/2] iio: dac: mcp47feb02: add MCP48FEB02 SPI driver to MCP47FEB02 I2C driver Ariana Lazar
2026-04-04 13:49   ` David Lechner
2026-04-08 20:22     ` Andy Shevchenko
2026-04-14 15:28     ` Ariana.Lazar
2026-04-14 15:48       ` David Lechner [this message]
2026-04-19 16:16   ` Jonathan Cameron

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=16816b5d-2316-43be-99ca-6b54d4326371@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=Ariana.Lazar@microchip.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@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®