All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: 'Michal Nazarewicz' <mina86@mina86.com>,
	Krzysztof Opasiak <k.opasiak@samsung.com>
Cc: balbi@ti.com, jackp@codeaurora.org, pheatwol@codeaurora.org,
	linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	benoit@android.com, Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
	gregkh@linuxfoundation.org,
	'Manu Gautam' <mgautam@codeaurora.org>,
	Karol Lewandowski <k.lewandowsk@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: RE: [PATCHv2] usb: gadget: f_fs: Add flags to descriptors block
Date: Thu, 05 Jun 2014 13:32:35 +0200	[thread overview]
Message-ID: <008201cf80b1$d9efc590$8dcf50b0$%opasiak@samsung.com> (raw)
In-Reply-To: <xa1tk38wlck3.fsf@mina86.com>

Hi,

> -----Original Message-----
> From: Michal Nazarewicz [mailto:mpn@google.com] On Behalf Of Michal
> Nazarewicz
> Sent: Wednesday, June 04, 2014 9:06 PM
> To: Krzysztof Opasiak; 'Manu Gautam'
> Cc: balbi@ti.com; jackp@codeaurora.org; pheatwol@codeaurora.org;
> linux-usb@vger.kernel.org; linux-arm-msm@vger.kernel.org;
> benoit@android.com; Andrzej Pietrasiewicz;
> gregkh@linuxfoundation.org; 'Manu Gautam'; Karol Lewandowski; Marek
> Szyprowski
> Subject: Re: [PATCHv2] usb: gadget: f_fs: Add flags to descriptors
> block
> 
> >> -struct usb_functionfs_descs_head {
> >> -	__le32 magic;
> >> -	__le32 length;
> >> -	__le32 fs_count;
> >> -	__le32 hs_count;
> >> -} __attribute__((packed));
> 
> On Wed, Jun 04 2014, Krzysztof Opasiak <k.opasiak@samsung.com>
> wrote:
> > I have tried to compile FFS examples with v3.15-rc8 but I have
> faced an
> > issue that they are unable to build due to missing definition of
> this
> > structure.
> 
> https://lkml.org/lkml/2014/5/21/522

Thank you for this link, I have missed that patch.

> I don't care either way to be honest.  I guess if there's non-
> negligible
> number of usb_functionfs_descs_head structure users out there, I
> can
> prepare a CL adding the structure back.

The number of FFS users which I know is limited to 3 maybe 4, so it's not too much. I can port all of them to new API but I'm not sure if we would like to do this?

> 
> > There is also no structure definition for new API, maybe suitable
> > structure should be defined (struct usb_functionfs_descs_head2
> for
> > example) to make userspace life easier?
> 
> That structure would not have many fields though, since what
> exactly the
> header contains depends on the flags.  Whether fs_count, hs_count
> and
> ss_count fields are present depends on which bits in the flags are
> set.
> So the usb_functionfs_descs_head2 structure could only contain:
> 
> 	struct usb_functionfs_descs_head2 {
> 		__le32 magic;
> 		__le32 length;
> 		__le32 flags;
> 	};
> 
> I'm not sure if that would be particularly helpful.

I think that this structure is much more user friendly than copy-paste of those 3 fields in each ffs program.

-- 
BR's
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
k.opasiak@samsung.com

      reply	other threads:[~2014-06-05 11:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  9:30 [PATCH v5 1/1] usb: gadget: f_fs: Add support for SuperSpeed Mode Manu Gautam
     [not found] ` <1387877408-17567-1-git-send-email-mgautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-02-25  4:47   ` Manu Gautam
2014-02-25 14:01 ` [RFC] usb: gadget: f_fs: Add flags to descriptors block Michal Nazarewicz
     [not found]   ` <xa1tsir7b5uz.fsf-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
2014-02-25 17:02     ` [PATCHv2] " Michal Nazarewicz
2014-02-25 18:32       ` Felipe Balbi
2014-02-28 10:11       ` Manu Gautam
     [not found]       ` <xa1tob1vazxh.fsf-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
2014-06-04 14:24         ` Krzysztof Opasiak
     [not found]           ` <005901cf8000$c16ec090$444c41b0$%opasiak-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-04 19:06             ` Michal Nazarewicz
2014-06-05 11:32               ` Krzysztof Opasiak [this message]

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='008201cf80b1$d9efc590$8dcf50b0$%opasiak@samsung.com' \
    --to=k.opasiak@samsung.com \
    --cc=andrzej.p@samsung.com \
    --cc=balbi@ti.com \
    --cc=benoit@android.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jackp@codeaurora.org \
    --cc=k.lewandowsk@samsung.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mgautam@codeaurora.org \
    --cc=mina86@mina86.com \
    --cc=pheatwol@codeaurora.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.