From: Hans Hu <HansHu-oc@zhaoxin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <andi.shyti@kernel.org>,
<linux-i2c@vger.kernel.org>
Cc: <cobechen@zhaoxin.com>, <TonyWWang@zhaoxin.com>
Subject: Re: [PATCH v3] i2c: add support for Zhaoxin I2C controller
Date: Thu, 8 Jun 2023 11:08:07 +0800 [thread overview]
Message-ID: <689522d4-b7b3-59ee-685d-fa88315dbde6@zhaoxin.com> (raw)
In-Reply-To: <4c2d8675-5cc0-ec6e-f352-b032600b9469@kernel.org>
Hi Krzysztof,
On 2023/6/7 21:55, Krzysztof Kozlowski wrote:
>>>> +static int zxi2c_probe(struct platform_device *pdev)
>>>> +{
>>>> + int error;
>>>> + struct zxi2c *i2c;
>>>> + struct pci_dev *pci;
>>>> + struct device *dev;
>>>> +
>>>> + /* make sure this is zhaoxin platform */
>>> Why? How can you match to different platform?
>>>
>> In case a platform device named "IIC1D17" is also reported on
>> non-zhaoxin platform, this driver may also be registered successfully,
>> even if it shouldn't. In theory.
> Why shouldn't it be registered on other platform? It's the same device,
> isn't it?
Sorry I didn't make myself clear. I mean, if there is another
non-zhaoxin I2C device with a same reported HID name of 'IIC1D17',
this driver shouldn't it be registered. Because it's not the same device.
Thank you,
Hans
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-06-08 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 5:01 [PATCH v3] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-06-05 14:56 ` Andi Shyti
2023-06-06 6:04 ` Hans Hu
2023-06-06 8:34 ` Krzysztof Kozlowski
2023-06-07 12:33 ` Hans Hu
2023-06-07 13:55 ` Krzysztof Kozlowski
2023-06-08 3:08 ` Hans Hu [this message]
2023-06-08 6:37 ` Krzysztof Kozlowski
2023-06-08 8:50 ` Hans Hu
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=689522d4-b7b3-59ee-685d-fa88315dbde6@zhaoxin.com \
--to=hanshu-oc@zhaoxin.com \
--cc=0489dec4-cd7a-4f50-e811-d4798d514fb4@kernel.org \
--cc=TonyWWang@zhaoxin.com \
--cc=andi.shyti@kernel.org \
--cc=cobechen@zhaoxin.com \
--cc=krzk@kernel.org \
--cc=linux-i2c@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