Kernel Newbies archive on
 help / color / Atom feed
* i2c possible patch
@ 2020-07-22 10:49 Nuno Sá
  0 siblings, 0 replies; only message in thread
From: Nuno Sá @ 2020-07-22 10:49 UTC (permalink / raw)
  To: kernelnewbies

Hi all,

I was looking at the i2c core code and I stumbled in a condition that
looks like some "legacy" thing. While I'm not sure about this, this
mailing list feels like a good place to get some feedback. The
condition in question is this

So, my first question is: Can we actually get into `i2c_device_probe()`
without `i2c_device_match()` being called first? If not, it looks that
this condition could just be removed...

If we can get there without `i2c_device_match()`, I can see a problem
in the condition if we just use of_id_table in ACPI.
`i2c_acpi_match_device()` just calls `acpi_match_device()` whereas I
think `acpi_driver_match_device()` should be used if we want to take
of_id_table into account. Does this really look like an issue or Am I
missing something?

- Nuno Sá

Kernelnewbies mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-22 10:49 i2c possible patch Nuno Sá

Kernel Newbies archive on

Archives are clonable:
	git clone --mirror kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ \
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone