StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POwhen to use platform_driver over I2C?
primarykey
Id
8212746
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-21T13:41:28.337
FavoriteCount
2
LastActivityDate
2011-11-21T13:53:54.623
LastEditDate
2011-11-21T13:43:17.530
LastEditorUserId
1043165
OwnerUserId
1034915
ParentId
0
PostTypeId
1
Score
1
ViewCount
1215
LastEditorDisplayName
text
Body
<p>I am looking a code xxx device is an IC using I2C to communicate. Somehow it is written using platform device. To communicate with the IC it is using "microp_i2c_write()"(pls refer to the following function write_xxx_register()). I think this code is hard to maintain in different platform. this is a navigation product.</p> <p>Question: 1. I believe my question is how can I include the struct i2c_client *client? into this scenario? So this way it is easier to port to different linux/ andriod kernel? 2. Why & when platform_driver preferred? any particular reason?</p> <pre><code>static struct platform_driver xxx_device_driver = { .probe = xxx_probe, .remove = __devexit_p(xxx_remove), .driver = { .name = XXX_NAME, .owner = THIS_MODULE, } }; static void write_xxx_register(uint8_t reg, uint8_t val) { uint8_t data[BURST_DATA_SIZE]; data[0] = reg; data[1] = val; microp_i2c_write(OJ_REGISTER_WRITE, data, 2); } static int __devinit XXX_probe(struct platform_device *pdev) { struct XXX_platform_data *oj = pdev->dev.platform_data; int err; int i; err = -ENOMEM; my_oj = oj; INIT_WORK(&oj->work, XXX_work_func); XXX__wq = create_singlethread_workqueue("XXX__wq"); if (!XXX__wq) { err = -ENOMEM; goto fail; } oj->input_dev = input_allocate_device(); if (!oj->input_dev) { printk(KERN_ERR "Unable to allocate device for OJ\n"); err = -ENOMEM; goto fail; } oj->input_dev->name = "XXX_-oj"; oj->input_dev->evbit[0] = BIT_MASK(EV_KEY) | BIT_MASK(EV_ABS)| BIT_MASK(EV_SYN )|BIT_MASK(EV_REL) ; input_set_capability(oj->input_dev, EV_KEY, BTN_MOUSE); input_set_capability(oj->input_dev, EV_KEY, BTN_TOUCH); oj->input_dev->relbit[0] = BIT_MASK(REL_X) | BIT_MASK(REL_Y); oj->input_dev->absbit[0] = BIT_MASK(ABS_X) | BIT_MASK(ABS_Y); input_set_abs_params(oj->input_dev, ABS_X, 8, 4024-8 , 0, 0); input_set_abs_params(oj->input_dev, ABS_Y, 41, 6604-41, 0, 0); input_set_abs_params(oj->input_dev, ABS_PRESSURE, 0, 255, 0, 0); input_set_abs_params(oj->input_dev, ABS_TOOL_WIDTH, 0, 15, 0, 0); input_set_abs_params(oj->input_dev, ABS_HAT0X, 8, 4024-8, 0, 0); input_set_abs_params(oj->input_dev, ABS_HAT0Y, 41, 6604-41, 0, 0); input_set_abs_params(oj->input_dev, ABS_MT_POSITION_X, 8, 4024-8, 0, 0); input_set_abs_params(oj->input_dev, ABS_MT_POSITION_Y, 41, 6604-41, 0, 0); input_set_abs_params(oj->input_dev, ABS_MT_TOUCH_MAJOR, 0, 255, 0, 0); input_set_abs_params(oj->input_dev, ABS_MT_WIDTH_MAJOR, 0, 15, 0, 0); set_bit(EV_SYN, oj->input_dev->evbit); set_bit(EV_KEY, oj->input_dev->evbit); set_bit(BTN_TOUCH, oj->input_dev->keybit); set_bit(EV_ABS, oj->input_dev->evbit); for(i = 0; i < ARRAY_SIZE(keymap); i++) set_bit(keymap[i], oj->input_dev->keybit); err = input_register_device(oj->input_dev); if (err) { printk(KERN_ERR "Unable to register %s input device\n", oj->input_dev->name); goto fail; } err = request_irq(my_oj->irq, XXX_irq_handler, IRQF_TRIGGER_NONE, XXX_NAME, oj); if (err < 0) { err = -ENOMEM; printk(KERN_ERR "request_irq failed\n"); goto fail; } normal_th = my_oj->normal_th; xy_ratio = my_oj->xy_ratio; interval = my_oj->interval; polling_delay = my_oj->mdelay_time; debugflag = my_oj->debugflag; ap_code = my_oj->ap_code; printk(KERN_INFO "driver loaded\n"); return 0; } </code></pre>
Tags
<linux-kernel><i2c>
Title
when to use platform_driver over I2C?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMartijn
UserOwnerUserId
1. UShumpingpanda
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POwhen to use platform_driver over I2C?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POwhen to use platform_driver over I2C?
  UserUserId
  USSylvain Huard
  VoteTypeVoteTypeId
  VTFavorite
3. VO
  singulars
  PostPostId
  POwhen to use platform_driver over I2C?
  UserUserId
  UShjsblogger
  VoteTypeVoteTypeId
  VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.