From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ee0-f52.google.com ([74.125.83.52]:62024 "EHLO mail-ee0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754497Ab3DMPcU (ORCPT ); Sat, 13 Apr 2013 11:32:20 -0400 Received: by mail-ee0-f52.google.com with SMTP id d17so1545547eek.25 for ; Sat, 13 Apr 2013 08:32:19 -0700 (PDT) Message-ID: <51697AC8.1050807@googlemail.com> Date: Sat, 13 Apr 2013 17:33:28 +0200 From: =?UTF-8?B?RnJhbmsgU2Now6RmZXI=?= MIME-Version: 1.0 To: Mauro Carvalho Chehab CC: linux-media@vger.kernel.org Subject: Re: [PATCH 1/3] em28xx: give up GPIO register tracking/caching References: <1365846521-3127-1-git-send-email-fschaefer.oss@googlemail.com> <1365846521-3127-2-git-send-email-fschaefer.oss@googlemail.com> <20130413114144.097a21a1@redhat.com> In-Reply-To: <20130413114144.097a21a1@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-media-owner@vger.kernel.org List-ID: Am 13.04.2013 16:41, schrieb Mauro Carvalho Chehab: > Em Sat, 13 Apr 2013 11:48:39 +0200 > Frank Schäfer escreveu: > >> The GPIO register tracking/caching code is partially broken, because newer >> devices provide more than one GPIO register and some of them are even using >> separate registers for read and write access. >> Making it work would be too complicated. >> It is also used nowhere and doesn't make sense in cases where input lines are >> connected to buttons etc. >> >> Signed-off-by: Frank Schäfer >> --- >> drivers/media/usb/em28xx/em28xx-cards.c | 12 ------------ >> drivers/media/usb/em28xx/em28xx-core.c | 27 ++------------------------- >> drivers/media/usb/em28xx/em28xx.h | 6 ------ >> 3 Dateien geändert, 2 Zeilen hinzugefügt(+), 43 Zeilen entfernt(-) > ... > > >> @@ -231,14 +215,7 @@ int em28xx_write_reg_bits(struct em28xx *dev, u16 reg, u8 val, >> int oldval; >> u8 newval; >> >> - /* Uses cache for gpo/gpio registers */ >> - if (reg == dev->reg_gpo_num) >> - oldval = dev->reg_gpo; >> - else if (reg == dev->reg_gpio_num) >> - oldval = dev->reg_gpio; >> - else >> - oldval = em28xx_read_reg(dev, reg); >> - >> + oldval = em28xx_read_reg(dev, reg); >> if (oldval < 0) >> return oldval; > That's plain wrong, as it will break GPIO input. > > With GPIO, you can write either 0 or 1 to a GPIO output port. So, your > code works for output ports. > > However, an input port requires an specific value (either 1 or 0 depending > on the GPIO circuitry). If the wrong value is written there, the input port > will stop working. > > So, you can't simply read a value from a GPIO input and write it. You need > to shadow the GPIO write values instead. I don't understand what you mean. Why can I not read the value of a GPIO input and write it ? Regards, Frank > Regards, > Mauro