LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org> To: Hans-Peter Jansen <hpj@urpla.net> Cc: Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>, linux-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com, linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl> Subject: Re: [GIT PATCHES] V4L/DVB fixes Date: Wed, 9 Jan 2008 16:30:02 -0200 [thread overview] Message-ID: <20080109163002.58cb933b@gaivota> (raw) In-Reply-To: <200801091643.52658.hpj@urpla.net> On Wed, 9 Jan 2008 16:43:51 +0100 Hans-Peter Jansen <hpj@urpla.net> wrote: > + /* The mspx4xx chips need a longer delay for some reason */ > + if (!(itv->hw_flags & IVTV_HW_MSP34XX)) > + itv->i2c_algo.udelay = 5; > + > > where the logic in hunk #1 was switched, resulting in a now misleading > comment over there. If you notice the ! at the above line, and remind that the original value for udelay is 10, you can understand the comment ;) > > How about something in the line of: > > /* > * We started with a bigger udelay in order to fulfill the needs of the > * mspx4xx chips: cut it down here for all other members of the family. > */ Your suggestion seems clearer to my eyes. Still the other possibilities are not from Micronas msp34xx family, but audio decoder chips from other vendors - as weel as other kind of i2c devices, like IR chips, video encoders, etc. So, IMO, a better comment would be something like: /* * We started with a bigger udelay in order to avoid troubles with some * msp34xx chips. Boards without msp34xx are known to work with the full * i2c 100 kHz speed. */ I'm C/C the patch author (Hans) for his comments about this, since he is the one who faced with the problems with msp34xx and ivtv. Cheers, Mauro
next prev parent reply other threads:[~2008-01-09 18:30 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-07 9:38 [GIT PATCHES] V4L/DVB fixes Mauro Carvalho Chehab 2008-01-09 15:43 ` Hans-Peter Jansen 2008-01-09 18:30 ` Mauro Carvalho Chehab [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-02-12 21:02 Mauro Carvalho Chehab 2008-01-11 21:42 Mauro Carvalho Chehab 2007-12-13 22:45 Mauro Carvalho Chehab 2007-12-12 1:05 Mauro Carvalho Chehab 2007-11-04 23:18 Mauro Carvalho Chehab 2007-10-17 17:17 Mauro Carvalho Chehab 2007-09-14 16:41 Mauro Carvalho Chehab 2007-08-23 17:04 Mauro Carvalho Chehab 2007-08-20 19:55 Mauro Carvalho Chehab 2007-07-30 19:15 Mauro Carvalho Chehab 2007-07-03 19:20 Mauro Carvalho Chehab 2007-06-09 11:13 Mauro Carvalho Chehab 2007-05-13 16:38 Mauro Carvalho Chehab 2007-03-26 3:36 Mauro Carvalho Chehab 2007-03-26 21:55 ` Linus Torvalds 2007-03-27 11:57 ` Mauro Carvalho Chehab 2007-03-27 16:24 ` Linus Torvalds
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20080109163002.58cb933b@gaivota \ --to=mchehab@infradead.org \ --cc=akpm@linux-foundation.org \ --cc=hpj@urpla.net \ --cc=hverkuil@xs4all.nl \ --cc=linux-dvb-maintainer@linuxtv.org \ --cc=linux-kernel@vger.kernel.org \ --cc=torvalds@linux-foundation.org \ --cc=video4linux-list@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).