redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

greybus: Fixup __u64, __u32 to __le64, __le32 in timesync declarations 

A number of data in TimeSync command structures are declared __u64/__u32
instead of __le64/__le32, I forgot to put this through an x86_64 compile
before presentation for merge and as a result didn't catch this error. This
patch fixes.

Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
hifive-unleashed-5.1
Bryan O'Donoghue 2016-04-12 17:15:11 +01:00 committed by Greg Kroah-Hartman
parent a7ddda1f5a
commit 777471a445
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/staging/greybus/control.c
View File

@ -269,7 +269,7 @@ int gb_control_timesync_authoritative(struct gb_control *control,
int i;
for (i = 0; i < GB_TIMESYNC_MAX_STROBES; i++)
request.frame_time[i] = frame_time[i];
request.frame_time[i] = cpu_to_le64(frame_time[i]);
return gb_operation_sync(control->connection,
GB_CONTROL_TYPE_TIMESYNC_AUTHORITATIVE,

12
drivers/staging/greybus/greybus_protocols.h
View File

@ -180,7 +180,7 @@ struct gb_control_timesync_enable_request {
/* timesync enable response has no payload */
struct gb_control_timesync_authoritative_request {
__u64 frame_time[GB_TIMESYNC_MAX_STROBES];
__le64 frame_time[GB_TIMESYNC_MAX_STROBES];
} __packed;
/* timesync authoritative response has no payload */
@ -911,16 +911,16 @@ struct gb_svc_route_destroy_request {
struct gb_svc_timesync_enable_request {
__u8 count;
__u64 frame_time;
__u32 strobe_delay;
__u32 strobe_mask;
__u32 refclk;
__le64 frame_time;
__le32 strobe_delay;
__le32 strobe_mask;
__le32 refclk;
} __packed;
/* timesync enable response has no payload */
/* timesync authoritative request has no payload */
struct gb_svc_timesync_authoritative_response {
__u64 frame_time[GB_TIMESYNC_MAX_STROBES];
__le64 frame_time[GB_TIMESYNC_MAX_STROBES];
};
#define GB_SVC_UNIPRO_FAST_MODE 0x01