-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sensor_drivers: better way to tell if system is ACPI-based #7
Comments
@djrscally Because I wanted to avoid defining the new string ( (in if (acpi_match_device(dev->driver->acpi_match_table, dev)) {
dev_info(dev, "system is acpi-based\n");
ov7251->is_acpi_based = true;
} else
dev_info(dev, "system is not acpi-based\n"); Then, I noticed that, when Do you have any idea why? By the way, I also want to remove the current |
Huh, no - that seems pretty weird. Let me look into it for you; might not be till later on though.
The mailing list came back with a lot of changes, part of which was basically to make the code just be exported functions (I.E. have |
Thanks!
OK, I'm glad that the discussion is already taken place.
Does this mean that sensor drivers will be able to read properties from swnode? device_property_read_u32(&client->dev, "clock-frequency", &input_clk);
if (input_clk != 19200000)
return -EINVAL; |
Yes, I think they should be able to, as the call to |
Got it, thanks! |
OK, I got to the bottom of cio2-bridge breaking That means that any properties read during the sensor driver's |
OK; I think I can solve both issues by:
As I say; seems very hackish, so I'll probably ask on linux-media first. |
I see. Thanks for the investigation as always! |
Comment from me (kitakar5525)
Comment from djrscally
The text was updated successfully, but these errors were encountered: