--- v6
+++ v4
@@ -1,34 +1,20 @@
 This allows userspace to more easily distinguish which bus a particular
 atmel_mxt_ts device is attached to.
 
-The resulting phys will be something like:
- i2c-1-0067/input0
-
 Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
 ---
- drivers/input/touchscreen/atmel_mxt_ts.c |    5 +++++
- 1 files changed, 5 insertions(+), 0 deletions(-)
+ drivers/input/touchscreen/atmel_mxt_ts.c |    1 +
+ 1 files changed, 1 insertions(+), 0 deletions(-)
 
 diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
-index 42e6450..b1108ca 100644
+index 42e6450..eda9eed 100644
 --- a/drivers/input/touchscreen/atmel_mxt_ts.c
 +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
-@@ -250,6 +250,7 @@ struct mxt_finger {
- struct mxt_data {
- 	struct i2c_client *client;
- 	struct input_dev *input_dev;
-+	char phys[64];		/* device physical location */
- 	const struct mxt_platform_data *pdata;
- 	struct mxt_object *object_table;
- 	struct mxt_info info;
-@@ -1106,6 +1107,10 @@ static int __devinit mxt_probe(struct i2c_client *client,
+@@ -1106,6 +1106,7 @@ static int __devinit mxt_probe(struct i2c_client *client,
  	}
  
  	input_dev->name = "Atmel maXTouch Touchscreen";
-+	snprintf(data->phys, sizeof(data->phys), "i2c-%u-%04x/input0",
-+		 client->adapter->nr, client->addr);
-+	input_dev->phys = data->phys;
-+
++	input_dev->phys = client->adapter->name;
  	input_dev->id.bustype = BUS_I2C;
  	input_dev->dev.parent = &client->dev;
  	input_dev->open = mxt_input_open;