public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
	alexandre.belloni@free-electrons.com, a.zummo@towertech.it
Cc: cw00.choi@samsung.com, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, javier@osg.samsung.com,
	rklein@nvidia.com
Subject: Re: [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP
Date: Wed, 02 Mar 2016 13:28:38 +0900	[thread overview]
Message-ID: <56D66BF6.60403@samsung.com> (raw)
In-Reply-To: <56D667AC.5030400@nvidia.com>

On 02.03.2016 13:10, Laxman Dewangan wrote:
> 
> On Wednesday 02 March 2016 09:22 AM, Krzysztof Kozlowski wrote:
>> On 02.03.2016 11:15, Laxman Dewangan wrote:
>>
>>>>> (kernel_ulong_t)&max77802_drv_data, },
>>>>> +    { "max77620-rtc", .driver_data =
>>>>> (kernel_ulong_t)&max77620_drv_data, },
>>>>> +    { "max20024-rtc", .driver_data =
>>>>> (kernel_ulong_t)&max77620_drv_data, },
>>>> There shouldn't be "max20024-rtc". This is exactly the same as
>>>> "max77620-rtc" so re-use existing id. No point of duplicating device
>>>> names for 100% compatible devices.
>>>>
>>>>
>>> I am thinking that having compatible for each device which it supports
>>> is better.
>>>
>>> In MFD, I have made all sub module of max20024 as max20024-<module>.
>>> I have not mixed the sub module name for max20024 with max77620 module.
>> The point of compatible is to be... compatible so you don't create
>> compatibles for the same meaning!
>>
>> However this is actually not a compatible but a matching name... which
>> should follow the same idea. You did not give any argument why this is
>> better.
> 
> My point is that if any driver supporting the any devices then it should
> be there in their compatibility although other everything is same.

Nope. The driver can describe supported devices in comment, Kconfig,
module description, DT binding description but the compatible is one.
One compatible for all compatible devices.

> This way, it is easy to find that the driver is available for the device
> or not. Also easy way to tell that someone has invested time to find out
> the driver corresponding to device and he confirmed that this driver is
> compatible with that device.
> Otherwise, it is difficult to quickly find out the driver whether this
> is available/support or not for given device.

This is so specific, imaginated use case... Regular users don't write
DTS. This is strictly for developers and the engineer who develops
code/platforms using maxim devices has this problem? No way...

You want to create many artificial device ids for the same compatible
device just to make grepping easier for someone (I cannot even find out
for whom...)? Nooo, that is just wrong. These are the same
blocks/subdevices. They use the same driver. They should use the same
compatible or the same name of driver.

Best regards,
Krzysztof

  reply	other threads:[~2016-03-02  4:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 12:58 [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP Laxman Dewangan
2016-02-29 12:58 ` [PATCH 2/2] rtc: max77686: Use REGMAP_IRQ_REG for regmap-rtc-irqs initialisation Laxman Dewangan
2016-03-02  1:00   ` Krzysztof Kozlowski
2016-03-02  2:04     ` Laxman Dewangan
2016-03-02  3:45       ` Krzysztof Kozlowski
2016-03-02  0:58 ` [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP Krzysztof Kozlowski
2016-03-02  2:15   ` Laxman Dewangan
2016-03-02  3:52     ` Krzysztof Kozlowski
2016-03-02  4:10       ` Laxman Dewangan
2016-03-02  4:28         ` Krzysztof Kozlowski [this message]
2016-03-02  6:01           ` Laxman Dewangan

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=56D66BF6.60403@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=cw00.choi@samsung.com \
    --cc=javier@osg.samsung.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rklein@nvidia.com \
    --cc=rtc-linux@googlegroups.com \
    /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