Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751687AbaBGJOP (ORCPT ); Fri, 7 Feb 2014 04:14:15 -0500 Received: from 11.mo1.mail-out.ovh.net ([188.165.48.29]:49850 "EHLO mo1.mail-out.ovh.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751381AbaBGJOL (ORCPT ); Fri, 7 Feb 2014 04:14:11 -0500 Date: Fri, 7 Feb 2014 09:37:19 +0100 From: Jean-Christophe PLAGNIOL-VILLARD To: Nicolas Ferre Cc: Bo Shen , Felipe Balbi , Greg Kroah-Hartman , linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] USB: at91: fix the number of endpoint parameter Message-ID: <20140207083719.GY9558@ns203013.ovh.net> References: <1389927565-22477-1-git-send-email-voice.shen@atmel.com> <20140118052059.GL9558@ns203013.ovh.net> <52DC9A66.6080009@atmel.com> <20140121054932.GO9558@ns203013.ovh.net> <52DE2C05.9060800@atmel.com> <52DE389B.3000702@atmel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52DE389B.3000702@atmel.com> X-PGP-Key: http://uboot.jcrosoft.org/plagnioj.asc X-PGP-key-fingerprint: 6309 2BBA 16C8 3A07 1772 CC24 DEFC FFA3 279C CE7C User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 11164986426370993004 X-Ovh-Remote: 91.121.171.124 (ns203013.ovh.net) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: -100 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejtddrjedvucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd X-Spam-Check: DONE|U 0.5/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejtddrjeehucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10:06 Tue 21 Jan , Nicolas Ferre wrote: > On 21/01/2014 09:12, Bo Shen : > > Hi J, > > > > On 01/21/2014 01:49 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > >> On 11:39 Mon 20 Jan , Bo Shen wrote: > >>> Hi J, > >>> > >>> On 01/18/2014 01:20 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > >>>> On 10:59 Fri 17 Jan , Bo Shen wrote: > >>>>> In sama5d3 SoC, there are 16 endpoints. As the USBA_NR_ENDPOINTS > >>>>> is only 7. So, fix it for sama5d3 SoC using the udc->num_ep. > >>>>> > >>>>> Signed-off-by: Bo Shen > >>>>> --- > >>>>> > >>>>> drivers/usb/gadget/atmel_usba_udc.c | 2 +- > >>>>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>>>> > >>>>> diff --git a/drivers/usb/gadget/atmel_usba_udc.c b/drivers/usb/gadget/atmel_usba_udc.c > >>>>> index 2cb52e0..7e67a81 100644 > >>>>> --- a/drivers/usb/gadget/atmel_usba_udc.c > >>>>> +++ b/drivers/usb/gadget/atmel_usba_udc.c > >>>>> @@ -1670,7 +1670,7 @@ static irqreturn_t usba_udc_irq(int irq, void *devid) > >>>>> if (ep_status) { > >>>>> int i; > >>>>> > >>>>> - for (i = 0; i < USBA_NR_ENDPOINTS; i++) > >>>>> + for (i = 0; i < udc->num_ep; i++) > >>>> > >>>> no the limit need to specified in the driver as a checkpoint by the compatible > >>>> or platform driver id > >>> > >>> You mean, we should not trust the data passed from dt node or > >>> platform data? Or do you think we should do double confirm? > >> > >> no base on the driver name or the compatible you will known the MAX EP > >> > >> not based on the dt ep description > >> > >> as we do on pinctrl-at91 > > > > I am sorry, I am not fully get it after reading the code of > > pinctrl-at91.c, can you give the example code in pinctrl-at91.c? > > > > Btw, the udc->num_ep is get from the following code. > > for dt > > --->8--- > > while ((pp = of_get_next_child(np, pp))) > > udc->num_ep++; > > ---<8--- > > > > for non-dt > > --->8--- > > udc->num_ep = pdata->num_ep; > > ---8<--- > > It seems to me pretty valid to use num_ep in this driver and not have to > rely on another compatibility string just for this. > The information is here, it is retrieved pretty cleanly so I vote for a > simple use of it: if we introduce another information we will have to > double check the cross errors that would happen... here is the key point you describe the HW so choose detect the IP version and then check we do not describe too many EP or you prove the correct compatible so we known this not the same IP and we can check the DT information Best Regards, J. > > Bye, > > >>>>> if (ep_status & (1 << i)) { > >>>>> if (ep_is_control(&udc->usba_ep[i])) > >>>>> usba_control_irq(udc, &udc->usba_ep[i]); > >>>>> -- > >>>>> 1.8.5.2 > >>>>> > >>> > >>> Best Regards, > >>> Bo Shen > > > > Best Regards, > > Bo Shen > > > > > -- > Nicolas Ferre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/