public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Greg KH <greg@kroah.com>
Cc: Joachim Foerster <joachim.foerster@missinglinkelectronics.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: ISP1760: Add flags for interrupt polarity and edge/level trigger
Date: Wed, 14 Dec 2011 08:57:33 +0100	[thread overview]
Message-ID: <5171961.tdOaMPUdsK@ws-stein> (raw)
In-Reply-To: <20111213180010.GA29980@kroah.com>

On Tuesday 13 December 2011 10:00:10 Greg KH wrote:
> On Tue, Dec 13, 2011 at 10:33:13AM +0100, Alexander Stein wrote:
> > Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> > ---
> > 
> >  drivers/usb/host/isp1760-if.c |    4 ++++
> >  include/linux/usb/isp1760.h   |    2 ++
> >  2 files changed, 6 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/usb/host/isp1760-if.c
> > b/drivers/usb/host/isp1760-if.c index a7dc1e1..0ef9867 100644
> > --- a/drivers/usb/host/isp1760-if.c
> > +++ b/drivers/usb/host/isp1760-if.c
> > @@ -388,6 +388,10 @@ static int __devinit isp1760_plat_probe(struct
> > platform_device *pdev)> 
> >  			devflags |= ISP1760_FLAG_DACK_POL_HIGH;
> >  		
> >  		if (priv->dreq_polarity_high)
> >  		
> >  			devflags |= ISP1760_FLAG_DREQ_POL_HIGH;
> > 
> > +		if (priv->interrupt_polarity_high)
> > +			devflags |= ISP1760_FLAG_INTR_POL_HIGH;
> > +		if (priv->interrupt_edge_triggered)
> > +			devflags |= ISP1760_FLAG_INTR_EDGE_TRIG;
> > 
> >  	}
> >  	
> >  	hcd = isp1760_register(mem_res->start, mem_size, irq_res->start,
> > 
> > diff --git a/include/linux/usb/isp1760.h b/include/linux/usb/isp1760.h
> > index de7de53..c5edbc8 100644
> > --- a/include/linux/usb/isp1760.h
> > +++ b/include/linux/usb/isp1760.h
> > @@ -13,6 +13,8 @@ struct isp1760_platform_data {
> > 
> >  	unsigned analog_oc:1;			/* Analog overcurrent */
> >  	unsigned dack_polarity_high:1;		/* DACK active high */
> >  	unsigned dreq_polarity_high:1;		/* DREQ active high */
> > 
> > +	unsigned interrupt_polarity_high:1;
> > +	unsigned interrupt_edge_triggered:1;
> 
> So you added these, and you check them, but who sets them?  What is the
> point of this patch at this point in time?

These platform data bits are set by board configurations, which is completly 
optional. So currently maybe noone sets/use it, but in future someone may need 
it. Also dreq_polarity_high is also there and I only found board files setting 
them to 0... So why not add the feature bits too?

Regards,
Alexander


  reply	other threads:[~2011-12-14  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  9:33 [PATCH] ISP1760: Add flags for interrupt polarity and edge/level trigger Alexander Stein
2011-12-13 18:00 ` [PATCH] USB: " Greg KH
2011-12-14  7:57   ` Alexander Stein [this message]
2011-12-14 16:10     ` Greg KH

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=5171961.tdOaMPUdsK@ws-stein \
    --to=alexander.stein@systec-electronic.com \
    --cc=grant.likely@secretlab.ca \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=joachim.foerster@missinglinkelectronics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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: link
Be 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