On Mon, Sep 24, 2018 at 10:18:52PM +0200, Arnd Bergmann wrote:
> On Tue, Sep 18, 2018 at 7:59 PM Jason Gunthorpe wrote:
> >
> > On Tue, Sep 18, 2018 at 10:51:08AM -0700, Darren Hart wrote:
> > > On Fri, Sep 14, 2018 at 09:57:48PM +0100, Al Viro wrote:
> > > >
_user * as appropriate.
Then it just works right always and the compiler will help address
Al's concern down the road.
Cheers,
Jason
atic const struct file_operations uverbs_mmap_fops = {
> .release = ib_uverbs_close,
> .llseek = no_llseek,
> .unlocked_ioctl = ib_uverbs_ioctl,
> - .compat_ioctl = ib_uverbs_ioctl,
> + .compat_ioctl = generic_compat_ioctl_ptrarg,
> };
>
> static struct ib_client uverbs_client = {
For uverbs:
Acked-by: Jason Gunthorpe
It is very strange, this patch did not appear in the RDMA patchworks,
I almost missed it :|
Jason
.compat_ioctl = vtpmx_fops_compat_ioctl,
> -#endif
> + .compat_ioctl = generic_compat_ioctl_ptrarg,
> .llseek = noop_llseek,
> };
For vtpm:
Reviewed-by: Jason Gunthorpe
Arnd, would you consider including a patch as part of/after this
series to make compat_ioctl in drivers/infiniband/core/uverbs_main.c
use this as well? Looks like a bug too?
Thanks,
Jason
On Mon, May 14, 2018 at 02:59:36PM -0500, David R. Bild wrote:
> On Mon, May 14, 2018 at 2:31 PM, Jason Gunthorpe wrote:
> >
> > On Thu, May 10, 2018 at 09:41:53AM -0500, David R. Bild wrote:
> >
> > > 3) Allow the driver to register the TPM with TPM driver, but n
e TPM driver that it is safe to expose the TPM to userspace. This
> would be my preferred approach.
We already have this. The driver can setup enough to use the TPM
framework to send commands before completing registration. We use it
in startup timeouts and other flows today.
Jason
--
To unsubs
s and would let me drop nearly the entire second patch from
> this series. (I think the dictionary lockout reset can be done via
> the already exported "tpm_send(...)" function.)
Sounds like a much better approach to me.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
has loaded.
The tpm driver already does most of this stuff automatically, why
duplicate it there and why is it coded in a way that doesn't use the
existing TPM services to do it?
Make no sense to me.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-us
ent information? Or should I try to gather more somehow?
Regards,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I'm having this issue on kernel 4.11.0 and 4.11.1. It usually happens
after a while of ordinary USB use. Afterwards, USB does not work. If I
rmmod all the modules and reinsert them, it works for a while, but
even sooner after it stops working again.
[48112.422418] [ cut here ]-
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three,/
So you look at the sixty-fours
On Sun, Nov 29, 2015 at 2:29 AM, Ioan-Adrian Ratiu wrote:
> On Fri, 20 Nov 2
Fixed several style issues with: comments, function perenthesis,
indentation, and conditional braces
Signed-off-by: Jason Eastman
---
drivers/usb/image/mdc800.c | 769 +++-
1 file changed, 336 insertions(+), 433 deletions(-)
diff --git a/drivers/usb
Since usb-storage requires an
interface class of 0x8, I believe it's correct to disambiguate the two
devices by matching on 0xff inside pl2303.
[1] http://permalink.gmane.org/gmane.linux.usb.user/4264
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/pl2303.c | 2 +-
1 file changed, 1
This phone is actually a pl2303 device, and is already supported there.
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/visor.c | 2 --
drivers/usb/serial/visor.h | 1 -
2 files changed, 3 deletions(-)
diff --git a/drivers/usb/serial/visor.c b/drivers/usb/serial/visor.c
index bf2bd40
On Wed, Apr 22, 2015 at 2:38 PM, Greg Kroah-Hartman
wrote:
> I'd bet this is really a pl2303 device, given that the visor driver was
> just a "dumb" pipe to the device and the pilot sync tools never cared
> about baud rates and the like, so odds are the visor entry should be
> removed.
In the lat
This phone is already supported by the visor driver.
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/pl2303.c | 1 -
drivers/usb/serial/pl2303.h | 4
2 files changed, 5 deletions(-)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 829604d..f5257af
value 255 (0xff). Since usb-storage requires an
interface class of 0x8, I believe it's correct to disambiguate the two
devices by matching on 0xff inside visor.
[1] http://permalink.gmane.org/gmane.linux.usb.user/4264
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/visor.c | 2 +-
to be the interface
class, which has value 255 (0xff). Since usb-storage requires an
interface class of 0x8, I believe it's correct to disambiguate the two
devices by matching on 0xff inside pl2303 and visor.
[1] http://permalink.gmane.org/gmane.linux.usb.user/4264
Signed-off-by: Jason A. Donenfel
le it.
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/pl2303.c | 1 -
drivers/usb/serial/pl2303.h | 4
2 files changed, 5 deletions(-)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 829604d..f5257af 100644
--- a/drivers/usb/serial/pl2303.c
+++ b/driver
ort for Marvell EBU on-chip EHCI USB controller"
> - depends on USB_EHCI_HCD && PLAT_ORION
> + depends on USB_EHCI_HCD && ( PLAT_ORION || ARCH_MVEBU )
hmmm, ARCH_MVEBU selects PLAT_ORION in mach-mvebu/Kconfig:8 over here.
What are you trying to fix?
thx,
Jason.
>
On Wed, May 21, 2014 at 03:53:22PM +0200, Gregory CLEMENT wrote:
> On 19/05/2014 13:09, Paul Bolle wrote:
> > On Fri, 2014-05-16 at 15:07 -0400, Jason Cooper wrote:
> >> On Thu, May 15, 2014 at 12:17:35PM +0200, Gregory CLEMENT wrote:
> >>> This patch adds the selecti
++
> 3 files changed, 29 insertions(+)
Patches 14 through 17 applied to mvebu/dt. Patch 17 amended as Sergei
suggested.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
arch/arm/mach-mvebu/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
Patches 10 and 11 applied to mvebu/soc
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> Signed-off-by: Thomas Petazzoni
> ---
> arch/arm/configs/mvebu_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Applied to mvebu/defconfig
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.ke
++
> 3 files changed, 29 insertions(+)
Patches 14 through 17 applied to mvebu/dt. Patch 17 amended as Sergei
suggested.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> Signed-off-by: Thomas Petazzoni
> ---
> arch/arm/configs/mvebu_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Applied to mvebu/defconfig
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.ke
arch/arm/mach-mvebu/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
Patches 10 and 11 applied to mvebu/soc
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
y, I'll fix it up when I pull it in. No need
to respin.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> Signed-off-by: Thomas Petazzoni
> Cc: a...@kernel.org
> Cc: Kevin Hilman
> Cc: Olof Johansson
> Cc: Arnd Bergmann
> ---
> arch/arm/configs/multi_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Jason Cooper
thx,
Jason.
--
To unsubscribe from this list: s
If you need to do another respin of this series, please add Olof, Arnd
and Kevin (and a...@kernel.org) to the To:. Otherwise, I'll take care of
it.
thx,
Jason.
On Tue, May 06, 2014 at 02:14:07AM +0200, Gregory CLEMENT wrote:
> The Marvell Armada 38x platform needs the xhci_mvebu driver
orms have clock support then enabling and disabling
> the clocks have been placed in separate functions. Then if the clocks
> are not supported we still can use the same calls, and there is no
... ?
thx,
Jason.
>
> Signed-off-by: Gregory CLEMENT
> ---
>
have to push the patch to -stable team at least for 3.13,
> I wonder if it would not make sense to extend that at least to 3.12.
> and possibly 3.10 (3.2 is still widely used but I wonder if it makes
> sense to go that far).
Can you pinpoint the commit that introduced the regression?
thx,
1 deletions(-)
Acked-by: Jason Cooper
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Dec 10, 2013 at 09:20:30PM +0900, Jingoo Han wrote:
> Use dev_warn() instead of printk() to provide a better message
> to userspace.
>
> Signed-off-by: Jingoo Han
> ---
> drivers/usb/host/ehci-orion.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
A
rn off debug messages, but that boot parameter is
>> limited to 1023 characters. I'm concerned that if more drivers add
>> dynamic debugging, the distros will eventually run out of space in the
>> dynamic debugging boot parameter. I know Greg was ripping out debugging
>> con
On 06/25/2013 02:03 PM, Joe Perches wrote:
> (Using Jason Baron's most current email address)
>
> On Tue, 2013-06-25 at 10:56 -0700, Joe Perches wrote:
>> On Tue, 2013-06-25 at 10:38 -0700, Greg KH wrote:
>>> On Tue, Jun 25, 2013 at 10:29:50AM -0700, Joe Perches wrote:
le_dbg(mask, fmt, ...)
> do {
> if (mask & some_module_var)
> debug_something(...)
> } while (0)
>
> It'd be nice to consolidate those in dev_dbg
>
> I'll get 'round to it one day if Jason doesn't.
>
Hi,
I've been a bit
a
> frame number of 0 now. So for each allocation when now_frame == 0 we
> allocate from the dma_pool, not from the free_list. The attached
> patch invalidates the frame number in each iTD before it is sent to
> the scheduler. This fixes the problem without the need to iterate
> over a iTD
;s own gateable
clock. The user should be able to conserve power by unloading the
module or building without it.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ci-hcd a library module", we can
> avoid this problem by turning a bus glue into a separate
> module, as we do here for the orion bus glue.
>
> Signed-off-by: Manjunath Goudar
> Signed-off-by: Arnd Bergmann
> Cc: Jason Cooper
> Cc: Andrew Lunn
> ---
> dri
| 12
> arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts |6 ++
> 4 files changed, 34 insertions(+), 0 deletions(-)
Applied to mvebu/dt
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
i | 15 +++
> arch/arm/boot/dts/armada-370.dtsi|9 +
> arch/arm/boot/dts/armada-xp.dtsi | 17 +
> 3 files changed, 41 insertions(+), 0 deletions(-)
Applied to mvebu/dt
thx,
Jason.
--
To unsubscribe from this list: send the line &quo
|5 -
> 1 files changed, 4 insertions(+), 1 deletions(-)
Applied to mvebu/boards
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Manjunath,
I think this is the second version of this series. Please indicate so
in the subject "[PATCH V2 X/Y]" and provide a changelog with each patch
so that we can easily confirm suggested changes from one version to the
next.
thx,
Jason.
On Mon, Feb 11, 2013 at 12:28:
On Tue, Jan 29, 2013 at 03:56:20PM -0300, Ezequiel Garcia wrote:
> Hi Jason,
>
> On Wed, Jan 23, 2013 at 2:40 PM, Jason Cooper wrote:
> > On Wed, Jan 23, 2013 at 02:06:12PM -0300, Ezequiel Garcia wrote:
> >> Jason,
> >>
> >> On Wed, Jan 23, 2013
On Wed, Jan 23, 2013 at 02:06:12PM -0300, Ezequiel Garcia wrote:
> Jason,
>
> On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
> wrote:
> > The Armada 370 and Armada XP SoC has an Orion EHCI USB controller.
> > This patch adds support for this controller in Armada 3
On Thu, Nov 15, 2012 at 4:20 AM, Christoph Hellwig wrote:
> On Wed, Nov 14, 2012 at 05:03:22PM -0500, Jason J. Herne wrote:
>> From: "Jason J. Herne"
>>
>> Force large capacity (> 0x blocks) drives to use READ/WRITE(16)
>> instead
>> of REA
On Wed, Nov 14, 2012 at 5:22 PM, Sergei Shtylyov wrote:
> Hello.
>
>
> On 15-11-2012 2:03, Jason J. Herne wrote:
>
>> From: "Jason J. Herne"
>
>
> You have already posted Try #3. And preferrably, information about patch
> version should be inclu
On Wed, Nov 14, 2012 at 2:02 PM, Sebastian Andrzej Siewior
wrote:
> On Wed, Nov 14, 2012 at 12:55:13AM -0500, Jason J. Herne wrote:
>> }
>> }
>>
>> + /* Use read/write(16) for > 2TB disks */
>> + sdp->use_16_for_rw = (sdkp->
From: "Jason J. Herne"
Force large capacity (> 0x blocks) drives to use READ/WRITE(16) instead
of READ/WRITE(10). Some(most/all?) USB enclosures do not like READ(10) commands
when a large capacity drive is installed. This issue was reported and discussed
here: http://marc.
From: "Jason J. Herne"
Force large capacity (> 0x blocks) drives to use READ/WRITE(16) instead
of READ/WRITE(10). Some(most/all?) USB enclosures do not like READ(10) commands
when a large capacity drive is installed.
Signed-off-by: Jason J. Herne
---
drivers/scsi/sd.c
From: "Jason J. Herne"
Force large capacity (> 2TB) drives to use READ/WRITE(16) instead of
READ/WRITE(10). Some(most/all?) USB enclosures do not like READ(10) commands
when a large capacity drive is installed.
Signed-off-by: Jason J. Herne
---
drivers/scsi/sd.c |5 +
From: "Jason J. Herne"
Force large capacity (> 2TB) drives to use READ/WRITE(16) instead of
READ/WRITE(10). Some(most/all?) USB enclosures do not like READ(10) commands
when a large capacity drive is installed.
Signed-off-by: Jason J. Herne
---
drivers/scsi/sd.c |5 +
On Mon, Nov 12, 2012 at 10:10 AM, James Bottomley
wrote:
> On Mon, 2012-11-12 at 15:31 +0100, Paolo Bonzini wrote:
>> Il 12/11/2012 12:33, James Bottomley ha scritto:
>> > On Fri, 2012-11-09 at 11:08 -0500, Jason J. Herne wrote:
>> >> diff --git a/drivers/usb/stor
On Mon, Nov 12, 2012 at 9:31 AM, Paolo Bonzini wrote:
> Il 12/11/2012 12:33, James Bottomley ha scritto:
>> On Fri, 2012-11-09 at 11:08 -0500, Jason J. Herne wrote:
>>> diff --git a/drivers/usb/storage/scsiglue.c
>>> b/drivers/usb/storage/scsiglue.c
>>> ind
From: "Jason J. Herne"
Force large capacity (> 2TB) drives in USB enclosures to use READ(16) instead
of READ(10). Some(most/all?) enclosures do not like READ(10) commands when a
large capacity drive is installed.
Signed-off-by: Jason J. Herne
---
drivers/scsi/sd.c
Hello, I've noticed Linux seems to have issues with external USB
enclosures containing drives > 2 TB. The USB mass storage driver
apparently emulates a SCSI device and sends a read/write(10) for all
requests where the target sector is not large enough to require the
use of read(16). The issue is
very much for all your help with this.
Do you have any thoughts on where I should take this next?
I noticed that a usb-storage list exists. Perhaps there?
--
- Jason J. Herne (hern...@gmail.com)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messag
On Wed, 7 Nov 2012, Jason J. Herne wrote:
>>> Most likely that's the answer. Of course, for a device to recognize
>>> READ(16) but not READ(10) is a violation of the SCSI spec.
>>>
I can confirm that the use of READ(10) instead of READ(16) is indeed
the problem
On Wed, Nov 7, 2012 at 12:27 PM, Jason J. Herne wrote:
> On Wed, Nov 7, 2012 at 12:14 PM, Alan Stern wrote:
>> On Wed, 7 Nov 2012, Jason J. Herne wrote:
>>
>>> > Most likely that's the answer. Of course, for a device to recognize
>>> > READ(16) but
On Wed, Nov 7, 2012 at 12:14 PM, Alan Stern wrote:
> On Wed, 7 Nov 2012, Jason J. Herne wrote:
>
>> > Most likely that's the answer. Of course, for a device to recognize
>> > READ(16) but not READ(10) is a violation of the SCSI spec.
>> >
>> > I do
On Wed, Nov 7, 2012 at 11:00 AM, Alan Stern wrote:
> On Tue, 6 Nov 2012, Jason J. Herne wrote:
>
>> I was comparing the two USB captures and I noticed the Windows capture
>> uses a READ(16) and Linux is using a READ(10). I'm not sure how the
>> kernel determines w
700's btw :)
Window's first READ(16) is at frame 291.
Linux first READ(1) is at 161.
Hope this is useful. I'll keep digging.
--
- Jason J. Herne (hern...@gmail.com)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to major
Here is the pcap file, as captured from Wireshark.
On Tue, Nov 6, 2012 at 10:46 AM, Alan Stern wrote:
> On Mon, 5 Nov 2012, Jason J. Herne wrote:
>
>> I have a Seagate ST3000DM 3.0TB Sata Drive enclosed in a Vantec
>> NexStar CX USB 3.0/2.0 Enclosure. This enclosure/drive
ch-kirkwood/board-ts219.c |1 -
> drivers/usb/host/ehci-orion.c | 38
> ++--
> 14 files changed, 58 insertions(+), 14 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/usb/ehci-orion.txt
Applied to:
git://git.inf
t; device if it sits on an i2c bus, etc.
> >
> > I Olaf
> >
> > Could i suggest a third option:
> >
> > I just drop USB phy configuration all together. Only mach-orion5x
> > needs this and nobody has shown any interest in moving mach-orion5x to
>
On Sat, Sep 01, 2012 at 11:26:25AM +0200, Andrew Lunn wrote:
> Based on previous work by Michael Walle and Jason Cooper.
>
> Made their work actually work, which required added interrupt from DT
> and auxdata, along with setting the dma_mask, which DT does not
> currently do.
>
have
> USB can specifically disable it.
>
> Signed-off-by: Andrew Lunn
Applied to:
git://git.infradead.org/users/jcooper/linux.git kirkwood/dt
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel
his thread. We can add _LEGACY later, once we are
making more productive use of it. So,
Acked-by: Jason Cooper
thx,
Jason.
> ---
> drivers/usb/Kconfig |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> index a7773a3..7
default y if MACH_LOONGSON1
>+ default y if PLAT_ORION
PLAT_ORION_LEGACY?
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
uch as a Lenovo X220i and an Ivybridge development
> platform that needed to wait ~450-950 microseconds.
This seems fine to me.
I'll test it, merge it, and add a CC for -stable.
Thanks,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" i
71 matches
Mail list logo
