Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Thomas Green <TGreen2@Sorenson.com>
To:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: k780 keyboard
Thread-Topic: k780 keyboard
Thread-Index: AdVk95O2aFIEbHzJRHC1fordVu8Q7Q==
Date:   Fri, 6 Sep 2019 21:14:27 +0000
Message-ID: <BYAPR04MB5096402D65551A2ECBDE92DB9FBA0@BYAPR04MB5096.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: Sorenson.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: beadb8fa-8561-4be5-f835-08d7330f3388
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2019 21:14:27.7595
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b03ef08-a104-48c4-a951-f18d295428d5
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: lqaDffjMBmebnhgMNoTxXWFpKHRYOAKObNPXuQO9NWly5ptp1iwxrPui2r87/L0FjZ8CkspS+5+F2U72RsLPdA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR04MB5032
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-bluetooth.vger.kernel.org>
X-Mailing-List: linux-bluetooth@vger.kernel.org

All,

I'm having trouble with the Logitech K780 bluetooth keyboard.  It will appe=
ar in the scan, and I can pair then connect the keyboard.  The issue is tha=
t it seems the final set up of the keyboard isn't preformed, and as a resul=
t is unusable.  It would seem to me that the appropriate driver isn't being=
 set up and the /dev/input* files aren't being created.  I see the appropri=
ate udev events when the keyboard connects, and udevadm info -a on the devi=
ce returns all of the appropriate information.  I would guess then that the=
re is a specific udev rule that needs to be made for this keyboard (as othe=
r Bluetooth keyboards seem to work just fine).  Any hint on the driver or u=
dev rule that needs to occur for this particular Bluetooth keyboard?

Thanks in advance,

Tom