From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Yunke Cao <yunkec@chromium.org>, Ming Lei <tom.leiming@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Max Staudt <mstaudt@google.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v2] media: uvcvideo: Do not alloc dev->status
Date: Thu, 15 Dec 2022 11:08:04 +0200 [thread overview]
Message-ID: <Y5rj9GhQuyNbNnDw@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCtQFR-CPNXu-hqM_11DogMTvdhK9xWy7cZyd7vwZAMBSQ@mail.gmail.com>
Hi Ricardo,
On Thu, Dec 15, 2022 at 08:59:14AM +0100, Ricardo Ribalda wrote:
> Hi Sergey
>
> Thanks for looking into this
>
> On Thu, 15 Dec 2022 at 02:15, Sergey Senozhatsky wrote:
> >
> > On (22/12/14 14:37), Ricardo Ribalda wrote:
> > [..]
> > > +struct uvc_status_streaming {
> > > + u8 button;
> > > +} __packed;
> > > +
> > > +struct uvc_status_control {
> > > + u8 bSelector;
> > > + u8 bAttribute;
> > > + u8 bValue[11];
> > > +} __packed;
> > > +
> > > +struct uvc_status {
> > > + u8 bStatusType;
> > > + u8 bOriginator;
> > > + u8 bEvent;
> > > + union {
> > > + struct uvc_status_control control;
> > > + struct uvc_status_streaming streaming;
> > > + };
> > > +} __packed;
> > > +
> > > struct uvc_device {
> > > struct usb_device *udev;
> > > struct usb_interface *intf;
> > > @@ -559,7 +579,7 @@ struct uvc_device {
> > > /* Status Interrupt Endpoint */
> > > struct usb_host_endpoint *int_ep;
> > > struct urb *int_urb;
> > > - u8 *status;
> > > +
> > > struct input_dev *input;
> > > char input_phys[64];
> > >
> > > @@ -572,6 +592,12 @@ struct uvc_device {
> > > } async_ctrl;
> > >
> > > struct uvc_entity *gpio_unit;
> > > +
> > > + /*
> > > + * Ensure that status is aligned, making it safe to use with
> > > + * non-coherent DMA.
> > > + */
> > > + struct uvc_status status __aligned(ARCH_KMALLOC_MINALIGN);
> >
> > ____cacheline_aligned ?
> >
> > I don't see anyone using ARCH_KMALLOC_MINALIGN except for slab.h
>
> Seems like cacheline is not good enough:
>
> https://github.com/torvalds/linux/commit/12c4efe3509b8018e76ea3ebda8227cb53bf5887
> https://lore.kernel.org/all/20220405135758.774016-1-catalin.marinas@arm.com/
>
> and ARCH_KMALLOC_MINALIGN is what we have today and is working...
>
> But yeah, the name for that define is not the nicest :)
>
> I added Jonathan Cameron, on cc, as he had to deal with something
> similar for iio in case we are missing something
I'd like to get feedback on this from DMA and USB experts. Expanding the
CC list of the original patch would help (especially including the
linux-usb mailing list).
> ps: and I thought this was an easy change :P
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-12-15 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 13:37 Ricardo Ribalda
2022-12-15 1:14 ` Sergey Senozhatsky
2022-12-15 7:59 ` Ricardo Ribalda
2022-12-15 9:08 ` Laurent Pinchart [this message]
2022-12-15 9:11 ` Laurent Pinchart
2022-12-15 11:45 ` Jonathan Cameron
2022-12-20 22:59 ` Ricardo Ribalda
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=Y5rj9GhQuyNbNnDw@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mstaudt@google.com \
--cc=ribalda@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=tom.leiming@gmail.com \
--cc=yunkec@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®