public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>, Hans Hu <hanshu-oc@zhaoxin.com>
Cc: linux-i2c@vger.kernel.org, cobechen@zhaoxin.com, TonyWWang@zhaoxin.com
Subject: Re: [PATCH v4] i2c: add support for Zhaoxin I2C controller
Date: Fri, 9 Jun 2023 15:11:04 +0200	[thread overview]
Message-ID: <01ddc13a-8be1-2b1f-4986-0218fa9c3324@kernel.org> (raw)
In-Reply-To: <20230609122414.l2pcuwv5foclkxea@intel.intel>

On 09/06/2023 14:24, Andi Shyti wrote:
>> +
>> +static int zxi2c_probe(struct platform_device *pdev)
>> +{
>> +	int err = 0;
>> +	struct zxi2c *i2c;
>> +	struct pci_dev *pci;
>> +	struct device *dev;
>> +
>> +	/* make sure this is zhaoxin platform */
> 
> Krzysztof is asking what does this mean? I guess here you are
> checking if the device connected is really the zhaixin plaform of
> this driver. Makes sense. Just to avoid misunderstandings we
> could rephrase this with something like:
> 
> 	/*
> 	 * Check if vendor and device ID match the expected
> 	 * values for the zhaoxin platform
> 	 */
> 
> would it work?

I don't understand why does it make sense. Only correct devices are
matched, right? So either this is impossible condition or  this is
plugged into other proper platform. In both cases you should not have
such checks.

Why would ever a driver check in probe what platform it is?

Best regards,
Krzysztof


  reply	other threads:[~2023-06-09 13:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  3:16 [PATCH v4] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-06-09  9:33 ` Krzysztof Kozlowski
2023-06-12  3:31   ` Hans Hu
2023-06-09 12:24 ` Andi Shyti
2023-06-09 13:11   ` Krzysztof Kozlowski [this message]
2023-06-12  8:24   ` Hans Hu
2023-06-09 12:47 ` Andi Shyti
2023-06-14  7:34 ` [PATCH v5] " Hans Hu
2023-06-14  8:21   ` Andi Shyti
2023-06-14  9:48   ` [PATCH v6] " Hans Hu
2023-06-23  8:47     ` Wolfram Sang
2023-06-25 10:57       ` Hans Hu
2023-06-30  8:01         ` Andi Shyti
     [not found]           ` <6f3479fb79944d5a8b4a562d67c82a4b@zhaoxin.com>
     [not found]             ` <1abb34e5cbe74514911598a5a522045b@zhaoxin.com>
2023-07-06  7:25               ` Hans Hu
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09  2:55 [PATCH v4] " 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=01ddc13a-8be1-2b1f-4986-0218fa9c3324@kernel.org \
    --to=krzk@kernel.org \
    --cc=TonyWWang@zhaoxin.com \
    --cc=andi.shyti@kernel.org \
    --cc=cobechen@zhaoxin.com \
    --cc=hanshu-oc@zhaoxin.com \
    --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