Export symbol from I2C eeprom driver

Trivial patch to export a symbol from the eeprom driver. Currently there are no exported symbols. The symbol lets the radeon DRM driver link to it and modprobe will then force it to load along with the radeon driver.

Quoted 4 lines · Jon Smirl

Trivial patch to export a symbol from the eeprom driver. Currently there are no exported symbols. The symbol lets the radeon DRM driver link to it and modprobe will then force it to load along with the radeon driver.

Why do you need this symbol? Or are you just saying that you need the eeprom driver loaded for some reason?

I say this as this variable is probably going to go away in the very near future, as it isn't really needed at all.

Quoted 9 lines · Greg KH

Quoted 4 lines · Jon Smirl

Trivial patch to export a symbol from the eeprom driver. Currently there are no exported symbols. The symbol lets the radeon DRM driver link to it and modprobe will then force it to load along with the radeon driver.

Why do you need this symbol? Or are you just saying that you need the eeprom driver loaded for some reason?

Quoted 2 lines

I say this as this variable is probably going to go away in the very near future, as it isn't really needed at all.

I just need a symbol to force eeprom to load, it can be any symbol. I need something for the radeon driver to link to so that modprobe will know to force eeprom to load when radeon is loaded. radeon is getting hotplug code that needs the eeprom module loaded.

And why do you need the eeprom driver for the radeon driver to work properly?

Quoted 2 lines · Greg KH

And why do you need the eeprom driver for the radeon driver to work properly?

In the new radeon driver at hotplug time a user space app reads the DDC from the monitor and sets the list of valid modes into the driver. The radeon driver includes an I2C driver. The eeprom driver finds the radeon DDC ROMs and makes them visible to the userspace driver through sysfs. I could add code to the radeon driver to export the DDC ROMs to sysfs but the eeprom driver works fine.

I don't want to load the driver from the script because the radeon driver is creating a sysfs link into the eeprom directory from the radeon one.

Quoted 3 lines

I don't want to load the driver from the script because the radeon driver is creating a sysfs link into the eeprom directory from the radeon one.

How are you getting the kobject to the eeprom directory from the radeon driver?

Quoted 7 lines · Greg KH

Quoted 3 lines

I don't want to load the driver from the script because the radeon driver is creating a sysfs link into the eeprom directory from the radeon one.

How are you getting the kobject to the eeprom directory from the radeon driver?

I own the private I2C bus and eeprom is the only chip that will attach to the bus. I need to do the link in the driver since there are four busses and upto two monitors. The driver knows how to pair the head up with the right bus.

if (dev_priv->primary_head.connector != ddc_none)
list_for_each(item,

&dev_priv->i2c[dev_priv->primary_head.connector].adapter.clients) {
    client = list_entry(item, struct i2c_client, list);
    sysfs_create_link(&dev->primary.dev_class->kobj,
&client->dev.kobj, "monitor");
    break;

}